Clovie
Privacy
Clovie, a calendar and shared space for two people.
Clovie is a calendar, a shopping list, a recipe book, a training log and a cycle tracker for two people.
Everything the two of you put in stays on the phone it was typed on until one of you signs in. The shared account is optional, and without it nothing the two of you write is kept anywhere but the phone.
With the shared account, what the two of you write is also held in a database run by Firebase, a Google service, in Europe. That is what lets both phones show the same things, and what brings everything back when a new phone signs in. Only your two accounts can read it, the database enforces that rule itself, and nobody at this end has another way in. Nothing is sold, and nothing watches how you use the app.
Three things go outside the app whether or not you sign in, each only at the moment you ask for it. Looking a food up sends what you type in the search box, or the barcode you scan, to Open Food Facts, the free public database the nutrition figures come from. Tapping the place written on an event hands that place to the phone's maps app, or to Google Maps in a browser when there is no maps app. Sharing your join code hands that code, inside a clovie.eu address, to whichever app you pick to send it with. Each sends those words and nothing else, and none of them carries your name or your account.
Cycle entries are stored and synced the same way as everything else here, a shopping list or a training log, with no separate encryption or access control set aside for them.
Signing out keeps everything already on this phone and stops anything more from travelling.
A copy you save goes wherever you choose to put it. From that moment it is an ordinary file on your phone or your drive, under whatever protection that place gives it, and the app has no further say over it.
If you let the app read the calendars already on the phone, it only reads them. Those events are shown next to yours and are never changed, never deleted and never written back. If you turn on sharing for one of those calendars, copies of its events are stored and synced the same way as events typed in here, and are removed again when you turn sharing off.
Reminders are set on the phone itself, so the time you pick is known to Android and to nothing else.
Erasing everything removes it from this phone for good, and from the shared space and the other phone when the two are paired. For about three months the shared space keeps a blank note in place of each removed row, holding nothing readable, which is how a phone that was off learns about the removal, and then the notes go too. A copy saved earlier is left alone, because by then it belongs to the folder it was put in rather than to the app.
Deleting your account, instead of just erasing what is on this phone, removes your sign-in for good. Your own seat in the shared space goes with it, right away rather than after the three months above. If someone is still paired with you, the calendar, list, recipes and everything else you both wrote stay exactly as they were for that person. Only your own seat and the sign-in behind it are removed. More on how to delete an account.
This website
The pages at clovie.eu use Cloudflare Web Analytics to count visits, see which pages are useful and measure page performance. This is separate from the Clovie app: the app contains no analytics code, and none of your calendar, list, recipes, training or cycle data is sent to it.
Cloudflare Web Analytics uses no cookies, browser storage or fingerprinting. It reports aggregate page views, referring sites, approximate countries, browser and device categories, and performance timings. Cloudflare discards the visitor's IP address at its edge and does not give Clovie an identifiable browsing history.
What the app asks the phone for
| Permission | Why | Without it |
|---|---|---|
| Internet | To reach the shared account, so both phones hold the same things | Without the shared account it sits unused |
| Calendars | To show events already on the phone next to your own. Android grants reading and writing as one permission, and the app only ever reads | The rest of the app works, that overlay is empty |
| Notifications | To ring at the time you set on an event | Events still save, they do not ring |
| Run after restart | So reminders already set survive the phone restarting | A reminder set before a restart is lost |
| Camera | To scan a barcode when logging food | You can still type the barcode's numbers in instead |
Nothing is asked for at startup. Each one is asked for the first time you use the thing that needs it, and saying no leaves the rest of the app alone. The internet permission is the one exception, Android grants it with the install, and nothing uses it until somebody signs in.
Children
The app is not aimed at children and collects nothing that would identify anybody, here or anywhere else.
Changes
If this ever changes, the wording changes with it in the same release, and the app carries the current version of this page under Us, Privacy.
Contact
Questions go to hello@clovie.eu.
Last updated 18 August 2026.