Privacy Policy
Effective date: 10 November 2026 Last updated: 10 November 2026
Quietly ("we", "us") is a private, end-to-end-encrypted diary. This policy explains what we process, what we deliberately cannot see, why, for how long, who helps us, and your rights. Plain language is intentional: privacy you can't understand isn't privacy.
The short version
- What you write — entries, titles, moments, the day's feeling, photos, voice notes, letters — is encrypted on your phone before it reaches us. We store only ciphertext and cannot read it.
- Your vault PIN and vault key never leave your phone.
- Your phone number is used to send you a sign-in code. We store only a one-way hash of it, never the number.
- Your contacts' numbers are hashed on your phone before matching. We never receive them.
- We don't sell your data, show ads, or profile you.
1. Who is responsible for your data
The controller is Esshva Techq Pvt Ltd (company registration PV 128920), 546/7 Galle Road, Colombo, Sri Lanka — privacy@quietly.today.
- Data Protection Officer: The Data Protection Officer, dpo@quietly.today.
- Representative in the EU (GDPR Art. 27): not yet appointed — write to privacy@quietly.today.
- Representative in the UK (UK GDPR Art. 27): not yet appointed — write to privacy@quietly.today.
2. What we process, why, and on what legal basis
| Data | Why | What we can see | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| Your phone number | To send a sign-in code and recognise your account | Only during sending; we store a SHA-256 hash | Contract (b) |
| Display name, avatar colour, profile picture | Shown to people you share with | Plaintext — they are meant to be shown | Contract (b) |
| Public key | So others can encrypt what they share with you | A public key (not secret) | Contract (b) |
| Diary entries, titles, moments, the day's feeling, photos, voice notes, plans, letters, comments, event titles | Your diary and what you share | Ciphertext only — unreadable to us | Contract (b) |
| Dates and structure: the day an entry is for, when a letter opens, when something was shared, which moments are in the vault, event dates | To sync and deliver at the right time | Yes — dates and counts, never content | Contract (b) |
| Who you share with, invite, react to or comment to (user ids) | To deliver what you share | Yes — the connection, never the content | Contract (b) |
| Contacts' numbers, for finding who is on Quietly | To show which of your contacts use Quietly | SHA-256 hashes only; kept no longer than needed to answer | Consent (a) — only if you allow contacts access; withdraw it any time in your phone's Settings |
| Backup email (optional) | To send a sign-in code when none reaches your phone | The address, encrypted at rest | Consent (a) |
| Recovery escrow (optional) | To restore your keys on a new phone | Ciphertext only — we cannot derive your recovery code | Consent (a) |
| Push notification token | To notify you of shares and replies | A device token from Apple / Google | Contract (b) |
| Passkeys (optional) | Sign-in without a code | A public credential, never your biometrics | Contract (b) |
| Plan and purchase records | To give you what you paid for; tax records | Product, price, currency, store, country, dates — never card details | Contract (b); legal obligation (c) for tax records |
| IP address, device id and request metadata | Security: rate limits and abuse prevention | Yes, briefly — see retention | Legitimate interests (f): keeping the service and your account safe |
Special categories (Art. 9). A diary may hold health, beliefs or other sensitive matters. We cannot read any of it: it is encrypted on your phone with keys we never hold, including the day's feeling. We do not infer anything about you from what we can see.
We do not: read your diary, sell or rent personal data, show ads, use advertising identifiers, profile you, or make automated decisions that have legal or similarly significant effects on you.
3. How the encryption works (so you can check our claims)
- Content is encrypted on your phone with AES-256-GCM. Keys are derived with PBKDF2 and held in your phone's secure storage (iOS Keychain / Android Keystore).
- What you share is encrypted separately for each recipient with their public key.
- Copies waiting for someone who has not joined yet are encrypted under a key only your phone has.
- Optional recovery wraps your keys under a recovery code only you hold; we store the result and can never unwrap it.
- So we cannot recover your diary if you lose both your phone and your recovery code. That is the guarantee, and its cost.
4. Who helps us (processors) and where data goes
We use these service providers, each under a data processing agreement, only to run Quietly:
| Provider | What for | Location |
|---|---|---|
| Amazon Web Services | Hosting, database, storage, SMS codes, email codes | United States (us-east-1) |
| Meta Platforms (WhatsApp Business Platform) | Sending sign-in codes by WhatsApp | Global |
| Apple and Google | App stores, purchases, push notifications, app integrity checks | Global |
| RevenueCat | Confirming purchases (it knows you only by a random account id) | United States |
| Firebase App Check (when enabled) | Checking requests come from the real app | Global |
International transfers. Your data is stored in the United States. Transfers from the EEA, the UK and Switzerland rely on the EU–US Data Privacy Framework where the provider is certified, and otherwise on the European Commission's Standard Contractual Clauses (and the UK Addendum), with the safeguards above: what we hold about your diary is ciphertext we cannot read.
We share data with people you choose (only as ciphertext they can decrypt) and when the law requires — and then we can hand over only what we can see (section 2), never your diary.
5. How long we keep it
| Data | Kept |
|---|---|
| Account, profile, diary ciphertext, shares | While your account exists; deleted when you delete it |
| Database backups | Up to 14 days after deletion, then gone |
| Sign-in codes | 10 minutes (stored only as a hash) |
| IP addresses and device ids for rate limits | Up to 7 days in counters; up to 30 days in security logs |
| Copies waiting for someone to join | Until they join, you take it back, or you delete your account |
| Purchase records | 5 years (Sri Lankan tax law), unlinked from you when you delete your account |
6. Your rights
Wherever you are, you can:
- Access and portability — get a copy of what we hold about you: your diary from the app (Settings → Export, decrypted on your phone), and the rest by writing to us or from Settings → Your data.
- Correct your profile in the app at any time.
- Delete your account in the app (Settings → Delete account). Everything is erased, except purchase records kept as section 5 says.
- Withdraw consent at any time: contacts access in your phone's Settings, the backup email and recovery in Quietly's Settings. This does not affect what was done before.
- Object or restrict — write to us.
If you are in the EEA or the UK you may also complain to a supervisory authority — where you live, work, or where you think the problem happened (in the UK, the ICO). In Sri Lanka, the Data Protection Authority of Sri Lanka.
We answer requests within one month. Write to privacy@quietly.today. Because we cannot read your diary, we cannot search it or hand it over — only you can, from the app.
7. Children
Quietly is for people aged 16 and over (13 and over in the United States and other places where the law allows it). We do not knowingly process the data of younger children; if you believe we have, write to us and we will delete it.
8. Security
End-to-end encryption, TLS on every connection (pinned to our provider's certificate authorities in the app), a private server network, least-privilege access, and redacted logs. No system is perfectly secure, but our design means a breach of our servers does not expose what you write. If a breach puts your rights at risk we will notify the supervisory authority within 72 hours and tell you without undue delay.
9. Changes
We will post changes here and update the date above; important changes are announced in the app first.
10. Purchases
Paid plans are bought through the App Store or Google Play; RevenueCat confirms the purchase to us. We never receive card or payment details. The app identifies you to RevenueCat by a random account id, never your phone number or name. We receive: the product, amount and currency, store, storefront country, and the dates of purchase, renewal, cancellation or expiry.
11. Sri Lanka (PDPA)
Under Sri Lanka's Personal Data Protection Act, No. 9 of 2022, you may ask for access to, correction or erasure of the personal data we hold, and withdraw consent (deleting your account does this completely). Our Data Protection Officer is named in section 1. If a breach is likely to harm you we will notify you and the Data Protection Authority of Sri Lanka as the law requires.
12. Contact
Esshva Techq Pvt Ltd (Reg. No. PV 128920), 546/7 Galle Road, Colombo, Sri Lanka — privacy@quietly.today