makiolaj
6f69a33514
Reverses yesterday's framing. The policy is reviewed here like any other change; the Astro page holds no prose of its own — the website build checks this repository out beside itself and renders this file through a content collection, so there is one copy of the text anywhere and drift is impossible rather than merely detectable. Both app repos are public on Codeberg, so the site needs no token to read them and nothing has to run on the Codeberg side.
3.3 KiB
Agendula — privacy policy
This file is the policy. Edit it here, in a PR, reviewed like any other change — it is the source of truth.
It is published at https://jeanlucmakiola.de/agendula/privacy, which is what the app's Settings → Privacy policy row opens and what the Play Console field must hold. That page holds no copy of the prose: the website build checks this repository out beside itself and renders this file through an Astro content collection, so there is exactly one copy of the policy anywhere and the two cannot drift. An edit here reaches the live page on the site's next build.
Last updated: 2026-09-07.
Agendula is a task app for Android, published by Jean-Luc Makiola. This policy describes what happens to your data. It is short because very little happens to it.
The short version
Agendula has no servers. There is no Agendula account, no analytics, no advertising, no tracking and no third-party SDK that reports anything anywhere. Your tasks live on your device, and — only if you set that up yourself — on a CalDAV server you choose.
What is stored on your device
- Your task lists, tasks, reminders and app settings.
- If you add a CalDAV account: the server address, your username, and your password or app password. The password is encrypted with a key held in the Android Keystore, which cannot be exported from the device.
What leaves your device
Only if you add a CalDAV account, and only to the server you entered:
- Your tasks in those lists, as iCalendar data, and the credentials needed to authenticate.
- Requests are made over HTTPS. Cleartext HTTP is refused unless you explicitly opt in for a specific account.
Nothing is sent anywhere else. In particular, nothing is sent to the developer.
Under Google Play's Data Safety definitions this counts as collected — Play defines collection as transmitting data off the device, regardless of who receives it — and not shared, because the only recipient is the server you nominated. Data is encrypted in transit.
Your CalDAV provider has its own privacy policy, and your data on their server is governed by it. Agendula has no relationship with them.
Crash reports
If the app crashes, it can show you the report and ask whether to send it. It is never sent without you choosing to send it, and you can read the whole report first.
Backups
If Android Auto Backup is enabled on your device, your tasks and settings may be backed up to your own Google account. Two things are deliberately excluded: your stored CalDAV password, and Agendula's per-device sync bookkeeping.
Deleting your data
- Remove a CalDAV account from Settings → Accounts. This deletes the stored credential and, where the server supports it, revokes the app password. Task lists become device-only lists rather than being destroyed.
- Remove an account and delete its local data removes the lists and tasks as well.
- Uninstalling the app removes everything Agendula stored on the device.
Deleting data from your CalDAV server is done on that server.
Children
Agendula is not directed at children and collects nothing about anyone.
Changes
Material changes will be noted here with a new date at the top. The history of this file is public in the repository.