There is no Hush account to delete
Hush does not require account creation or maintain server-side user accounts. You can still delete local data and request deletion of information you have sent to us.
Clear browsing data
- In Hush, open More → Settings → Clear browsing data.
- Select cookies/site data, cache and, if available, history. History is not selected by default.
- Confirm the clear action. You may be signed out of websites.
- Remove bookmarks separately in Bookmarks. Close all private tabs to end the private session.
Private files, downloads and exports
Open Private files, unlock the vault, select a file and confirm Delete. Clearing browsing data does not erase your vault. Remove downloads and exported copies separately using Android Files/Gallery. Imported originals may also remain in their original location.
Remove all local app data
Use Android Settings → Apps → Hush → Storage → Clear storage/data, or uninstall Hush. Menu names vary by device.
This also removes vault files and unlock material. Export anything you want to keep first; exported copies are outside vault encryption. This does not delete previously transmitted information or files in your public Downloads folder.
Request deletion of information held by the developer
Create a data deletion request or email mrtckr.developer@gmail.com. Include the email used for previous correspondence, the information to delete and its approximate date. Do not send identity documents, passwords or your vault code.
For assistant-related requests, include the approximate time and what you want deleted; you do not need to resend sensitive page content. We may ask for limited information to locate the data or verify the request. Because there is no account, we may not be able to associate every assistant request with an email address. We handle requests within applicable legal time limits and explain any required retention or provider limitations.
Closing the assistant does not erase previous requests from providers. Clearing local browsing data also does not erase previously transmitted Firebase analytics or crash reports. See the privacy policy for retention and service-provider details.