Diarion Privacy Policy
In short
Diarion has no accounts, no servers and no sync. Your diary is stored on your device and is not sent to the developer or to anyone else. We collect no usage statistics, show no ads, and bundle no analytics or advertising SDKs.
What the app stores
All of the following lives only in the app's storage on your device:
- diary entries, mood, reflections, notes and tags;
- habits, tasks and planner events, wishlist, good deeds, happy moments;
- financial transactions, accounts, budgets;
- cycle tracker data and its symptoms;
- sleep times and how you felt, exactly as you typed them;
- profile: name, gender, date of birth (optional — used only to show the sections that have an age: intimate life from 18, the cycle calendar from 14), weight, height;
- settings: theme, language, currency, PIN, quick-menu order.
The database is encrypted on disk. The encryption key is generated on your device and held in the system keystore (Keychain on iOS, Keystore on Android); the developer does not have it and cannot obtain it. The PIN is stored as a hash, not as a number.
Where data can go — and only if you send it
- Backup. You create it. The file is encrypted with a key derived from your passphrase via PBKDF2 — not with the device key — and handed to the system share sheet, where you pick the destination. The app never stores the passphrase: lose it and nobody can open the backup, the developer included.
- Export. JSON, CSV and Markdown are produced locally and handed to you the same way.
- Crash report. If the app crashed, the last exception is written to a local file and the Data tab offers to send or delete it. Nothing is sent automatically.
Health
The app connects to neither Apple Health nor Google Health Connect and reads nothing from either. Sleep times, how you felt and any symptoms are what you typed yourself, and they stay in your local database.
Subscription and purchases
The subscription is bought and paid for through the App Store. Apple processes the purchase under its own privacy policy; the app sees neither your payment method nor your payment details, nor the name or address of your Apple ID.
From the system the app learns only what it needs to open or close writing: whether there is an active subscription, until when, and whether it will renew — and, to tell apart first-version users, who have free months, which version of the app your Apple ID downloaded first. This is kept in the system keychain on the device, never enters the database, backups, exports or crash reports, and is sent nowhere. The terms of the subscription itself are on the terms of use page.
Network
The app makes no network requests of its own: no telemetry, no update checks, no ads, no downloads. None of your entries, no diary text and no identifier are transmitted anywhere.
The one network connection connected with the app is checking and buying the subscription, and iOS itself makes it through the App Store; the app makes no requests of its own for it.
On Android the internet permission remains declared from earlier versions, which could download a language model; nothing in the app uses it now.
What there isn't
- No accounts, no registration.
- No Diarion servers — data cannot be sent anywhere because there is nowhere to send it.
- No analytics, crash analytics, A/B tests or advertising identifiers.
- No sharing with or selling to third parties.
- No cross-app tracking (App Tracking Transparency is not used, because there is nothing to track).
Your rights
The data is in your hands, so the rights are exercised in the app rather than by writing to the developer: to view it, open the app; to obtain a copy, use Export or Backup; to delete it, delete the app (its storage goes with it), tap “Delete all my data” in settings, or delete the individual entry. On Android, cloud backup is disabled in the manifest, so your diary does not end up in a Google backup.
Children
The app is not directed at children and collects no data, therefore it collects none from children.
Changes
A new version is published at this same URL with a new effective date. If a change involves sending data off the device, the app will ask for separate consent before the first such transmission.