Policy
Privacy Policy
Last updated: April 14, 2026
This Privacy Policy explains how alrim may collect, use, store, and share information when you
use our websites, apps, and notification-related services, including alrim.app, alrim.me, and alrim.io.
This policy is intended to cover both website usage and Android app features such as channel
subscriptions, push notifications, and QR-code scanning.
1. Scope
alrim is a notification utility that helps users subscribe to channels, receive push
notifications, open deep links, and review notification-related history. This policy applies
to information processed through our public websites, app interfaces, and supporting backend
services.
2. Information We Collect
- - Information you provide directly, such as notification content, channel titles, support messages, or other data you intentionally submit.
- - Device and technical information such as IP address, browser type, device type, operating system, request metadata, and basic access or error logs.
- - Notification-related information such as channel identifiers, delivery status, topic subscription state, and diagnostic information needed to operate the service.
- - App or browser storage data such as preferences, pinned channels, locally saved notification metadata, and similar settings stored on your device.
3. Camera and QR Scanning
- - The Android app may request camera access so you can scan QR codes to subscribe to channels more easily.
- - Camera access is only used for the QR scanning feature while you choose to use it.
- - Camera preview frames are intended to be processed locally on your device for QR recognition and are not intentionally uploaded to our servers merely because you opened the scanner.
- - If you do not want to grant camera access, you can still use manual links, direct channel URLs, or other non-camera subscription flows where available.
4. Push Notifications and Firebase Cloud Messaging
- - We may use Firebase Cloud Messaging (FCM) or similar notification infrastructure to deliver push notifications to subscribed devices.
- - When push notifications are enabled, notification-related technical identifiers, such as a push token or topic subscription data, may be processed by Google Firebase and related infrastructure providers.
- - Notification payloads may include a title, body, channel identifier, and optional structured data supplied by the sender.
- - Delivery providers operate under their own privacy terms, and their handling of technical delivery metadata is governed by their respective policies.
5. How We Use Information
- - To provide, operate, maintain, and secure our services.
- - To process notification requests, deliver channel subscriptions, and support app or web features.
- - To monitor reliability, investigate abuse, troubleshoot failures, and improve performance and product quality.
- - To respond to support requests, legal obligations, security incidents, or service communications.
6. Information Stored Locally on Your Device
- - The app or website may store local preferences, pinned channels, subscription metadata, cached notification data, or similar settings on your device.
- - Local device storage is used to make the service work properly and improve continuity across app sessions.
- - You may be able to remove some or all locally stored data by clearing app storage, resetting the app, or using available in-app management controls.
7. Server Logs and Notification History
- - Our backend services may record operational details such as request IP address, user agent, delivery status, error messages, timestamps, channel codes, and sender-related identifiers.
- - We may keep hashed publisher-key attribution or similar technical identifiers for abuse prevention, diagnostics, and service integrity.
- - Depending on the feature, some send-history information may be visible to users by product design.
8. How We Share Information
- - We may share information with hosting, infrastructure, analytics, app-distribution, or notification-delivery providers when necessary to run the service.
- - We may disclose information if required by law, legal process, or to protect the rights, safety, and security of users, operators, or the public.
- - We do not sell personal information in exchange for money.
9. Data Retention
- - We retain information for as long as reasonably necessary to provide the service, maintain security, comply with legal obligations, resolve disputes, and enforce our terms.
- - Retention periods may vary depending on the type of data, the feature involved, and operational or legal requirements.
- - Some information stored locally on your device may remain there until you remove it, clear app storage, or uninstall the app.
10. Your Choices
- - You can control notification permissions through your device, browser, or operating system settings.
- - You can deny camera permission and avoid QR scanning if you do not want the app to access the camera.
- - You can manage cookies, local storage, and similar browser technologies through your browser settings, although some features may stop working properly.
11. Security
We use reasonable administrative, technical, and operational measures intended to protect
information handled through the service. However, no internet, mobile device, or electronic
storage system is completely secure, and we cannot guarantee absolute security.
12. Children's Privacy
Our services are not intended for children under the age required by applicable law to use
the service without parental consent. If you believe a child has provided information in
violation of applicable law, contact the service operator of this deployment.
13. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we may revise the
"Last updated" date above and publish the updated version on this page.
14. Contact
For privacy questions, data-related requests, or policy concerns, contact the service operator
of this deployment.