Privacy Policy — Quietbook
Last updated: 2026-09-24
Last updated: 2026-09-23
Quietbook is a journaling app published by LeadRescue LLC. This policy is short because there isn't much to say: Quietbook does not collect, transmit, or share your data, and the app is technically incapable of doing so.
The short version
- No account, no sign-up, no email address, no phone number — ever.
- No network permission in the app at all. Quietbook cannot connect to the
- Your entries are encrypted on your device using a key derived from your own
- Backups are created only when you choose to create one, and are written
- No analytics, no crash reporting, no advertising SDK of any kind is
internet even if it wanted to.
passphrase (and optionally protected further by your device's fingerprint/ face unlock). We never see this passphrase, this key, or your entries.
only to a location you choose using Android's own file picker. Quietbook does not upload backups anywhere itself.
included in the app.
Why we can make these claims literally, not just as policy
Most privacy policies are promises about what a company chooses to do with data it is technically capable of collecting. Quietbook is different: its AndroidManifest.xml does not request the INTERNET permission, and does not request ACCESSNETWORKSTATE. On Android, an app without the INTERNET permission is blocked by the operating system itself from opening any network socket — this is enforced below the level of our own code, by the same sandboxing mechanism that keeps apps from reading each other's files. There is no server for Quietbook to send data to, no API endpoint, no SDK phoning home, because the app has no path to the network in the first place. You do not have to trust our intentions on this point — you (or anyone) can inspect the app's manifest and permission declarations, or simply observe that Quietbook cannot be granted a network permission through Android's settings, because it never asks for one.
What data Quietbook stores, and where
Quietbook stores your journal entries (title, body text, mood tag, tags, pin status, and timestamps) in a database file inside the app's private storage on your device. That database is encrypted at rest using SQLCipher (AES-256), keyed by a value derived from your passphrase and/or your device's biometric hardware. Nobody — including LeadRescue LLC — can read this file without your passphrase or your unlocked device, because we never receive a copy of it and never receive your passphrase.
Some non-sensitive app preferences (whether you've completed onboarding, whether biometric unlock is enabled, your auto-lock timeout) are stored separately in ordinary app preferences. These preferences never contain journal content, your passphrase, or key material.
Backups
If you use Settings > Export encrypted backup, Quietbook encrypts a copy of your entries (using a passphrase you enter at export time) into a single file, then hands that file to Android's system "Save to..." picker. You choose the destination — Google Drive, Dropbox, an SD card, a USB drive, email to yourself, or anywhere else your device offers. Quietbook does not call any cloud provider's API directly, does not know where you saved the file afterward, and does not automatically back up or sync anything on its own. Import works the same way in reverse, via Android's "Open" picker.
What we do not do
- We do not collect your journal entries, titles, tags, or mood data.
- We do not collect your passphrase or biometric data (biometric matching
- We do not use analytics, crash reporting, or advertising SDKs.
- We do not have user accounts, so there is no account data to store, sell,
- We do not sell or share any data with third parties, because we do not
happens inside Android's own secure hardware; Quietbook only ever receives a yes/no "authenticated" result and a cryptographic key it already possesses in wrapped form).
or lose in a breach.
collect any to begin with.
Children
Quietbook is not directed at children and does not knowingly collect any information from anyone, of any age, because it does not collect information from anyone at all.
Changes to this policy
If this policy ever changes, the "Last updated" date above will change, and the new policy will be included with the app update. Any change that would add network functionality would be a fundamental change to the product and would be called out explicitly and prominently — it is not something we plan to do.
Contact
Questions about this policy can be sent to the developer contact address listed on Quietbook's Google Play Store listing.