Privacy Policy
Notifications Is Jemica — Android notification forwarder
Effective date: July 3, 2026
In short: Notifications Is Jemica reads the notifications of the apps you select and sends their content to destinations you configure — your own email inbox, your own Telegram bot, or your own webhook. Everything is processed on your phone. We operate no servers, we never see, collect, sell, or share your data, and the app contains no ads, no analytics, and no trackers.
1. Who we are
Notifications Is Jemica ("the app") is an Android application whose sole purpose is to forward notifications from apps you choose to a destination you choose. This policy explains what data the app touches, where it goes, and what never happens to it.
2. Data the app accesses
| Data | Why |
|---|---|
| Notification content (title, text, sender, category, time) — only from apps you enable | This is the app's core, user-facing function: forwarding those notifications to you. Notifications from apps you did not enable are ignored and never processed beyond checking the app they came from. |
| List of installed apps with a home-screen launcher | Shown once in the app picker so you can choose which apps to forward from. The list never leaves your device. |
| Delivery credentials you enter (email SMTP app password, Telegram bot token, webhook URL/secret) | Used only to deliver your forwards. Stored exclusively on your device in Android Keystore–backed encrypted storage. Never transmitted anywhere except to the corresponding service as part of the delivery itself. |
The app requires your explicit consent inside the app, plus the Android Notification access permission that you grant manually in system settings, before it can read any notification.
3. Where your data goes
Forwarded notification content travels directly from your device to the destination(s) you configured — there is no intermediate server operated by us:
- Email: sent through your own email account via your provider's SMTP server (e.g. Gmail, Outlook, iCloud), authenticated with an app-specific password you created.
- Telegram: sent through your own Telegram bot to your own chat, via the official Telegram Bot API over HTTPS.
- Webhook: sent as a JSON request to a URL you control.
Once delivered, that content is governed by the privacy policy of the service you chose (your email provider, Telegram, or your webhook endpoint) — the same as any message you send yourself through those services.
4. Data stored on your device
- Your rules and settings — which apps to forward, keyword/regex filters, schedule, delivery preferences.
- Delivery credentials — encrypted with the Android Keystore; never stored in plain text, never written to logs.
- Forward history — a local list of recently forwarded notifications (including their text) so you can review what was sent. It is capped at the most recent 200 entries and can be wiped at any time with the in-app "Clear history" button.
- A short-lived de-duplication cache — content hashes kept for minutes, used to avoid sending the same notification twice.
All of this lives only on your phone. Uninstalling the app permanently deletes all of it.
5. What we never do
- No servers: we do not operate any backend, and your notification content is never sent to us.
- No collection: we cannot see your notifications, credentials, rules, or history.
- No selling or sharing of data with anyone, for any purpose.
- No advertising, no ad identifiers, no profiling.
- No analytics, telemetry, or crash-reporting SDKs.
- No use of notification data for anything other than the forwarding you configured.
6. Android permissions used
| Permission | Purpose |
|---|---|
Notification access | Read notifications from the apps you selected (granted manually in system settings; revocable there at any time). |
INTERNET | Deliver your forwards to your email provider, Telegram, or webhook. |
POST_NOTIFICATIONS | Show the app's own alerts, e.g. "forwarding stopped working" or "email sign-in failed". |
RECEIVE_BOOT_COMPLETED | Resume forwarding automatically after your phone restarts. |
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS | Optionally exempt the app from battery optimization so forwarding keeps working in the background. |
7. Data retention and deletion
- Forward history: kept on-device, newest 200 entries only; delete any time via History → Clear history.
- Credentials: removed when you disconnect a delivery method in Settings, or when you uninstall the app. You can additionally revoke access at the source at any time (revoke the email app password, revoke the Telegram bot token via @BotFather).
- Everything else: deleted permanently when you uninstall the app.
Emails and Telegram messages already delivered to your own accounts are yours and are not affected by anything the app does.
8. Security
Delivery credentials are stored in encrypted preferences backed by the Android Keystore. All network delivery uses encrypted transport: SMTP with STARTTLS or SSL/TLS for email, and HTTPS for Telegram. We recommend HTTPS for webhook endpoints; an optional shared secret header lets your endpoint verify that requests come from your device.
9. Children
The app is a general-purpose utility, is not directed at children under 13, and collects no data from anyone — children included.
10. Changes to this policy
If the app's data handling ever changes, this policy will be updated and the effective date above revised before the change ships. Because the app has no backend, changes can only ever be introduced through an app update you install.
11. Contact
Questions about this policy or the app's data handling: info@jemi.ca