Notificator Privacy Policy · Iterative Key LLC

This Privacy Policy explains how Iterative Key LLC (“we,” “us,” or “our”) handles information in Notificator (the “app”), our notification automation app for Android. It applies to the app only. Our website is covered by the separate website privacy policy.

Notificator is designed to work entirely on your phone. It does not require an account, does not connect to any server operated by us, and does not include advertising, analytics, or crash reporting. We have no way to see your notifications or anything else you do in the app.

Information stored on your device

To do its job, Notificator reads the notifications other apps post on your phone, once you grant it notification access. It stores the following in the app’s private storage, which other apps cannot read:

Notification history: each notification’s app, title, text, time, icon, images, buttons, and related details, kept until you delete them. Notifications can contain anything your apps post, including messages from other people, sign-in codes, and other sensitive information.
Triggers: the conditions and actions you set up, including any words, places, Wi-Fi network names, Bluetooth devices, reply text, links, and webhook addresses you enter, and a log of each time a trigger ran.
Statistics: counts of the notifications that arrived and of what your triggers handled, shown in Insights.
AI summaries, if you turn them on: the summaries written for you, the topics you follow, and the on-device model if you download one.
App settings: your preferences, and the addresses and keys of any servers you connect the app to.

This information is never sent to us.

Backup and moving to a new phone

Notificator does not use Android backup. Its data is left out of cloud backups and out of device-to-device transfer, so your notification history never ends up in a backup you did not choose to make.

Instead, you can create a backup file yourself in the app. The file is encrypted with a password you choose, and can also be opened with a recovery key the app gives you. You decide where the file is saved, for example on your phone or in a cloud storage app; once saved there, it is handled by that storage provider under its own privacy policy. We never receive it, and without your password or recovery key its contents cannot be read.

What can leave your phone

Nothing leaves your phone unless you set it up. Each of the following is optional and off until you configure it, and each sends information only to the service or server you chose, never to us:

Webhook actions. A trigger can call a web address you enter, sending whatever you put in the request, which can include the notification’s text.
AI voice. The “read with an AI voice” action sends the text to be spoken to the OpenAI-compatible speech server you set up.
AI summaries. If you turn on AI summaries and choose a server instead of the on-device model, the notifications being summarized (their apps, titles, and text) are sent to the OpenAI-compatible server you set up. Topic summaries always use that server.
Downloading the on-device model. If you choose to run summaries on your phone, the app downloads the model from Hugging Face. The download sends Hugging Face the same technical information as any download, such as your device’s IP address, and no notification content. On-device summaries never leave your phone.
Connecting a Notificator server. If you pair the app with a Notificator server, the notifications your triggers forward are encrypted on your phone before they are sent, so that only your paired devices can read them, not the server.

These services and servers are operated by you or by the companies you chose, not by us, and their handling of your information is governed by their own privacy policies. Notificator sends requests to the exact address you enter; if that address does not use HTTPS, the information is sent without encryption.

Permissions the app uses

Notification access: to read, keep, and act on the notifications your apps post. This is the one permission the app needs to work.
Notifications: to show its own notifications, such as a summary being ready or a backup in progress.
Location, including “Allow all the time”: asked for only when you add a place or Wi-Fi network condition to a trigger, to check where you are or which network you are on when a notification arrives. It is used on your phone to check the condition and is not sent anywhere.
Nearby devices (Bluetooth): asked for only when you add a Bluetooth condition, to check which devices are connected.
Camera: to scan a QR code of a shared trigger or of a device you are pairing. Images are processed on your phone and are not saved or sent.
Installed apps: to list the apps on your phone when you choose which apps a trigger applies to, including apps that have not posted a notification yet. The list is not sent anywhere.
Do Not Disturb access: to let a sound action play even when your phone is silenced, if you allow it.
Ignore battery optimizations: to ask that the system not stop the app in the background, which could make it miss notifications.
Foreground service, vibration, and flashlight: to finish a backup you started after you leave the app, and to vibrate or blink the flashlight when a trigger asks for it.
Internet: used only for the features you set up, described above.

The app does not access your contacts, microphone, photos, calendar, or other accounts.

Features that rely on your phone

Text-to-speech. To read notifications aloud, the app uses the text-to-speech engine installed on your phone. The engine is provided by your phone’s maker or by another company you have chosen, and its handling of text is governed by that provider’s own privacy policy.

Google ML Kit. QR code scanning, and choosing the right language when a notification is read aloud, use Google ML Kit, which runs on your phone. The images and text it processes are not sent anywhere. ML Kit may send Google technical information about how these features perform, such as the device model, app version, and how the features were used, as described in the Google Privacy Policy.

Assistants on your phone. On Android 16 and later, Notificator lets the assistant built into your phone, and other apps the system allows, ask it for your recent notifications and statistics, read them aloud, or create and change triggers when you ask the assistant to. What an assistant does with that information is governed by its provider’s privacy policy. Notificator itself sends nothing to them.

Actions that reach other apps. Replying to a notification, pressing one of its buttons, or dismissing it works through the app that posted it. Copying text puts it on your phone’s clipboard, where other apps may be able to read it. Opening an app or a link hands it to that app or to your browser.

Sound and screen. A notification read aloud, or a message spoken by a trigger, can be heard by anyone near your phone. Keep this in mind when setting up triggers for private conversations.

We do not collect information from the app, so we do not use it for anything, and we do not sell, rent, trade, or share it. We may disclose information if required to do so by law, or to protect the rights, safety, or property of our users, ourselves, or others. If Iterative Key LLC is involved in a merger, acquisition, or sale of assets, this policy will continue to apply.

Security

Information on your phone is protected by Android’s app sandbox and your phone’s storage encryption. Backup files are encrypted with your password, and notifications forwarded to a Notificator server are encrypted before they leave your phone. No method of storage or transmission is completely secure, so connect the app only to services and servers you trust, and use HTTPS addresses where you can.

Your choices and rights

You can delete notifications, triggers, and summaries at any time in the app, or delete all notification data from Settings.
Turning off AI summaries deletes the saved summary and offers to delete the downloaded model.
You can remove notification access, location, or any other permission in your phone’s Settings at any time. The features that need it stop working, and the rest of the app keeps working.
Uninstalling the app deletes everything it stored on your phone. Backup files you saved elsewhere remain until you delete them.

Because we do not collect your information, we have nothing to give you access to, correct, or delete. Data you sent to a service or server you chose is held by that service or server; contact its operator to exercise your rights there. If you have questions, please contact us.

Children’s privacy

The app is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided personal information through the app, please contact us and we will take appropriate steps.

Changes to this policy

If we change how the app handles information, we will update this policy on this page and change the effective date above. If the changes are significant, we will also let you know in the app or in its store listing.

Contact

Questions about this policy? Email us at [email protected].