Privacy Policy
In plain words:
- Everything you track in Abvy, your drinks, sessions, body profile, and BAC estimates, lives in a database on your device. We run no server that stores it, and we cannot see it.
- What does leave your device: anonymous usage statistics (you can turn them off), crash reports, purchase receipts handled by Apple or Google, and on Android a few app-usage steps sent to Google to measure our ad campaigns (the same off switch).
- Details about your drinks are never included in usage statistics unless you separately and explicitly opt in.
- We never sell your data, show ads, or use your data to train AI models.
Who we are
Abvy is developed and operated by Antonín Wingender, an individual developer based in the Czech Republic ("we"). For anything in this policy, write to support@abvy.app. We are the data controller for the processing described here.
What stays on your device
Abvy has no account system and no backend of its own. The following is stored only in the app's local database and never transmitted to us:
- Every drink, meal, water, and session you log, including times and amounts
- Your body profile: sex, weight, height, and date of birth
- Your answers to the drinking-habits questionnaire during onboarding
- Optional health flags you set (for example liver conditions or GLP-1 medication)
- Breath test readings, whether you enter them yourself or take them with a paired BACtrack breathalyzer, and the paired breathalyzer's model and serial number
- BAC estimates and insights, which are computed entirely on your device
- Photos you attach to custom drinks, and all app settings
This data participates in your device's normal system backups (for example an iCloud device backup), which are governed by Apple's or Google's terms, under your control. You can erase everything at any time with Settings → Your data → Factory reset.
What leaves your device
Usage analytics
We collect anonymous usage events, such as "a drink was added" or "settings opened", through PostHog, processed on servers in the European Union. These events carry a random install identifier, never your name (we do not know it) and never drink details. We use them to understand which features matter and to fix what does not work. The practice evening in onboarding is the one exception: it is never saved and is not your drinking record, so its events say which sample drinks you try there (type, size, strength, time on its clock) and what you search for, as the website calculator does. PostHog also derives an approximate location (country and city) from your connection's IP address; the IP address itself is not stored. You can turn this off at any time in Settings → Your data, and the app stops sending events immediately.
Drink-detail analytics (separate opt-in)
Only if you explicitly opt in, and never before, analytics events additionally include drink-level details such as the drink name, quantity, and timing. Because drinking data is health data, we treat this opt-in as your explicit consent. You can withdraw it at any time in Settings → Your data, with effect for all future events.
Crash and error reports
When the app crashes or hits an error, a diagnostic report goes to Sentry (servers in the United States). Reports contain technical state, recent in-app actions (event names only, no drink details), the same random install identifier, and coarse usage buckets, never exact drinking totals. If you send us feedback, your message, an optional email address, and, when you leave the "include app data" switch on, a copy of your tracked data may be attached so we can debug your issue. That switch is clearly shown on the feedback screen and is always yours to turn off.
Purchases
Payments are processed by Apple or Google; we never see your payment details. RevenueCat validates purchase receipts and remembers, under an anonymous identifier, which plan is active so the app can unlock itself. Purchase and restore events in the usage analytics and crash reports carry that same anonymous identifier, so we can find your purchase when you ask us for help with it.
How you found Abvy
On Android, the app reads once which link you installed it from, using the campaign tags Google Play keeps for that link (for example "from a page on abvy.app" or "from the Caffeine Clock app"). The tags stay on your device and, while usage analytics are on, are added to the analytics events and to the anonymous RevenueCat record, so we can tell which links bring people to Abvy.
On iPhone, while usage analytics are on, RevenueCat collects the attribution token that Apple's AdServices framework gives the app. Apple uses it to tell whether the install came from an Apple Ads campaign, and which campaign and search term. The token does not identify you or your device.
If you came from Caffeine Clock, our other app, the link also carries Caffeine Clock's anonymous purchase identifier. To give Caffeine Clock supporters their free year, our server asks RevenueCat whether that identifier owns Remove Ads and stores which Caffeine Clock identifier unlocked which anonymous Abvy identifier, so each purchase unlocks one year. Neither identifier says who you are.
Ad campaign measurement (Android)
On Android, the app reports a few app-usage steps to Google Analytics for Firebase so we can measure whether our ad campaigns lead people to use Abvy: starting and finishing onboarding, viewing the practice evening, viewing the paywall, choosing a plan, starting and completing a purchase, opening the calculator, and logging your first drink. Each report is only the name of the step. It never carries drink details, BAC or other health data, and ad personalization is turned off. Google also receives the technical data its SDK collects by itself, such as an app instance identifier, device model, and approximate location. The same switch as usage analytics, Settings → Your data, turns this off.
App updates
On launch the app asks Expo's update service (EAS Update) whether a newer version of the app's code is available. That check carries your device's operating system and a randomized token, nothing about you or your tracking.
iPhone waitlist (this website)
If you joined the iPhone waitlist on abvy.app before Abvy came to the App Store, we stored the email address you entered and the language of the page you signed up on, on Cloudflare's infrastructure, based on your consent, and use them for exactly one purpose: telling you that Abvy is now on the App Store. No newsletter, no sharing, no linking to anything you later track in the app. The waitlist no longer takes signups. Write to support@abvy.app to have your address deleted at any time; the list is deleted once that one email has gone out.
Visiting abvy.app
The website keeps anonymous usage statistics through PostHog (servers in the European Union): which pages are viewed, where visitors came from, coarse device and country information, taps on the App Store and Google Play links, and which sample drinks are added in the calculator. The calculator's body settings are never sent. The site sets no analytics cookies and stores nothing in your browser, so every visit is counted separately and there is nothing to opt out of or delete. If a page breaks, a technical error report (the page, browser type and the error itself, no personal data) goes to Sentry (servers in the United States) so it can be fixed.
Apple Health
If you enable Health sync, Abvy writes your drink counts into Apple Health. Abvy never reads data from Apple Health, and data gathered through HealthKit is never used for advertising, marketing, or data mining, and is never shared with third parties. You can turn sync off and delete Abvy's Health entries in Settings → Integrations.
Bluetooth breathalyzer
If you pair a BACtrack breathalyzer, Abvy uses Bluetooth to connect to it while you pair it or take a breath test, and only after you tap to connect. Each reading arrives from the breathalyzer and is stored with the rest of your data on your device and in your encrypted iCloud backup. Readings are not sent to us, with one exception: if the breathalyzer sends a message the app cannot read, the error report includes that raw message, which can contain a reading. Abvy remembers the breathalyzer's model and serial number so it can reconnect to it. Forgetting the breathalyzer in Settings removes it from your phone, and Factory reset erases its readings.
iCloud backup
On iOS, Abvy keeps an encrypted backup of your data in your own iCloud Drive so you can restore after losing a device. Backups are encrypted on your device with a key stored in your iCloud Keychain (end-to-end encrypted by Apple); we cannot read them. A small unencrypted status file carries only counts and dates, never drink data. Automatic backup is on by default and can be disabled, and backups deleted, in Settings → Your data.
Sharing, and what we never do
We never sell personal data, never share drink, BAC or health data for advertising, and never use it to train AI or machine-learning models. The only recipients are the processors above, acting on our instructions under data processing agreements: PostHog Inc. (analytics, EU region), Functional Software Inc. dba Sentry (diagnostics), RevenueCat Inc. (purchases), Google (Google Analytics for Firebase on Android, ad campaign measurement), and Expo (updates), alongside Apple and Google as your app store. Each of them is contractually required to protect your data to the same standard as this policy. If you use iCloud backup, device-to-device transfer, or CSV export, the destination is chosen by you.
Legal bases (GDPR)
| Processing | Legal basis |
|---|---|
| Purchase validation and entitlements | Performance of a contract (Art. 6(1)(b)) |
| Anonymous usage analytics and crash reports | Legitimate interest in improving and stabilizing the app (Art. 6(1)(f)), with an always-available off switch |
| Ad campaign measurement on Android (Google Analytics for Firebase) | Legitimate interest in measuring whether our advertising works (Art. 6(1)(f)), with the same off switch as usage analytics |
| Drink-detail analytics | Your explicit consent (Art. 6(1)(a) and Art. 9(2)(a)) |
| Feedback you send, including optional attachments | Your request and consent when you press Send |
Abvy makes no automated decisions about you with legal or similarly significant effects (GDPR Art. 22). BAC estimates are informational calculations on your device.
International transfers
Usage analytics stay in the European Economic Area (PostHog EU). Sentry, Expo and Google (for ad campaign measurement on Android) are certified under the EU-US Data Privacy Framework; RevenueCat relies on the EU Standard Contractual Clauses. Copies of these safeguards are available from each provider or from us on request.
Retention and deletion
Data on your device stays until you delete it, factory-reset the app, or uninstall. Diagnostic and analytics data is kept only as long as needed for the purposes above and is then deleted or aggregated by our processors under their standard retention windows. To have the data linked to your install identifier deleted, or to exercise any other right, email support@abvy.app; deleting the app's data and turning analytics off also stops all future collection.
Your rights
Under the GDPR you can ask us for access, rectification, erasure, restriction, portability, and you can object to processing based on legitimate interest, or withdraw consent at any time without affecting past processing. Write to support@abvy.app and we will respond within one month. You also have the right to complain to a supervisory authority, in particular where you live or work. Our lead authority is the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Prague 7, Czech Republic, uoou.gov.cz.
If a US state consumer health data law applies to you, our separate Consumer Health Data Privacy Policy describes those rights.
Age
Abvy is intended for people who are at least 18 years old and of legal drinking age where they live. It is not directed to children, and we do not knowingly collect data from anyone under 18.
Changes
When this policy changes materially, the app will tell you and this page will show a new effective date.
- August 20, 2026: first published.
Contact
Antonín Wingender · Školská 660/3, 110 00 Praha 1, Czech Republic · support@abvy.app