Transparency & control

Privacy Policy

NotiVault is an Android notification history and backup application. This policy describes what information the app handles, why it is needed, where it is stored, and how you can control or delete it.

Effective: November 22, 2026Applies to: NotiVault for Android
Important: Notification access is sensitive. If you enable Android Notification Access, NotiVault may read and save notifications from other apps. These notifications may contain message previews, names, authentication codes, financial alerts, or other private information. Only enable access on a device you own or are authorized to manage. Cloud backup is optional and should be enabled only when you understand its purpose.

1. Overview

NotiVault helps you preserve notification history on your Android device and, if you choose, back up and recover that history using your Google account. The app also supports recovery-password-protected restoration, multiple linked devices, device-specific backup management, and a cloud trash feature.

Notifications are not necessarily complete copies of the underlying messages or conversations. What the app can capture depends on Android, the sending application, your permissions, and device settings.

2. Information we handle

Notification data

When Notification Access is enabled, NotiVault can process information made available by Android's notification service, which may include:

  • The originating app name or package identifier.
  • Notification title, text, message preview, and other notification details provided by Android.
  • Notification timestamps, Android notification identifiers, and related metadata.

Because apps may display sensitive content in notifications, this information can sometimes include personal or confidential information. NotiVault does not require you to share the contents of a separate app's account or inbox directly.

Google account and backup information

If you connect Google Drive, the app may process your selected Google account identity (such as email address and display information), the authorization necessary to access its own app backup storage, encrypted backup files, and information used to associate backups with devices.

Device and operational metadata

To make multi-device backup, recovery, and settings synchronization work, NotiVault processes device identifiers used by the application, device names or labels, backup status/timestamps, synchronization settings, and operational diagnostics. These are not a guarantee that your device is anonymous.

Recovery password and key material

The app uses a recovery password and encryption keys to protect backup operations. Your recovery password may be entered to unlock, restore, or confirm protected deletion actions. Encryption key-related records may be stored in protected local storage and, where required for cross-device recovery, in your app's Google Drive storage.

3. Permissions, disclosure, and consent

Notification Access: Android requires you to explicitly enable access in device settings. This allows NotiVault to observe notifications and record information that Android makes available. You can revoke this permission in Android settings. Revoking access stops future capture but does not automatically erase history or backups already stored.

Google sign-in and Drive authorization: These are requested for optional Google Drive features. You can use local notification history without enabling cloud backup, subject to the app's available local functions.

Background backup: If enabled, NotiVault may upload encrypted changes periodically, including while the app is not open, subject to Android scheduling, internet access, and an available encryption key. You can turn off background backup in the app.

Some deletion operations are designed to preserve records in encrypted Cloud Trash before deleting their active copies; therefore, those operations may require network access and authentication.

4. Why we use this information

  • To capture, display, search, and organize your notification history.
  • To filter unwanted system or selected app notifications according to your settings.
  • To create and restore encrypted backups in Google Drive.
  • To identify and manage backups from multiple devices linked to your account.
  • To synchronize supported device settings and coordinate app-initiated device management features.
  • To support recovery, deletion, Cloud Trash, troubleshooting, and backup status reporting.

Google account data obtained through Google APIs is used for the user-facing account, backup, synchronization, and recovery functions described here, not for unrelated advertising or profiling.

5. Where data is stored and how it is protected

On your device: Notification history and app settings are stored locally. Local files remain subject to your device's security, backup configuration, and risks associated with device compromise or loss.

In your Google Drive: When cloud features are enabled, NotiVault stores its encrypted backup and recovery-related files using Google Drive's application-specific storage (appDataFolder). These files are not the same as publicly shared Drive files.

Encryption: NotiVault is designed to encrypt cloud notification backups with AES-256-GCM and to use a recovery-password and Android Keystore-based protection flow. Encryption reduces unauthorized access risk, but no technology can guarantee absolute security. Anyone with access to your unlocked device, Google account, recovery password, or encryption keys may be able to access corresponding data.

Protect your Google account and recovery password. Do not share your recovery password with anyone you do not trust.

6. Google and Firebase services

Google Drive and Google Sign-In

