Lido

Privacy policy

Effective 16 September 2026 · Applies to Lido for Android, version 1.0.0

The short version

Lido has no account and no cloud for your drinks. Hydration data is written to your phone's own storage and stays there until you export it or delete it. Nobody, including us, can see it. Internet access exists only so the app can open optional pages later; it is not used to upload your history. The one other case worth knowing about is Android's own backup, covered in section 5.

1. Who this is from

Lido ("the app") is an independent Android application. In data-protection terms the person responsible for it is its developer, reachable at [email protected]. Because the app processes no personal data on our side, there is no database of users for us to hold, search or hand over.

2. What we collect

Nothing. Concretely, Lido does not:

  • ask for your name, email address, phone number or date of birth;
  • create an account, profile or user identifier of any kind;
  • include advertising, ad networks or ad identifiers;
  • include analytics, telemetry, crash reporting or attribution SDKs;
  • read your contacts, photos, files, location, calendar or other apps' data;
  • send your hydration data anywhere.

There is no opt-out to find in the settings, because there is nothing to opt out of.

3. What the app stores on your device

Everything Lido remembers lives in its own private storage on your phone, in a database and a small preferences file that other apps cannot read:

  • Drinks — the amount, the time you logged it, the drink type, and the note you typed if you added one.
  • Daily goals — your current goal, plus the goal each past day had, so changing it doesn't rewrite your history.
  • Containers — the presets you've named and sized.
  • Check-ins — the mood you tap on the Today screen, if you do.
  • Achievements — which ones you've unlocked and when.
  • Settings — units, theme, haptics, and your reminder interval and active hours.

None of this is transmitted. It is not encrypted beyond the whole-device encryption Android already applies, so it is protected by your device's lock screen rather than by a password of its own.

4. Permissions, and why

Lido asks for four permissions. Three more are added automatically by the Android libraries it is built on; they are listed too, because a permission viewer will show you seven and an honest policy should explain all of them.

PermissionWhy it is there
INTERNET So the app can open optional in-app pages (help, this policy, and a future WebView). Core tracking works with no connection. Lido does not upload your drinks, settings or check-ins.
POST_NOTIFICATIONS To show reminders. Android asks you first, and declining costs you nothing but the reminders — the rest of the app works normally and will not ask again.
VIBRATE The short haptic tap when you log a drink or reach your goal. Can be switched off in Settings → Appearance.
RECEIVE_BOOT_COMPLETED So your reminder schedule is restored after you restart your phone, change time zone, or update the app.
WAKE_LOCK
ACCESS_NETWORK_STATE
FOREGROUND_SERVICE
Added by Android's WorkManager library, which Lido uses to schedule reminders. They are not used to send your hydration data anywhere.

Offline still means offline. Having INTERNET lets the app open a page when you ask it to. It does not create a Lido account, sync, or analytics pipeline. Your drinks stay in local storage unless you export them or Android's own backup (section 5) copies them into your Google account.

5. Android's own backup

This is the one place your Lido data can leave the device, and it is worth being precise about. Lido allows Android's standard backup, which means:

  • If you have backup to Google Drive switched on for your device, Android may include Lido's database and settings in that backup. It goes to your own Google account, under Google's terms, and is used to restore the app if you switch phones or reinstall.
  • If you use device-to-device transfer when setting up a new phone, Lido's data can be copied across as part of it.

In both cases the transfer is performed by Android, not by Lido, and we have no access to it. If you would rather it did not happen, turn off backup for your device in Settings → Google → Backup, or exclude Lido there if your phone offers per-app control. You can also simply uninstall and reinstall, which leaves nothing behind locally.

6. Exports and backups you make yourself

Lido can write a CSV of every drink or a complete JSON backup. When you do that, the file is saved wherever you point Android's file picker — your phone's storage, an SD card, or a cloud folder if that is the destination you choose. From that moment the file is an ordinary document under your control, and its privacy depends on where you put it. Lido does not upload it, keep a copy, or remember what it contained.

7. Deleting your data

  • In the app: Settings → Export and backup → Delete all Lido data. This removes every drink, setting and achievement from the device. There is no cloud copy, so it cannot be undone — export a backup first if you want to keep it.
  • Uninstalling: removes the app's storage along with it. If Android's backup is enabled, a copy may remain in your Google account until it expires or you delete it there.

Because we hold no data about you, there is nothing to request, correct or erase on our side — the rights you would normally exercise against a company are ones you can exercise directly, on your own phone, without asking anyone.

8. Children

Lido is a water-tracking app suitable for general audiences. It collects no data from anyone, of any age, and contains no ads, purchases, social features or external links to unmoderated content.

9. Google Play

Lido will be distributed through Google Play. The store itself is Google's, and your download, purchase history and any crash reports you have agreed to share with Google are handled under Google's privacy policy, not this one. That is outside the app and outside our control.

10. Third-party code

Lido is built on Android's Jetpack libraries — Compose, Room, DataStore, WorkManager, Navigation, Glance and Hilt — all licensed under the Apache License 2.0. None of them is an advertising, analytics or tracking SDK, and no other third-party code is included in the app.

11. Changes to this policy

If a future version of Lido changes what it stores or what permissions it needs, this page will be updated before that version ships, and the effective date at the top will change with it. A change that would involve collecting data or adding network access would be stated plainly here rather than buried in a clause.

12. Contact

Questions about this policy, or about anything the app does with your data: [email protected].


See also the terms of use and the support page.