Get the app
← Back to Complevia

Privacy Policy

Last updated: 16 September 2026. Applies to Complevia for Android v1.4.0, to the counter behind the Complevia Mini App in Telegram (section 4), and to this website, complevia.fyi.

The short version: the habits you create, your schedule and your completion history are stored on your device and are not uploaded anywhere. Three things in the app use the network, and all three are named below — the update check (only in the copy installed from this site), the daily ad, and the optional Telegram link. This website counts its visitors in two ways, both named in section 9. Nothing here is written to make the app sound better than it is.

1. Data we collect

We ask you for nothing. The app needs no account, no email address and no name to function, and there is no sign-up step. We operate no server that receives your habits unless you choose to connect Telegram (section 4).

The app counts itself, with a number it made up about itself. From version 1.4.0 onwards, the copy you installed directly from this site generates a random identifier on first launch and sends it with the update check it already makes. It exists for one purpose: so we can tell how many people installed Complevia and stopped opening it. It is not your Android ID, not the advertising ID of section 3, and is not derived from your phone, your habits, your language or anything else about you — it is a random number and nothing more. It authorises nothing, it is never sent with your habits, and clearing the app’s data destroys it. We delete any identifier that has not been seen for 180 days. The Google Play copy of the app does not send it, because it makes no update check at all.

Google does receive one identifier, because the app shows an ad. Requesting that ad hands Google your Android advertising ID, which counts as personal data under the GDPR and the CCPA. We never see it, and your habits are never part of the request — but it leaves your phone, so saying "no personal data is collected" would be false. Section 3 explains exactly what happens and how to reset that identifier.

2. Data stored on your device

Complevia stores the following locally, using SQLite (Room) and Android DataStore:

  • Recurring actions you create — title, category, schedule, time window, completion type
  • Completion history and per-habit stats — streak count, weekly completion rate, timestamps
  • App preferences — notification settings, prompt style, language, snooze interval
  • An onboarding-completion flag

This data is not transmitted to a server, cloud storage or third party — unless you connect Telegram, which is covered in section 4.

3. Advertising

Complevia displays ads through Google AdMob. The app shows one full-screen interstitial per calendar day, after the first action you complete that day, and does not show a second one before midnight.

Requesting an ad involves a network call to Google, and AdMob may collect device identifiers — including your Android advertising ID — and usage data, in accordance with Google's Privacy Policy. Your habits, schedule and history are not part of that request.

You can change this in Android under Settings → Google → Ads, where the advertising ID can be reset or deleted. Doing so does not remove the ad; it stops it being personalised.

4. Telegram (optional, off by default)

Complevia can be linked to a Telegram account so that the same habits appear in a chat and reminders can be answered there. This is off until you turn it on. Once connected, your habit titles, schedules and completion events are sent to the Complevia server so that both surfaces show the same data, together with the Telegram account identifier needed to deliver messages to you.

If you never connect Telegram, no habit data of yours reaches that server.

The Mini App’s counter. To learn whether the Complevia Mini App in Telegram helps anyone, our server counts a few things there on our own Umami server: app launches, habits created, habits that could not be created, and days closed in the app, with your language and the kind of schedule. It never receives your Telegram account, your name or anything you wrote. To tell one visit from another it is given your network address and browser name; it stores neither, only what it works out from them (the type of device and browser and a rough location: country, region, city). It sets no cookie, stores nothing on your phone, recognises a returning visit for one month at most, and nothing it collects is shared with anyone. The Mini App and the bot send nothing to Google. This website’s own counters are described in section 9.

5. Working offline

Every feature that concerns your habits — scheduling, notifications, escalation, snoozing, history and stats — works with no network connection at all. With the network off, the daily ad simply fails to load and the app carries on.

6. Permissions

  • POST_NOTIFICATIONS — to deliver reminders when an action is due.
  • SCHEDULE_EXACT_ALARM and USE_EXACT_ALARM — to fire a prompt at the scheduled moment rather than whenever the system next feels like waking the app.
  • RECEIVE_BOOT_COMPLETED — to reschedule pending reminders after the device restarts.
  • VIBRATE — for notification vibration, including the heavier patterns used by the escalation channels.
  • INTERNET and ACCESS_NETWORK_STATE — used only by the update check described in section 1 (in the copy installed from this site) and the two features described in sections 3 and 4.

No permission gives the app access to your contacts, camera, microphone, location or files.

7. Children's privacy

Complevia is not directed at children under 13, and we do not knowingly collect any information from children.

8. Changes to this policy

If this policy changes, the new version is posted here and the date at the top is updated.

9. This website

This section is about complevia.fyi itself, not the app. The site counts visits in two ways, and the banner at the bottom of the page names both.

Our own counter. We run Umami on a server we operate ourselves; nothing it records is sent to a third party. It sets no cookie and stores nothing on your device. For each page view it records the page’s address without anything after ? or #, the page title, the website you came from (the site only, never the full address), your browser’s language, your screen size, and the browser, operating system, device type and approximate location (country, region, city) worked out from the request. When you press a download or Telegram button it also records which of the two you pressed and the page’s language — never anything you typed. To recognise a returning visitor without a cookie it combines your IP address and browser identifier with a secret that changes every month, so the same visitor can be recognised within a month and not beyond; the IP address itself is not stored. It never receives a name, an account, a Telegram identifier or anything from the app.

This counter runs for visitors who have not answered the banner, because it stores nothing on their device. “No thanks” stops it. Your answer is remembered in this browser’s local storage; if your browser blocks site storage, the answer applies to the page you gave it on and the banner asks again on the next one.

Google Analytics. Every page also loads Google Analytics with Google’s consent mode set to “denied”. In that state it stores no cookie on your device, though Google may still receive cookieless signals about the visit. Only if you press “Accept” does it store analytics cookies; “No thanks” keeps them off. What Google does with that data is described in Google’s Privacy Policy.

To change your answer, clear this site’s data in your browser; the banner will ask again.

10. Contact

Questions about this policy go to support@complevia.fyi, which is read by the person who wrote the app.