Last updated: June 2024
At Hush, we believe that your notifications are your business, not ours. Hush is built from the ground up to be a privacy-first, fully offline application. This policy explains our commitment to your data security.
The most important thing to know about Hush is that it does not collect, transmit, or share your data.
No Internet Access: Hush does not request or use the `INTERNET` permission. It is technically impossible for the app to send your data to a server.
No Accounts: There are no sign-ups or logins. We do not know who you are.
No Analytics: We do not use third-party tracking tools like Firebase, Google Analytics, or any other telemetry SDKs.
Hush functions by analyzing notifications as they arrive. This process happens entirely in your device's local memory (RAM):
Real-Time Analysis: Notification content (titles and text) is analyzed strictly to identify "Critical" alerts such as OTPs, banking alerts, or security codes.
No Content Storage: The actual text of your notifications is never saved to a database. Once the filtering decision is made, the content is immediately discarded from memory.
Audit Logs: We save a metadata-only history (App Name, Time, and Filtering Decision). These logs never contain message snippets, contact names, or private content.
Even though your data stays on your device, we protect it as if it were on a high-security server:
Encrypted Database: All local settings, filtering rules, and audit logs are stored in a SQLCipher database using AES-256 encryption.
Android Keystore: The encryption keys are generated and stored within the Android Keystore, a hardware-backed security module.
Biometric Lock: You can optionally enable Biometric Authentication (Fingerprint or Face ID) to prevent anyone holding your phone from opening the Hush app and seeing your audit logs.
We do not share any information with third parties because we never have access to it. Hush is a standalone tool with:
* No Advertisements.
* No Marketing SDKs.
* No Cloud Backups.
Hush requires specific Android permissions to function. We only use them for the following reasons:
Notification Access: To intercept and filter incoming alerts based on your rules.
Use Biometric: To protect access to the app's settings and history.
Query All Packages: To allow you to choose which of your installed apps should be prioritized or blocked.
Foreground Service: To ensure the filtering engine remains active and does not get shut down by the system.
Auto-Cleanup: You can configure the app to automatically delete audit logs after a set period (e.g., 7 days).
Manual Deletion: You can clear all logs at any time within the app.
Uninstallation: Deleting the Hush app will permanently erase all local data, rules, and logs. There is no cloud recovery.
If you have any questions regarding this Privacy Policy, please contact:
Email: cst@ismatapps.fyi
App: Hush
Developer: ismatapps