Your cups. Your choice.
Who runs Little Beverages
Little Beverages is operated by Connor Patterson in Washington State, United States. Contact hello@littlebeverages.com for support and privacy requests. Anyone can browse without an account. Accounts and uploads are for people age 13 or older; the first account beta is limited to invited U.S. residents. We do not offer accounts to children under 13. If you believe a child under 13 supplied account or uploaded personal data, contact us so we can investigate, restrict the account and remove the data where required.
Your diary
Without an account, your notes, photos, dates and favorites stay in this installation’s diary. When signed in, a separate private account diary syncs through Supabase and keeps an offline copy here. Bringing the signed-out diary into an account requires a separate choice. Account diaries use owner-only database and photo storage access. They are not end-to-end encrypted. Your device’s backup settings may include app data, and someone with access to your unlocked device or browser profile may be able to read stored data.
Places you record
A saved drink can include the café, its address and map coordinates, the visit date, drink details, a rating and price. Together these can reveal where you have been and what you bought, even though we do not request GPS access. These details stay in the device diary when signed out, or sync with your private account diary when signed in. Save only information you want included in your diary.
Your account
If you choose to sign up, Supabase processes your account identifier, email address, authentication information and service security logs to run your account. Apple sign-in can use Hide My Email. We don’t request your full name from Apple. Passwords are handled by Supabase; the app doesn’t save your password. iPhone sign-in sessions use the device Keychain; browser sessions use local browser storage. Beta access requires a single-use invitation and acknowledgement of the current notices after sign-in. We keep the admission status and a server-dated history of the notice version, age/residency attestations and agreement. These are self-attestations, not independent age or residency verification.
What you choose to share
Publishing is optional and separate from saving a drink. A public copy includes the drink name, café, category, optional rating, order-again choice, an account identifier, an entry identifier and publication time. Other people can read and copy public posts. Diary notes, photos, price and the original visit date are not included. Editing your diary does not update the public copy automatically.
Friends
A friend profile is optional. If you create one, your display name and unique handle are visible to other signed-in people, who can send a request. A connection requires acceptance. Its participants and service operators can see the relationship; other users cannot read your friends list. Friends see only drinks you explicitly published and that passed review. No contacts are uploaded, and no private diary data is shared. Blocking closes the connection and hides your profiles from each other. A display name can identify you; you may choose a nickname. Friend requests, connections and blocks form an in-app social graph.
Menus and ratings
The drink names, categories, details, café, menu date, source link and optional menu photo you submit are stored in Supabase. The app renders a new JPEG before uploading; avoid including people or personal information in the photo. Uploads are visible to you and service operators until approved, then become publicly readable. You must have permission to share the menu. Only aggregate drink ratings are public; your individual ratings are visible to you and service operators. You can change or remove your ratings and remove your own menu uploads. Removing a menu also removes its item ratings. Short-lived photo links may work for up to two minutes after withdrawal.
Maps and other services
Map and café catalog requests go to OpenFreeMap. These requests reveal your IP address and the map area you view; the app does not request your device’s location. Some city-preview images load from their image providers. Directions opens Apple Maps or Google Maps, and invitations use the share destination you choose. Café websites and menu-source links open the external website you choose. Those services have their own privacy practices. Our current Supabase project stores account data in the United States (Northern Virginia). Providers may process operational data under their own service terms.
No advertising profiles
This version has no advertising SDK, behavioral analytics, contact upload or device location tracking. We do not sell personal information or share it for cross-context behavioral advertising. Necessary account storage is used to keep you signed in. The app does not change its practices in response to a browser Do Not Track signal; it does not perform the advertising tracking described above.
Cookies and device storage
The website has a separate cookie and storage notice. The app uses storage for the diary, café cache, preferences and sign-in that you choose to use. Browser diaries use local storage or IndexedDB; native diaries use app storage, and native account sessions use the Keychain. These are not advertising identifiers. Clearing browser/app storage can remove unsynced diary data, so export anything you want to keep first.
Your choices
You can browse and keep a diary without an account. Settings lets you export your private diary or clear it. Clearing a signed-out diary affects this installation. Clearing an account diary also syncs that removal to the account and its connected devices. Account settings lets you request an account-data export, withdraw individual shared drinks and delete your account. Deleting an account removes its private cloud diary, uploaded photos, shared posts, friend profile and connections, menu uploads and ratings, block list and reports. The current device’s account cache is cleared after successful deletion. Other devices need to reconnect to receive account changes; exported or independently retained offline copies cannot be remotely guaranteed erased. The separate signed-out diary has its own deletion control. Copies you exported, device backups and copies made by other people are outside the app’s deletion controls.
Retention and security
Device copies stay until cleared, browser storage is removed or the app is uninstalled. Private account records stay until deleted or the account is deleted. To avoid breaking offline changes, replaced or removed cloud photo objects remain until account deletion; storage cleanup and backup retention must be finalized before launch. Public submissions wait for review and stay until withdrawn, removed or the account is deleted. Reports and blocks are stored to operate community safety. Closed friend requests are kept until account deletion to prevent repeat requests; action-limit counters are pruned after 30 days when you next use a limited action. Menu uploads remain until removed or account deletion. Provider logs and backups have separate retention periods that must be confirmed before launch. Network requests use HTTPS. No system can guarantee absolute security. The beta reserves up to 100 immutable private cloud-photo paths per account, at most 3 MB each. Reservations include failed uploads and replaced photos; retrying the same photo reuses its reservation. Reservations and notice-acceptance records are removed with the account. Redeemed invitation codes cannot be reused after account deletion; the retained code hash and redemption time are no longer linked to the deleted account.
Community safety
Drink posts and menu submissions are reviewed before display. You can also report menus or friend profiles. You can report a shared drink, block its author and manage blocked accounts in Account. Reports and block lists are visible to the account owner and authorized service operators, not the public feed. Contact hello@littlebeverages.com for help or to request review of a moderation decision.
Beta feedback
If you test through Apple TestFlight, Apple handles test distribution and may provide us with testing and crash information. Feedback and screenshots you choose to send may reveal app content. Please leave private diary notes, passwords and other sensitive details out of feedback. Email sent to our support address is handled by our email provider and used to answer your request.
Questions and requests
Use the contact below to ask about access, correction, deletion or other privacy rights. Rights and deadlines depend on where you live. We will verify requests in a way appropriate to the data and won’t require you to publish your private diary to make a request.
Changes to this notice
The date above identifies this version. We will update this notice when our data practices change and provide notice of material changes in the app before those changes take effect, obtaining additional permission where required.