There is no server, so there is very little to explain.

Diplina has no account, no cloud and no analytics. It stores what you type on the device you typed it on. This page explains exactly what that means, and the few cases where something does leave your phone — every one of which you start yourself.

Last updated: 1 October 2026

The short version

We collect nothing. There is no analytics, telemetry or crash reporting in the app.
There is no account and no sign-in, because there is nowhere to sign in to.
Your habits, goals, notes and attachments stay in the app's private storage on your device.
Diplina's own Android manifest requests no internet access. The permission list shown on Google Play is longer, because the store's billing library contributes it. The only network traffic is the store's own: the Pro purchase, and on Android Google Play's check for a newer version of the app. None of your data is part of either.
Data leaves only when you send it: a backup or export, an attachment opened in another app, a note shared through your phone's share sheet, or an email you write to us.
Buying Pro is handled entirely by Apple or Google. We never see your payment details.

Who is responsible

Patrick Schad, Hamburg, Germany — the controller within the meaning of Art. 4(7) GDPR. The full postal address and contact details are in the Impressum. For anything on this page, write to hi@diplina.app.

What the app stores, and where

Everything you create lives in Diplina's own private storage — a local database on Android, a local file on iOS — which other apps cannot read. None of it is transmitted to us or to anyone else, because the app has nowhere to transmit it to.

What	Stays where
Habits, schedules, reminder times	On your device
Check-offs, streaks, time-spent notes	On your device
Goals, decisions, notes and checklists	On your device
Spaces and their settings	On your device
Themes and app preferences	On your device
Attached images, videos and files	On your device — see below

Excluded from system backups, deliberately. On Android the app sets allowBackup="false"; on iOS every stored file is marked isExcludedFromBackup, re-applied after each write and read back to confirm it held. Your habit data is therefore not copied into Google or iCloud backups. The trade-off is real and worth knowing: restoring a phone will not bring Diplina's data back. Your own export file is the way to move to a new device, which is why the app reminds you to make one.

Attachments

You can attach an image, a video or any file to a habit, goal or decision. Diplina either remembers where the file is, or — if you allow it — keeps a private copy inside the app so the attachment survives you moving or deleting the original. You are asked once, and can change the choice in Settings at any time.

Copies live in app-private storage, are excluded from system backups like everything else, and are deleted when nothing refers to them any more. Opening an attachment hands it to whichever app you choose to open it with — at that point, that app's own privacy policy applies.

When data leaves your phone

Every case is an action you take deliberately. Nothing happens in the background.

1. Backups and exports you create

You can export a JSON backup or a CSV of your completions, and you can switch on automatic local backups. In every case you choose the destination folder, and the file is written there. It is never uploaded anywhere by Diplina. If the folder you pick happens to be synced by another service — a cloud drive folder, for example — then that service, not Diplina, is handling the file from that point on.

2. Sharing a note or opening an attachment

You can share a note or checklist as text, which hands it to your phone's own share sheet — you pick the app it goes to, and from then on that app's privacy policy applies. Opening an attachment works the same way (see above).

3. Emails you write to us

"Send feedback" and "Request a feature" in Settings open a draft in your own mail app, addressed to hi@diplina.app. The feature-request draft ends with the app version and platform, which you can see and delete. Diplina sends nothing itself; the email leaves only if you press send, through your mail provider. We use what you write only to answer you and to improve the app, and delete it when it is no longer needed for that.

4. Buying Diplina Pro

Pro is a single one-time purchase, never a subscription. It is processed entirely by the App Store or Google Play. We never receive your name, address or payment details — only whether this device owns the purchase, which the store tells the app. Refunds, receipts and payment questions are handled by Apple or Google under their own privacy policies.

The store's code is the only part of the app that reaches the network. Diplina itself declares no internet permission on Android; Google Play's billing library talks to the store for the purchase — the same code Apple and Google ship in every paid app. On Android, the app also asks Google Play's in-app update service, through the Play Store app on your phone, whether a newer version of Diplina exists, so it can offer the update. That check carries no data of yours. On iPhone the App Store handles updates itself, and StoreKit handles the purchase.

Notifications

Reminders are scheduled and delivered by your phone's own operating system, locally. There are no push notifications, which means no push token, no notification server, and nothing to register with. If you deny or revoke the notification permission, everything else in the app continues to work.

What we do not do

No analytics or usage measurement of any kind.
No crash or error reporting SDK.
No advertising, ad identifiers or tracking pixels.
No profiling and no automated decision-making under Art. 22 GDPR.
No cookies — the app is not a web view and this site sets none.
No data sold, shared or transferred to third parties, in the EU or outside it.

These are enforced by the build, not just promised here: an automated test fails the build if the internet permission appears, if the backup flag changes, if an analytics or ad dependency is added, or if the purchase is ever turned into a subscription.

Your rights under the GDPR

You have the right to access, rectify, erase, restrict and port your data, and to object to processing (Art. 15–21 GDPR). In Diplina's case these are unusually direct, because we hold nothing:

Access and portability — export a JSON or CSV file from Settings at any time. That file is the complete record.
Rectification — edit or delete any entry in the app.
Erasure — deleting the app removes its data from the device. There is no copy on our side to request the deletion of.

You also have the right to complain to a supervisory authority. For Hamburg this is the Hamburgische Beauftragte für Datenschutz und Informationsfreiheit.

This website

diplina.app sets no cookies, runs no analytics or tracking scripts, and makes no third-party requests at all. The fonts and images are served from diplina.app itself rather than from Google Fonts or a CDN, so your browser never contacts another company's server while reading this site — not even to render the type.

As with any website, the hosting provider may keep short-lived server logs (IP address, timestamp, requested page) for security and operations. That is the only processing that happens here, and it is not linked to anything you do in the app.

Children

Diplina is a general-audience app and is not directed at children. Since it collects no personal data at all, no age verification is required or performed.

Changes to this policy

If a future version of the app changes anything described here — a new feature that needs the network, for example — this page will be updated before that version ships, and the date at the top will change with it.