Privacy
In short
Your habits and check-ins stay on your device. There is no account, no cloud sync, no tracking and no advertising. Two things leave your device: the purchase flow, if you buy Mitia Pro, and an anonymous count that knows the app was opened — not by whom, and not what is in it.
Who is responsible
Stephan Eberle
Bertha-von-Suttner-Str. 27
23843 Bad Oldesloe, Germany
info@mitia.app
Data in the app
Everything you create in Mitia — habits, check-ins, intensities, notes, categories, reminder times — is stored in a database on your device and nowhere else. It is never transmitted, never backed up by me, and I cannot see it. Two settings live in local device storage alongside it: your language choice and whether reminders are muted.
Uninstalling the app deletes this data with it. A device backup through iCloud or Google may include it — that is your choice and falls under Apple's or Google's terms.
Reminders
Reminders are scheduled and delivered locally on your device. No server is involved and there are no push notifications from outside. The notification permission is only requested when you switch a reminder on.
Purchases: Mitia Pro
If you buy Mitia Pro, payment is handled by Apple (App Store) or Google (Google Play). I receive neither your payment details nor your name or address.
To manage your entitlement I use RevenueCat (RevenueCat, Inc., San Francisco, USA). RevenueCat processes:
- a randomly generated, anonymous user ID — tied to no account and to no identity of yours
- purchase and subscription state (which product, valid until when, trial, refund)
- technical details about device and app: platform, OS and app version, country
- your IP address at the time of the request
Your habits and check-ins never reach RevenueCat. The service sees purchases and nothing else.
The legal basis is Art. 6(1)(b) GDPR — the processing is necessary to deliver what you bought and to let you restore purchases. The transfer to the USA relies on the European Commission's Standard Contractual Clauses. RevenueCat's own privacy notice: revenuecat.com/privacy.
If you write to me
The app has a way to reach me under Settings → Contact. It opens your mail app with a template that already contains the app version, build, bundle ID and operating system — which saves me asking which build you are on. You see the mail before you send it and can delete anything from it.
What reaches me is your sender address, your text, and those technical details. None of it is combined with data from the app; that would not be possible anyway, since it only exists on your device.
A mail to info@mitia.app first gets an automatic acknowledgement, so you are not left wondering. The actual reply I write myself. The mailbox and the routine that sends the acknowledgement run on servers of my own; no helpdesk provider reads along.
Legal basis: Art. 6(1)(f) GDPR (answering your enquiry), or Art. 6(1)(b) GDPR for questions about a purchase. I keep the message while the matter is open and delete it afterwards — after twelve months at the latest, unless a retention obligation says otherwise.
Anonymous counts
I count how often Mitia is opened, how many devices are still there after a week, and how many ever see the offer for Mitia Pro. Without those numbers I cannot tell whether the app holds up in daily use or whether the price is right.
No habit and no check-in is part of this. No name leaves your device, no intensity, no timestamp, not even how many entries you have made. Only these events are reported:
- the app was started — and whether it was the first start
- it was opened again one, three, seven or thirty days after installation
- the offer for Mitia Pro was shown, and by which of the three routes
- a purchase or restore succeeded, was cancelled, or failed
- a review was requested
Version, build, platform and whether this is a test build travel along. No identifier does — no device ID, no session, no timestamp per event. The server counts up and forgets; it cannot tell two reports from the same device apart.
So that a device still counts only once as "came back after seven days", the app remembers on the device what it has already reported. That split is exactly why the count works without recognising anyone.
The data arrives on a server of my own — no analytics provider, no SDK, no sharing. Sending it technically transmits your IP address; for this path it is not logged and not stored. Legal basis: Art. 6(1)(f) GDPR (my interest in improving an app I build alone).
This website
The site sets no cookies and embeds no tracking. Requesting a page creates server logs holding IP address, requested path, timestamp and user agent; they serve secure operation and are deleted after seven days at the latest. Legal basis: Art. 6(1)(f) GDPR.
The Quicksand and Nunito Sans typefaces are served from this server. The site loads nothing from third parties, including no fonts from Google.
What does not happen
- no advertising and no advertising identifiers
- no third-party analytics or crash SDKs, no Firebase
- no selling or sharing of data for advertising purposes
- no location, no contacts, no camera, no microphone
- no profiling and no automated decision-making
How long data is kept
| Data | Retention |
|---|---|
| Habits and check-ins | on your device until you delete them or remove the app |
| Purchase state at RevenueCat | for the life of the subscription, then as required by bookkeeping law |
| Website server logs | seven days at most |
| anonymous counts | indefinitely — they are plain sums with no link to you |
| emails to me | while the matter is open, twelve months at most |
Deleting your data
There are two places your data can live, and each has its own way out.
On your device. You delete it yourself, no request needed:
- A single check-in: tap it again to clear it.
- A single habit: open it, choose Archive.
- Everything at once: uninstall Mitia. The database goes with it.
Purchase records at RevenueCat. Write to info@mitia.app with the subject Delete my data and include your anonymous RevenueCat ID — without it a purchase cannot be matched to a request. I answer within 30 days.
What gets deleted: the anonymous user ID and the purchase and subscription records tied to it. What has to stay: transaction records that German bookkeeping law requires me to keep (§ 147 AO, up to ten years). Those are held by Apple and Google as the sellers, not by me, and cannot be deleted on request.
Deleting purchase records ends your access to Mitia Pro and cannot be undone.
Your rights
You have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR). For the data inside the app you do not need me: it sits on your device, and you can change or delete it there at any time — see Deleting your data.
For anything else, a message to info@mitia.app is enough.
You may also lodge a complaint with a supervisory authority. Mine is the Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein, Holstenstraße 98, 24103 Kiel, Germany.
Children
Mitia is not directed at children under 13. I do not knowingly collect data from children.
Changes
If features arrive that process data, I update this notice before they ship.