Google Sign-In is used to connect the Google account you select. Google Drive is used for app-managed encrypted backup and recovery data. NotiVault's use of information obtained through Google APIs is limited to the disclosed app functionality and is subject to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

Firebase Realtime Database

NotiVault uses Firebase Realtime Database for supported multi-device coordination, device registration/presence, and remote settings or command information. This may include account-linked identifiers, device metadata, settings, and synchronization state. Such metadata must not be assumed to be end-to-end encrypted in the same way as notification backup payloads.

Google and Firebase process data under their own service and privacy terms. See the Google Privacy Policy.

7. Multiple devices and remote features

Devices signed in under a supported account and authorized through the app's recovery and device-management flows may be able to view, restore, or manage data associated with that account. NotiVault includes device-management and relinking features that can affect what backups are available.

Only add devices you own or are authorized to use. Do not use NotiVault to monitor another person's notifications without their knowledge and appropriate permission. A shared Google account or disclosed recovery password can increase the risk that another person may gain access to your backups.

8. Retention, deletion, and Cloud Trash

Local history: Captured history is kept on your device until removed through the app, app data is cleared, or the app is uninstalled (subject to any separate device backups).

Cloud backups: Encrypted backups remain in your selected Google account's application-specific Drive storage until deleted using supported app controls, the relevant Google storage is removed, or other account/service actions affect availability.

Cloud Trash: For supported deletion flows, NotiVault first attempts to preserve affected notification records in encrypted Cloud Trash. Trash items are intended to remain recoverable for up to 30 days before expiration and cleanup. Deletion or cleanup can depend on network availability and successful synchronization. Do not assume a local deletion immediately removes every cloud copy.

Delete options: The app provides local-only, cloud-only, and combined deletion functions, with scopes that may differ between device-level and all-cloud actions. Read each confirmation screen carefully. Recovery password confirmation may be required. Some metadata needed for synchronization, duplicate prevention, and device retirement can remain after individual notification records are deleted.

Disconnecting your account or uninstalling: Disconnecting Google access or uninstalling the app does not necessarily delete previously uploaded encrypted files from Google Drive. Use the applicable in-app deletion controls and account settings to manage remaining cloud data.

9. Your privacy choices

  • Enable or disable Android Notification Access.
  • Use app-level smart filters and app exclusions to limit captured notifications.
  • Choose whether to connect a Google account and enable automatic cloud backup.
  • Review available device backups, restore data, and use supported deletion and Cloud Trash controls.
  • Disconnect or change the selected Google account.
  • Manage device access and protect or change your recovery credentials using supported app flows.

For a request concerning stored information or a privacy issue not covered by the available controls, contact the developer using the contact details below.

10. Disclosure and sharing

NotiVault's described backup functionality transmits data to Google services at your direction or according to features you enable. Firebase processes device and synchronization metadata used to provide the service. NotiVault is not designed to sell notification contents or use them for targeted advertising. Disclosure to service providers is distinct from publishing or publicly sharing your notifications.

We may need to disclose information if required by applicable law. Any additional analytics, crash-reporting, advertising, or other third-party integrations present in a published app version must be accurately disclosed here and in the Google Play Data safety section.

11. Children's privacy

NotiVault is a general-purpose notification utility and is not specifically designed for children. Parents or guardians should consider the sensitivity of notification content before permitting access on a minor's device.

12. Changes to this policy

We may update this policy when app functionality, services, security practices, or applicable requirements change. The effective date shown at the top will be updated when a revised policy is published. Material changes should be communicated through appropriate app or website notices.

13. Contact and privacy requests

Application: NotiVault

Developer / publisher: [INSERT EXACT GOOGLE PLAY DEVELOPER NAME]

Privacy and support email: [INSERT WORKING SUPPORT EMAIL]

Website: https://notivault.everylock.app/

Developer publishing checklist: Replace both bracketed contact placeholders with true information before posting this policy publicly. Verify actual SDKs, Firebase payloads, permissions, storage behavior, Cloud Trash retention, deletion capabilities, and any account creation/deletion functionality against the release APK. Update claims that differ from shipped code. This box is a pre-publication reminder and should be removed before publishing.