Privacy Policy
CUPPERLØG is a coffee diary built by a tiny independent team. This policy explains what information the app handles while you record your coffee journey, and the short version is: your diary belongs to you, most of it never leaves your device, and we don't run analytics, ads, or trackers.
1. Information we collect
Account credentials. A Cupperlog account is required to use the diary. We store your username, a contact email address, and your display name to manage account access and keep your diary secure.
Profile details. Your display name, @handle, an optional profile photo (resized to a small thumbnail on your device before it is stored), and an optional home city (which you can type yourself or have suggested on your device — see section 3) are saved with your profile, and are synced to our cloud while you are signed in.
Journal & sensory data. Your cupping notes, coffee details, calendar entries, ratings, and diary-board layouts make up your personal diary.
Visual media. Photos you attach to diary boards or upload for group tasting events are hosted on our cloud infrastructure so they display across devices.
Push tokens. If you allow notifications on iOS or Android, a device push token linked to your account is stored so we can deliver them (see section 3).
2. Local vs. cloud storage
Local-first. Your diary lives in your device's local storage first, so once you are signed in, writing and reading entries works even offline. Features that involve other people or the cloud (sync, group events, AI scanning) need an internet connection.
Cloud synchronization. When you are signed in and online, your entries, profile, and saved collections are backed up to our secure cloud database (powered by Supabase, hosted in Sydney, Australia).
3. Device permissions
The app requests system permissions only when you use a feature that needs them, and you can revoke any of them at any time in your operating system settings:
Camera & Photo Library. Used to photograph coffee packages for label scanning, attach photos to your diary boards, and read event join codes.
Location (optional, approximate). Only when you tap the location button (the compass icon) while editing your profile, the app reads your device's approximate location once and reduces it on your device to your nearest city, using a built-in list of cities. For the profile city, your coordinates never leave your device — only the resulting city name (for example “Melbourne, AU”) is saved to your profile. It is never read automatically, and you can always skip it and type your city by hand instead. Separately, when you start a new diary entry and you have already allowed location access, the app reads your approximate location once to pre-fill the day’s weather — it never shows a permission prompt by itself, and a tap on the weather icon always overrides it. It rounds the location on your device to about 11 km, and sends only that rounded point to our server, which asks MET Norway (the Norwegian Meteorological Institute) for the local forecast and returns a simple sunny / cloudy / rainy value. The rounded point is used only to answer that request and is never stored. Weather data by MET Norway, CC BY 4.0.
Notifications (optional). On iOS and Android, when you are signed in the app asks the system for permission to send push notifications — for example to tell you a group tasting's results are ready. If you allow it, a device push token linked to your account is stored in our cloud database so those notifications can reach your device; the token is removed when your account is deleted. Declining simply means no notifications — everything else works the same, and you can change your mind any time in your system settings.
4. AI label scanning
When you choose to scan a coffee package, the photo is sent over an encrypted connection to our server and forwarded to Anthropic's Claude API, which reads the label and returns the coffee's details as text. The photo is used only to answer that scan; it is not used to train AI models. Scanning is entirely optional — you can always type the details yourself, and when scanning is unavailable an on-device reader is used instead.
5. Analytics & tracking
CUPPERLØG currently contains no analytics, no advertising, and no third-party trackers. We only see the technical server logs needed to keep the cloud service running. If we add crash reporting in a future version to help fix bugs, this policy will be updated first to say exactly what it collects.
Our processors. The complete list of third parties that process data for us: Supabase (accounts, database, storage, and sync — hosted in Sydney, Australia), Anthropic (reads the label photo when you use the AI scan), Resend (delivers password-reset emails — it sees your contact email address only for that message), MET Norway (answers the diary’s weather lookup — it receives only a location rounded to ~11 km from our server, never who asked), and Cloudflare (serves this website and routes support email). Each processes your data only to provide its service to us, and none of them advertises to you or sells your data.
6. Your data rights
Export. You can export your coffee history to a portable JSON document from Settings at any time.
Deletion. Deleting your account from Settings permanently removes your entries, profile, media, and your answers and participation in events from our cloud servers. Events you hosted are unlinked from your account and closed instead of deleted, so the other tasters keep their records (see the deletion page for details). Feedback you submitted may be kept in anonymized form.
7. Information security
All data moving between the app and our servers is encrypted in transit (TLS), and cloud data is protected with per-user access rules so only you can read your diary. No internet system is perfectly secure, so cloud features are provided on an as-available basis.
8. Changes & contact
We may update this policy as the app evolves; the current version is always available at this address and inside the app under Settings → About. Questions or requests: support@cupperlog.com.