Last updated: September 29, 2026 · Effective: April 20, 2026
AlcoLog is operated by Dean Chew, a sole trader domiciled in the United Kingdom. For any privacy-related questions, contact us at privacy@alcolog.app.
AlcoLog is an alcohol consumption tracking app for iPhone, Apple Watch, Android and Wear OS. It helps you log drinks, monitor your intake, and understand your drinking habits. For people who have stopped drinking, its Sober Mode tracks alcohol-free days instead of consumption. AlcoLog is not a medical device and does not provide medical diagnosis, treatment, or advice.
AlcoLog stores all personal and identifiable data on your device. The only copy that can leave it is the optional iCloud backup to your own Apple Account, described below, which we cannot read. The following are never transmitted to our servers under any circumstances:
If you choose to opt in to anonymous data sharing, AlcoLog sends stripped-down statistical summaries of your sessions (see "Anonymous usage data" below). These summaries include general timing (day of week, month, hour), cost data with currency, and behavioral patterns, but never exact dates, locations, names, or anything that could identify you.
Location data: AlcoLog uses location services only for optional features you turn on yourself: geofencing (such as reminders when arriving at or leaving a saved venue) and tagging a logged drink with where you were. Saved places, home rules, drink location tags and geofence triggers are processed and stored on your device only, and are never sent to our servers. If you turn on iCloud backup, they are included in the backup saved to your own iCloud account, which we cannot read.
The one exception, venue name lookup: if you ask AlcoLog to identify the name of the venue you are at, that single lookup is sent to the platform's map provider, because naming a place requires a map database we do not host. On iPhone and Apple Watch it goes to Apple Maps. On Android it goes to Google Maps and Places. Your location is sent to that provider for that one lookup, and is then handled under their privacy policy rather than ours. Nothing else about your location leaves your device, and if you never use the venue name lookup, no location is sent anywhere at all.
If you have Premium and leave iCloud backup switched on, AlcoLog saves a copy of your app data (sessions, drinks, Sober Mode entries, medications, favorites, scanned products and your settings) to the private iCloud database of your own Apple Account, once a day and whenever you tap Back Up Now. The copy is stored by Apple under your account and counts against your iCloud storage. We run no server for it and cannot read, access or restore it for you. Apple Health data is never included. AlcoLog keeps your three most recent backups and replaces the oldest each time. You can turn automatic backup off in Settings > Data & Privacy, and delete the backups at any time in the iPhone Settings app under your name > iCloud > Manage Account Storage (or Storage) > AlcoLog. If Premium ends, new backups stop, and your existing backups stay yours to restore.
With your permission, AlcoLog writes four data types to Apple Health:
Editing or deleting a drink in AlcoLog updates or removes the matching Apple Health samples.
AlcoLog does not read data from Apple Health. HealthKit data is never used for advertising, data mining, or shared with third parties. HealthKit data is governed by Apple's own privacy protections and is not transmitted to our servers.
The Android app uses Health Connect rather than Apple Health. With your permission, AlcoLog writes two data types to Health Connect:
AlcoLog reads exactly one data type from Health Connect, and only if you grant that permission:
No other Health Connect data is read or written. AlcoLog does not access your steps, heart rate, sleep, exercise, or any other record type. Health Connect data is never used for advertising or data mining, is never shared with third parties, and is never sent to our servers.
If you choose to enable "Share Anonymous Data" in Settings, AlcoLog will send anonymized session summaries to our servers. This is off by default and entirely optional.
During setup, AlcoLog asks how you heard about it. You choose one of five options: a therapist, a doctor, a support-group sponsor, a friend or family member, or that you found it yourself. There is no free-text field, and we never ask who the clinician or service was.
Your answer stays on your device unless you turn on anonymous data sharing, which is off by default. If sharing is on, we receive only the option you chose, attached to the same random anonymous identifier as the rest of your shared data. It is never linked to your name, email address or any contact detail, and switching sharing off later stops it being sent.
We use this to understand where people find AlcoLog, including whether clinicians recommend it.
When you opt in, AlcoLog generates a random identifier (UUID) stored only on your device. This identifier allows us to group your sessions for trend analysis without knowing who you are. It is not linked to your Apple ID, Google account, device, or any personal information. If you opt out or delete the app, this identifier is discarded.
Anonymous data is sent via encrypted HTTPS connection to servers hosted by WPX (wpx.net). Data is encrypted in transit and at rest.
AlcoLog offers an optional Premium subscription via Apple's App Store on iPhone and Apple Watch, and via Google Play on Android and Wear OS. All payment processing is handled entirely by Apple or Google. We do not receive, process, or store any payment details, credit card numbers, or billing information.
The AlcoLog iPhone, Apple Watch, Android and Wear OS apps do not use third-party analytics SDKs, advertising networks, crash reporting tools, or social media SDKs.
The Android app includes two Google SDKs that are neither analytics nor advertising. ML Kit runs entirely on your device and sends nothing anywhere. The Places SDK is used only for the venue name lookup described above, and only at the moment you ask for it.
The AlcoLog website (alcolog.app) uses a small number of standard third-party services:
The AlcoLog website uses cookies for two purposes: essential session state and optional analytics. We do not use advertising, personalization, social, or cross-site tracking cookies of any kind.
A small amount of functional storage is always active: your cookie consent choice itself (so we don't ask again on every visit) and standard browser storage required for the site to render. These do not require consent under UK GDPR / PECR.
We use Google Analytics 4 to measure aggregate website traffic — pages viewed, approximate region, and referring source. This is only used to understand which parts of the site are useful. We do not combine it with your anonymous in-app identifier, and we do not sell, share, or rent analytics data.
Google Analytics is loaded with Google Consent Mode v2. On page load, all tracking is set to denied. What happens next depends on where you are visiting from:
_ga and _ga_<id>) and begins measuring. If you Reject, Analytics stays in a consent-denied state, which means no cookies are set and no identifiable data is collected. We decide whether the banner is legally required from your browser's reported timezone (read locally via Intl.DateTimeFormat()). Your IP address is not sent to any third party for this check; nothing leaves your device.You can change your cookie choice at any time by clicking Cookie Settings in the site footer. This re-opens the banner so you can accept or reject again, regardless of where you are visiting from. You can also clear all AlcoLog cookies directly from your browser settings.
Our contact form uses Google reCAPTCHA v3 to prevent spam. reCAPTCHA sets a small number of cookies solely for bot detection; it does not fire without you interacting with the contact form. Submitting the contact form implies acceptance of Google's Privacy Policy and Terms.
When you use the barcode scanner to look up a product, the numeric barcode is sent to public product databases to retrieve the product name, alcohol percentage, and calorie information. We do not send any identifier that could link the scan to you.
Barcode lookup is part of Premium. The following databases are queried:
Our server caches successful lookups for up to 30 days to reduce repeated queries to FatSecret. The cache contains only the barcode and the returned product information. It does not contain any user identifier, IP address, or timestamp linked to a specific user.
Each provider has its own privacy policy. The most relevant ones:
When you use the camera icon on the Add Drink form to identify a drink from a photo, the photo is analyzed entirely on your device using Apple's Vision framework. We do not upload the photo to our servers, do not transmit it to any third party, and do not retain a copy on our infrastructure. The photo remains in your camera roll exactly as it would for any other photo you take or choose. Only the resulting drink-type and size guesses are surfaced to the app for you to confirm before logging.
On Android the same feature uses Google ML Kit Image Labeling, which also runs entirely on your device, with the same guarantees: the photo is not uploaded, not transmitted to any third party, and not retained on our infrastructure. The Android barcode scanner also uses ML Kit on your device to read the code from the camera. What happens to the barcode number after that is described under "Barcode scanning" above.
Receipt scanning and the Menu Scanner work the same way. When you point the camera at a bar receipt or a drinks menu, the image is analyzed entirely on your device to read the drink names and prices printed on it. The image is not uploaded to our servers, not transmitted to any third party, and not retained on our infrastructure. The text it reads is used only to fill in the drinks you are logging, and it stays on your device with the rest of your log.
When you submit the contact form on our website, we receive the name, email address, subject, and message you provide. The submission is routed by enquiry type to the appropriate inbox (for example support, feedback, press, privacy, or legal).
For bug reports only, you may optionally attach screenshots or a short screen recording (images and video files). These attachments are sanitized on our server, then passed directly into the outgoing email. They are not stored separately on our web server.
We retain contact correspondence only as long as necessary to respond to and resolve your enquiry, plus a short period for reference and audit. Contact data is not merged with your anonymous in-app data except where specifically required to action a data rights request, as described below.
AlcoLog is not intended for use by anyone under the age of 18. We do not knowingly collect data from minors.
Under UK GDPR and applicable data protection laws, you have the right to:
Because the anonymous data we collect cannot identify you, we will ask you to provide your anonymous identifier (found in Settings > Data & Privacy in the app) to locate your data for access, export, correction, or deletion requests.
To action a data rights request, we need to temporarily pair the email address and name you contact us from with your anonymous identifier. This pairing is required by data protection law so we can verify the request and locate the correct data.
We use industry-standard security measures to protect your data, including:
We may update this policy from time to time. Material changes will be communicated via an in-app notice. The "Last updated" date at the top will always reflect the current version.
For any questions about this privacy policy or your data: