Privacy Policy
Last updated: August 13, 2026
In short
Divit keeps your agenda on your device. What you write never leaves it except through a cloud backup, and that only happens when you tap to start one. No ads, no advertising trackers. The app does measure how it is used and does report its own crashes — the section below says exactly what that covers, and what it never touches.
Here’s the long version — what the app does with your data, and what this website does with the email address you might give it.
Your data in the app
Every piece of agenda data in Divit — your projects, entries, dates — lives in a local SQLite database on your device. The app works fully without an internet connection; offline is the default, not a fallback mode.
Backing up to a file
You can back up your data to a file whenever you like. This is entirely optional and only happens when you start it — the file is saved wherever you choose on your device. Divit doesn’t send that file anywhere else.
Cloud backup
Once you’ve signed in with your Google account, Divit offers a cloud backup. This runs only when you tap something like “Back Up to Cloud” — there’s no automatic, background, or silent backup.
When you tap it, your agenda data is compressed and written to Firestore (Google’s cloud database) at backups/{your-user-id}. Security rules restrict that location so only you, signed in, can read or write it — no other user, and not us either, can see your backup.
Signing in
You can sign in with Google, with Apple, or with an email address and password. Whichever you choose, Divit receives your email address and a user ID (uid) through Firebase Authentication. That’s all it’s used for: linking your cloud backup to your account.
If you use Sign in with Apple and choose to hide your address, we only ever see Apple’s relay address (@privaterelay.appleid.com). If you sign in with an email address and password, the password is hashed and stored by Firebase — the app never writes it anywhere.
Signing in is optional. Divit works completely without an account; you only need one to keep a copy in the cloud.
Analytics and crash reports
Divit uses Google Analytics for Firebase and Firebase Crashlytics. That means two things leave your device:
- How the app is used — which screens are opened, and roughly how often. Firebase also assigns an installation identifier so repeat visits from one install can be counted.
- Crash and performance reports — if the app crashes, the technical details of that crash (the stack trace, the device model, the OS version).
What never leaves your device: the contents of your agenda. No entry title, note, project name, date or reminder is ever sent to either service. Crash reports carry the code path that failed, not the data being handled.
There is no ad network and no advertising identifier. Nothing collected is sold, shared with third parties, or matched against data from other companies — which is why the app does not ask for tracking permission on iOS.
Crash reporting is switched off in development builds, so only real crashes from released versions are recorded.
Notifications
Reminder notifications are scheduled entirely on your device. Sending one doesn’t send any data to a server.
What this website collects
This website — the page you’re reading — is a separate thing from the Divit app, but we’ll be just as upfront about it.
The email address you enter in the “notify me” form on the homepage is stored in Firestore for exactly one purpose: letting you know when Divit launches. It isn’t shared with anyone else, added to a marketing list, or used for anything beyond that.
The site doesn’t use cookies, doesn’t run analytics, and doesn’t track visitors.
Hosting
Both the app’s cloud backup infrastructure and this website run on Firebase — Google’s servers. As the infrastructure provider, Google may keep standard server access logs (things like IP address and timestamp). That’s not tracking added by Divit or by us; it’s just how any web server operates.
Deletion — a gap we’re being upfront about
We want to be honest here: Divit currently has no feature that lets you delete your cloud backup yourself. Signing out doesn’t delete it either — the backup stays in Firestore.
You still have the right to request deletion of your data under GDPR and similar laws, whether or not the app’s interface offers a button for it yet. If you’d like your cloud backup deleted, email us at the address below and we’ll handle the request manually.
Adding a “Delete Cloud Backup” button inside the app is on our list as separate work — we’ll update this section once it ships.
Contact
For privacy questions, deletion requests, or anything else: