Stored on device first
Notification history is intended to remain on the Android device unless the user explicitly exports or backs it up.
Privacy policy
Notisaver is presented as a local-first notification vault.
Last updated: March 6, 2026
User-controlled capture
Users can mute apps, delete records, change retention behavior, and stop using the app at any time.
Support inbox
Questions can be sent through the contact page or by email at peakliterature@gmail.com.
1. Scope
This policy applies to the Notisaver Android application, the static website, and the contact form experience hosted for the app. It explains the categories of information involved, why they are used, and what choices users have.
2. App information that may be processed
The app may process notification content and metadata shown on the device, including app name, package name, title, body text, timestamps, categories, and other notification details needed to display history, conversations, search results, statistics, backup exports, and digest summaries.
3. Website and contact information
The website itself is informational. If a visitor uses the contact form, the submitted name, email address, subject, and message are forwarded to the support inbox so the team can reply. Contact form forwarding is handled through FormSubmit.
4. How information is used
Information is used to archive notifications, support filters and search, display conversation threads, create statistics, generate exports or backups on request, provide support replies, and maintain the product website.
5. Storage and retention
Notification history is intended to be stored locally on the user device. Users may delete items, disable capture, or configure auto-delete rules based on app capabilities. Exported files and backup archives leave the app sandbox by design and should be handled carefully.
6. Security practices
Notisaver is described as a privacy-focused app with app lock options, per-app capture controls, and encrypted backup flows such as AES-256-GCM for supported backup packages. No method of storage or transmission is perfectly risk-free, so users should still protect their device and exported files.
7. Third-party services
The website may rely on third-party hosting and infrastructure providers such as Cloudflare Pages, GitHub, and Google Fonts. Contact form submissions are forwarded using FormSubmit so the support inbox can receive them without a custom backend.
8. User choices
Users can disable notification access, stop using the app, delete saved history, avoid using the contact form, or contact support directly by email instead of the hosted form.
9. Children and sensitive data
Notisaver is not directed to children. Users should avoid storing or exporting sensitive content unless they understand the privacy implications of keeping that data on their device or in exported files.
10. Updates and contact
This policy may be updated as the product evolves. Material changes will appear on this page with a revised effective date. Privacy questions can be sent to the contact page or directly to peakliterature@gmail.com.
Need help?
Privacy questions should go to the Notisaver support inbox.
If you need clarification about what the website or app does with data, use the contact form and include the device model, Android version, and what part of the app you are asking about.