All of the following is stored locally, in MMKV on Android or in your browser's localStorage on Web (when running outside the Play Store build). They never leave your device unless you explicitly export them yourself (CSV / JSON export inside Settings).

Exported data: when you tap "Export" in Settings, the app produces a CSV / JSON file in the app's share sheet. You decide where the export goes — we never auto-send it anywhere.

Uninstall: uninstalling the app deletes the above data with it. There is no remote copy to also delete.

Hoptimise has no proprietary backend. Every network call the app makes is to a named third-party service. Each is documented below.

The app requests only the permissions it needs. Each is opt-in via the OS dialog.

We do not request: contacts, microphone, calendar, phone state, Bluetooth, Nearby Devices, or background-location. The app does not run while in the background except for the foreground-service notification, which can be disabled at any time in Settings.

The third parties above may process your data outside the UK / EEA. In particular:

Hoptimise is intended for adults of legal drinking age in their jurisdiction. We do not knowingly collect data from anyone under that age. If you believe a child has used the app and uploaded any of the above third-party data, contact [email protected] and we will assist the relevant guardian in removing the data on a best-effort basis.

There is no account to delete and no remote profile to remove. Uninstall = total removal of all data the app stored.

When this policy changes materially, we will:

The git history of this file is the authoritative change log. We will not retroactively rewrite history.

We aim to respond to all privacy enquiries within 30 days.

This section sets out the legally-required disclosures a real privacy-policy lawyer would expect for UK GDPR / EU GDPR / California CCPA-CPRA. It is written for an EU-and-California distributed Android app, even though Hoptimise is operated by a UK-based developer.

Each processing purpose has a stated lawful basis under UK GDPR Article 6(1) (mirrored in EU GDPR):

Article 6(1)(f) requires the legitimate-interest basis to be backed by a documented Legitimate Interest Assessment (LIA). The assessment for the Gemini text stage is:

We will revisit the LIA if Gemini's pricing or Google's free-tier data-governance terms change materially, or if a local AI label-identification model becomes available with comparable accuracy.

You have the following rights. We will respond within 30 days; if your request is complex we will acknowledge within 7 days and complete within 90 days. To exercise any of these, email [email protected].

Hoptimise is provided by a UK-based developer. Under EU GDPR Article 27, a non-EU controller offering services to EU residents must appoint an EU representative unless exempted under Art. 27(2). We have not yet appointed one. Until we do, EU distribution remains a known compliance gap; EU residents should direct any EU GDPR correspondence to [email protected], and we will coordinate with an EU representative on a per-request basis.

Article 27(2) exempts the appointment requirement where processing is occasional, does not include special-category data on a large scale, and does not include large-scale processing of personal data.

We conclude the Art. 27(2) exemption is not safely available because AdMob rendering is not "occasional". We will appoint an EU representative before any EU-targeted marketing or paid EU promotion. Until that appointment is made, the disclosure above stands as the remediation step.

Hoptimise does not appoint a Data Protection Officer. Article 37(1) triggers mandatory DPO appointment in three cases: (a) the processing is carried out by a public authority or body, regardless of processing size; (b) the controller's or processor's core activities consist of processing operations which, by virtue of their nature, scope and/or purposes, require regular and systematic monitoring of data subjects on a large scale; (c) the controller's or processor's core activities consist of processing on a large scale of special-category data pursuant to Article 9(1)/(2) or of personal-data relating to criminal convictions and offences under Article 10. None apply: Hoptimise is a private controller (a does not apply); we do not conduct large-scale regular or systematic monitoring of data subjects (b does not apply); drink logs and the calorie aggregates shown in the drinking-session notification are not Art. 9 special-category data, and we hold no criminal-conviction data (c does not apply). Hoptimise processes no special-category data (drink logs are not health or biometric data) and does not monitor on a large scale. If this changes — for example, if the app begins collecting clinical-grade health signals (blood alcohol concentration, sustained drinking biomarkers, prescription interactions, etc.) — the policy, the Article 37 analysis, and the DPO appointment will be updated in the next release. Note that Hoptimise's current calorie aggregates (drinks × 56 kcal / unit) are not Art. 9 special-category data on their own.

Hoptimise is available to California residents via Google Play. The following disclosures apply under the California Consumer Privacy Act and the California Privacy Rights Act.

Categories of personal information collected, in the last 12 months:

Sources: directly from your device. No data brokers.

Business or commercial purposes: displaying in-app statistics, ad-funded revenue via AdMob, AI-assisted label identification.

Categories of third parties with whom we share or sell: we do not sell personal information, including that of California residents. For business purposes (rendering ads), we share limited device identifiers with Google AdMob, which Google may use for cross-context behavioural ad targeting unless you have opted out via Settings → Google → Ads → Opt out of Ads Personalisation at the OS level. We therefore treat the AdMob flow as a "share" under the CPRA. We do not otherwise share personal information with third parties.

California consumer rights:

We respond to verifiable consumer requests within 45 days, extendable to 90 days with notice, as required by California regulations.

Gemini's drink identification generates a structured JSON response that the app writes into the form fields of your drink-entry modal. This is automated processing. You can change any field before saving, so the processing is not solely automated within the meaning of Article 22(1): you retain full authority over the final entry. If a suggestion is wrong, edit or delete it before tapping Save — the app will not log a drink against a suggestion you have not personally confirmed.

Hoptimise itself does not hold your personal information (see §2 — everything is on-device, and we have no server). If a security incident ever affects a third party that processes your data on the app's behalf (Gemini, MapTiler, AdMob, Maps), we will:

This policy is hosted at the URL configured by EXPO_PUBLIC_PRIVACY_POLICY_URL (default https://goodbyemyliver-p970sab.gamma.site/privacy-policy). It is accessible from any web browser without the app installed, satisfying the Google Play User Data Policy requirement that the privacy policy be available both inside the app and outside it.

This app uses the following open-source / third-party components. Their respective privacy practices are governed by their own policies and apply only when the relevant feature is in use: