Effective date: 12 July 2026
This Privacy Policy explains what information Notily (the "App") accesses, how it is used, what remains on your device, and what is processed by the third-party services included in the App.
Notily is a local-first notification-history app. Captured notification content is stored in the App's private storage on your device. Notily does not automatically upload that content to the developer or to a Notily server, and the developer has no way to view it.
Notily has no user accounts or cloud-sync service. If you explicitly copy, share, or export content, it can leave the App through the recipient app, clipboard, or document provider you choose. The free version also uses Google AdMob. The App uses Firebase Analytics, Crashlytics, Remote Config, Installations, and Sessions, as described below. Google Play handles optional Premium purchases and in-app updates. We do not sell your personal data.
When you grant Android's Notification Access permission and capture is enabled, Notily can read notifications as they are posted, including while the App is not open. This access is the App's core function.
Depending on what a source app includes in a notification, Notily may locally process and store:
- notification titles, text, expanded text, sender or caller names, conversation names, message history, and reply history;
- the source app name and package, timestamps, notification category, channel and group information;
- images, avatars, media details, action labels, call information, progress information, and other notification metadata; and
- potentially sensitive content, including personal messages, information about other people, one-time passcodes, and financial or transactional alerts.
Notification text and metadata are stored in an app-private database. Captured images are stored as app-private files. Notily does not send captured notification content to Firebase, AdMob, Google Play, or the developer.
Notily also stores App settings and locally derived information such as rules, filters, tags, blocked or allowed apps, observed app identities, bookmarks, read state, reminder settings, and Premium entitlement state. This information remains in the App's private storage unless you explicitly export or share it.
Android system backup and device-to-device transfer are disabled for Notily's private database, captured images, and preferences.
You can:
- revoke Notification Access in Android Settings;
- pause capture or restrict capture to selected apps;
- delete individual notifications, conversations, or history inside Notily;
- choose an available automatic-retention period;
- copy or share selected text or images; and
- if Premium is active, export text history as JSON or CSV and import a compatible JSON export.
Copying places the selected content on Android's clipboard. Sharing sends the selected content to an app you choose. Exporting uses Android's document picker, so you can select local storage or a third-party provider such as Google Drive. Data sent to another app or provider is then governed by that recipient's terms and privacy policy. Uninstalling Notily does not delete copies that you previously exported, copied, or shared.
Notily uses the Google Mobile Ads SDK to show ads to eligible free users. Ads are not requested until Google Play Premium status has been resolved and Google's User Messaging Platform indicates that ads may be requested. Premium users do not receive AdMob ad requests from Notily.
Google states that the Mobile Ads SDK may automatically collect and share:
- the device's IP address, which may be used to estimate general location;
- app and ad interactions, including app launches, taps, and video views;
- diagnostic and performance information, including launch time, hang rate, and energy usage; and
- device or account identifiers, including the Android Advertising ID, app-set ID, and other applicable identifiers.
Google uses this information for advertising, analytics, and fraud prevention. Depending on your region and choices, ads may be personalised, non-personalised, or limited. Where Google requires a consent or privacy-options form, Notily uses Google's User Messaging Platform to present it and provide a way to revisit applicable choices.
You can reset or delete the Android Advertising ID through your device's privacy or ads settings. Buying Premium removes ads, but does not disable the separate Firebase services described below.
Google Analytics for Firebase is enabled by default. You can disable it independently in Notily under Settings > Privacy & security > Diagnostics.
When enabled, Analytics may automatically process information including:
- an installation-scoped app-instance ID;
- masked-IP-derived coarse location;
- app version, device and operating-system information, and language;
- app lifecycle, screen-view, and session events; and
- in-app purchase or subscription events, including product identifiers and prices.
Notily does not set a Firebase Analytics user ID and has disabled Firebase Analytics' separate Advertising ID collection. AdMob may still use the Advertising ID as described above. Notily does not include captured notification content, message text, sender names, or other captured payloads in Analytics events.
Disabling Analytics stops future Analytics collection from the App while it remains disabled. Information previously sent is retained and deleted according to Google's and the developer's configured Analytics retention controls.
Firebase Crashlytics is enabled by default. You can disable it independently in Notily under Settings > Privacy & security > Diagnostics.
When enabled, Crashlytics may collect crash stack traces, relevant application state, device metadata, a Crashlytics installation UUID, a Firebase installation ID, Analytics breadcrumb events, Remote Config rollout metadata, and reported non-fatal errors. Notily uses this information to diagnose crashes and improve stability.
Notily does not attach captured notification content, messages, sender names, or other captured payloads to crash reports. Disabling Crashlytics prevents Crashlytics reporting while it remains disabled. Information already transmitted follows Firebase's retention and deletion practices.
Notily uses Firebase Remote Config to retrieve a promotional feature flag and promotional text without requiring an App update. Remote Config may contact Firebase at startup and when offers are refreshed. This operates separately from the Analytics and Crashlytics switches.
Firebase states that Remote Config automatically processes information such as country code, language code, time zone, platform and OS version, App ID, package name, App version, SDK version, and Firebase installation ID.
Firebase Installations generates a per-installation identifier used by Firebase services. Firebase Sessions, included with Crashlytics, may process App and device metadata, network-connection type, and session information such as when the App enters the foreground. These services are used to deliver configuration and support stability reporting; they are not used to upload captured notification content.
Google Play Billing processes optional Premium purchases and subscriptions. Google handles payment-card and payment-account details. Notily receives and temporarily processes the product identifier, offer information, purchase state, purchase token, and acknowledgement status needed to complete a purchase and verify Premium access. Notily locally stores an entitlement state and cached offer information; it does not store your payment-card details.
The Google Play in-app update service may process App version and update-availability information to offer updates through Google Play.
Depending on which services are active, Google services may process the Android Advertising ID, app-set ID, Analytics app-instance ID, Firebase installation ID, Crashlytics installation UUID, IP address, and related technical identifiers.
Notily does not request GPS or precise-location permission. AdMob may estimate general location from an IP address, and Analytics may derive coarse location from a masked IP address.
Information may leave the device in these limited circumstances:
- Google processes technical, advertising, analytics, diagnostics, configuration, purchase, and update information through AdMob, Firebase, and Google Play as described in this Policy.
- You explicitly copy, share, export, or save content using an app or document provider you select.
- Information may be disclosed where legally required, such as in response to a valid legal process. The developer does not operate a server containing your captured notification history.
We do not sell captured notification content or other personal data.
For free users, unbookmarked notification history is retained for the selected period, up to 30 days. Premium users may select the available retention periods, including keeping history indefinitely. Bookmarked notifications are excluded from automatic retention deletion and remain until you remove the bookmark, delete the notification, clear the relevant history, or uninstall the App.
Other local settings and preferences remain until you change or clear them or uninstall Notily. Uninstalling removes Notily's app-private data from the device, subject to Android's normal deletion behaviour. It does not remove content previously copied, shared, or exported outside the App.
Data processed by Google is retained under Google's service-specific policies and the retention controls available to the developer. Disabling Analytics, Crashlytics, or ads does not automatically erase information already processed by Google.
Because Notily has no user account and Google identifiers are generally installation-scoped or pseudonymous, the developer may not be able to associate a privacy request with a particular SDK record. You may contact us using the details below, and you can also use the privacy and deletion controls provided by Google and Android.
Notily stores captured content in Android app-private storage and does not enable Android cloud backup or device transfer for that content. Data transmitted by the included Google SDKs is encrypted in transit using HTTPS or TLS. When you share or export data, its security is also determined by the recipient app, storage location, or provider you select.
No storage or transmission method can guarantee absolute security. You are responsible for protecting access to your device and for deciding what notification content to copy, share, or export.
Notily is not designed or directed to children under 13, or the minimum age required by local law. We do not knowingly create profiles for children or operate user accounts. If you believe a child has provided information through the third-party services described here, contact us.
Depending on where you live, you may have rights concerning personal data, such as access, correction, deletion, restriction, objection, or withdrawal of consent. You can exercise many controls directly through Notily, Android, Google's consent interface, and your Google account settings. You may contact us with other privacy questions or requests.
Data handled by Google services is also governed by the applicable Google terms and privacy policies:
- Google Privacy Policy: https://policies.google.com/privacy
- Google technologies used by partners: https://policies.google.com/technologies/partner-sites
- Firebase privacy and security information: https://firebase.google.com/support/privacy
- Google Mobile Ads SDK data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
- Google Analytics for Firebase data disclosure: https://support.google.com/analytics/answer/11582702
We may update this Privacy Policy to reflect changes to Notily, its third-party services, or legal requirements. The effective date at the top identifies the latest version.
Developer: Baxolino
Privacy contact: alientackers@gmail.com