Privacy Policy
This Privacy Policy explains what information the AIblink mobile app and aiblink.in website ("AIblink", "we", "us") collects, why we collect it, and how it is used. We aim to collect as little as possible — AIblink is a news reader, not an identity service.
1. Information we collect
The app collects only what is needed to deliver news and notifications:
- Push notification token (Firebase Cloud Messaging registration ID). When you enable notifications, Google Firebase issues an opaque token for your device. We store this token on our server so we can send you notifications about new articles. The token does not contain your name, email, phone number, or location, and it cannot be used to identify you outside the FCM system.
- Notification preferences. If you turn specific notification categories on or off in the app, that preference is stored with your token so the right messages are routed to your device.
- Standard server logs. Like every website, our server records the IP address and user-agent of inbound requests for short windows (typically a few days) so we can debug problems and prevent abuse. These logs are not linked to your notification token.
The app does not collect or transmit your name, email, phone number, precise or coarse location, contacts, calendar, photos, microphone, camera, SMS, call logs, browsing history, advertising ID, or device fingerprint. The app has no user accounts on the reader side.
2. How we use the information
- To send you push notifications about new articles via Firebase Cloud Messaging.
- To stop sending notifications when you turn them off or uninstall the app.
- To keep the service running reliably (debugging, abuse prevention).
We do not use your data for advertising, profiling, or any form of behavioural targeting. We do not sell or rent it.
3. Third-party services
AIblink uses Firebase Cloud Messaging (operated by Google) to deliver push notifications. When you enable notifications, your device communicates with Google's FCM servers to register and receive messages. Google's handling of FCM data is governed by their Firebase Privacy and Security documentation and the Google Privacy Policy.
We do not use any other third-party analytics, advertising, crash-reporting, or tracking SDKs. There are no third-party cookies on the website.
4. Data retention
- Push tokens are kept until you uninstall the app or Firebase reports them as invalid (e.g. the app was wiped). Stale tokens are deleted automatically when a delivery attempt fails permanently.
- Server logs are kept for a short rolling window (typically a few days) and then deleted.
- Article content is published by AIblink editors and is not personal data.
5. Your choices
- Stop receiving notifications: turn off notifications for AIblink in your device Settings, or uninstall the app. Either action invalidates the push token on Google's side and the token will be cleared from our database the next time we attempt delivery.
- Request deletion: if you'd like us to delete any data we hold about your device immediately, email guguloothu@gmail.com from any address with your FCM token (visible in app settings) or a description of when you installed the app. We respond within 30 days.
6. Children's privacy
AIblink is a general-audience news app and is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will delete it.
7. Security
Data is transmitted over HTTPS. Push tokens are stored on a hardened server. We do not have any database of names, emails, passwords, or payment information about readers because we don't collect any.
8. Changes to this policy
We may update this policy when the app changes (for example, if we add a new feature that collects different information). When we do, we will update the "Effective date" at the top. Material changes will also be announced via an in-app notice.
9. Contact
Questions, deletion requests, or complaints can be sent to: guguloothu@gmail.com.