Draft. 9 details on this page are still being finalized (highlighted below).
Drinkyin Privacy Policy
Effective date: [[EFFECTIVE_DATE]]
Last updated: [[EFFECTIVE_DATE]]
Version: 1.0
This Privacy Policy explains how Drinkyin LLC ("Drinkyin," "we," "us," or "our") collects, uses, discloses, and protects personal information when you use:
- the Drinkyin mobile app for iOS and Android;
- the Drinkyin web app / installable PWA at https://drinkyin.com;
- the Drinkyin Business Console — Business Accounts, currently in beta — used by shops and brands; and
- any related websites, emails, and support channels (together, the "Service").
Washington and Nevada residents: some of the information you enter into Drinkyin — hydration, nutrition intake, caffeine, and the allergy or "watch out for" tags you save — is treated as consumer health data under the Washington My Health My Data Act and Nevada SB 370. Those rights and our specific commitments are described in our separate Consumer Health Data Privacy Policy, which forms part of this Policy.
0. The short version
This summary is for orientation only; the numbered sections below control.
| Question | Answer |
|---|---|
| Do I need an account? | Not to log drinks. Without an account you can log drinks, see your history, and browse the drink library built into the app — and the app sends nothing to us or anyone else, except a crash report if the app crashes (§4). Features that use the internet (barcode scanning, nearby shops, weather tips, drink photos and brand logos, sync, and the community) need a free account. |
| What happens if I sign in? | Your logs, profile, and app settings sync to our cloud so you can use more than one device. |
| Can other people see my profile? | Only if you turn on your public profile (Settings → Account → Public profile, off by default). Then signed-in users can see your username, display name, avatar, bio, and the sections you switch on (collection, favorites, stats, check-ins, spots), plus your follower and following lists unless you hide them (§8.1). A private profile shows other users nothing — with one narrow exception: people you follow, or who follow you, see your name and avatar in their own follower and following lists. |
| Is my drink log public? | Not unless your public profile and its Check-ins section are on — both are off by default. Each log has its own share switch. When you are signed in, new logs start with sharing switched on; you can change that starting value in Settings → Privacy & Health ("Logs private by default") and switch sharing off on any log. Logs you make without an account are always private. A shared check-in is visible to signed-in users for 24 hours after the drink's time. You can hide what you drank or where you were on any shared check-in. |
| Do you sell my data? | No. We do not sell personal information, do not "share" it for cross-context behavioral advertising, and run no advertising or product-analytics SDKs. We use one crash-reporting service (Sentry) to find and fix bugs — see §4. |
| Do you track me across other apps and sites? | No. There is no ad identifier collection, no App Tracking Transparency prompt, no third-party trackers or advertising cookies. |
| Where is my location stored? | We do not store your device's location. Coordinates are sent to mapping and weather providers only at the moment you search for shops or load the weather. You can tag a log with a shop's name (picked from map results — never your coordinates or a free-text address). Shops you save to your wishlist (name, address, and the shop's coordinates) sync with your account. |
| Can I delete everything? | Yes. Delete your account and everything synced to it in the app (Settings → Account → Delete account), clear a device with Settings → Data → Clear data / Reset, or email us. See §11, §13, and our account deletion page. |
| Who can see my data at a shop or brand? | Businesses see counts of public check-ins only (how many public check-ins, how many distinct people). They never see private logs or identify individuals. |
| Can I add a business? | Yes — Business Accounts are in beta. Sign in to a personal account, then add one in Settings. When you put its shop page live, the business's name, menu, and shops are public; your own drink log and your personal profile keep their own, separate settings. To confirm you own the business we check a public channel it controls, never ID documents (§3). |
| Can I report or block someone? | Yes. You can report a profile, a check-in, or a business's drink, and block any account. Blocking works both ways and is enforced on our servers (§8.1). |
1. Scope and roles
This Policy applies to personal information we control as a business (under US state privacy laws). Drinkyin is currently offered only to users in the United States (§17).
- Consumers. If you use Drinkyin to log drinks, you are a consumer/user.
- Business accounts (beta). A Business Account is added to an existing personal account: you sign in and choose a username first, then add a shop or brand. This Policy also covers the information you give us about the business, its locations, and how you show that you control it. Your own drink logs stay private exactly as they are for any other user.
- Not covered. This Policy does not apply to third-party services you reach through Drinkyin (for example a map opened in Google Maps or Apple Maps), or to information you post publicly, which by definition is no longer private.
We are not a HIPAA covered entity or business associate, and Drinkyin is not a medical device or a healthcare service. See §15.
2. Two ways to use Drinkyin
Drinkyin is designed local-first, and the difference matters for your privacy.
2.1 Local mode (no account)
You can install and use Drinkyin without creating an account and without giving us an email address. Without an account, the app makes no requests to our servers or to any other online service, with two exceptions: downloading the app itself (from the App Store, Google Play, or, for the web app, from our website host), and, if the app crashes or hits an error, a crash report sent to our crash-reporting provider (§4). You can log drinks, see your history and totals, and browse and search the drink library, which is built into the app.
In this mode, everything — your logs, favorites, wishlist, ratings, settings, profile name and avatar — is stored only in your device's local storage (AsyncStorage on iOS/Android, localStorage in the browser). We cannot read it, cannot recover it, and cannot delete it for you. Uninstalling the app or clearing your browser's site data deletes it permanently.
If you use the Apple Watch app, it exchanges your quick-log data only with the Drinkyin app on your paired iPhone; it does not contact our servers itself.
Features that need the internet — scanning a barcode, finding nearby shops or tagging a log with one, weather tips, drink photos and brand logos, map thumbnails, sync, and the community — ask you to create a free account first, and do nothing until you do. When you create an account, the drinks you logged on the device are added to it. (Opening our legal or support pages from the app opens our website in your browser, like any link.)
2.2 Account mode (optional cloud sync and community)
If you create an account, we store a copy of your data on our servers ([[HOSTING_REGION]], operated by Supabase) so that you can:
- sync between devices and restore after reinstalling;
- claim a
@username, and, if you choose, turn on a public profile (§8.1); - follow other people, see a feed of the check-ins they share, and send a friend who follows you back a "drink some water" reminder;
- run a Business Account, whose shop page, shops, and menu are public once you put the shop page live.
Signing in is the moment your data starts leaving your device. You can sign out at any time, and you can delete the cloud copy yourself (§11, §16). Signing out — or a session that ends for any other reason, such as signing out everywhere from another device — also clears that account's data from the device; it comes back when you sign in again. (Data you logged while offline and that had not synced yet is cleared with it.) Data you created without ever signing in stays on the device.
3. Information you provide
| What | When | Where it goes |
|---|---|---|
| Email address | Sign-up and sign-in | Our servers (authentication). Also used to send you a one-time sign-in code. |
| Password | Sign-up, sign-in, password reset | Stored only as a salted cryptographic hash by our authentication provider. We never see your plaintext password. |
Username (@handle) | When you claim one | Our servers. Visible to other signed-in users only as described in §8.1 (your public profile, a business's menu items, follower lists). |
| Display name, bio, and avatar | Profile setup | Our servers, so they follow you across your devices. Visible to others only as described in §8.1. An avatar can be a built-in shape or a photo you choose from your device; a photo is shrunk to 256 × 256 pixels on your device before it is uploaded, and is stored in our file storage at a random, unguessable link (§8.1). |
| Public profile settings | Settings → Account → Public profile | Our servers: whether your profile is public, which sections are shown (collection, favorites, stats, check-ins, spots), and whether your follower and following lists are shown. When a section is on, a copy of it (the "showcase" — drink names and categories, your stats, the shop names in your Spots) is stored on our servers so others can read it; turning a section off empties that copy. |
| Follows | When you follow someone | Our servers: who follows whom and when. |
| Friend water reminders | When you tap 💧 Remind on a friend's profile | Our servers: who reminded whom and when — there is no message text. Reminders older than 7 days are deleted. The sender can't see whether you opened it. |
| Shared drinks | When you tap Share on a drink and send it to a friend | Our servers: who shared which drink with whom and when — the drink is stored by its catalog ID only, there is no message text. Only people you follow who follow you back can receive it. Shared drinks older than 7 days are deleted. The sender can't see whether you opened it. |
| Push notification address | When you allow notifications on a device | Our servers: the device's push token (or, on the web, its push subscription) and the device's time zone, used only to deliver friend reminders and shared drinks inside your reminder hours. Deleted when you sign out. |
| Reports and blocks | When you report or block | Our servers: who you reported (and which check-in or drink, if any), the reason, any note you add, and who you blocked. The person you report or block is never told who did it. |
| Drink logs | Every time you log a drink | Device always; our servers if you are signed in. Each log contains: the drink name and emoji, category, volume in ml, price if you enter one, the timestamp, a share flag with its "show what I drank" and "show where I was" choices, the name of a shop if you tagged one, and a nutrition snapshot taken at log time (calories, sugar, caffeine, sodium, and, where known, fat, saturated and trans fat, carbohydrates, fiber, protein, electrolytes, potassium, calcium, iron, added sugar, magnesium, taurine, and vitamins B3, B6, B12, C and D). |
| Date of birth | Sign-up | Our servers, on your account record (and a copy on your device). Asked once, when you create an account, to confirm you are old enough to use Drinkyin and, if age-restricted features are offered later, to check that you may use them (§12). It can't be changed in the app afterwards — if it is wrong, email us (§16). Not shown to other users. |
| Gender, height, and weight (all optional) | Sign-up and Settings → Personal | Device; our servers if signed in. You can change or clear them at any time in Settings → Personal. Not shown to other users. Height and weight are treated as sensitive information — see §6. |
| Hydration and nutrition goals | Settings → Personal | Device; our servers if signed in. |
| Nutrients you name yourself | When you add your own nutrient to track | The name, unit, amounts and daily target you type. Device; our servers if signed in (with your logs and settings). |
| Taste preferences | Onboarding and Settings | Device; our servers if signed in. |
| Allergy / "watch out for" tags (e.g. caffeine, dairy, nuts) | Settings → Personal | Device; our servers if signed in. Treated as sensitive information — see §6. |
| Favorites, wishlist, star ratings, collection, badges | As you use the app | Device; our servers if signed in. |
| Drinkware (cups and bottles you add) | When you add one to your collection | Name, nickname, brand, type, colour, capacity, quantity, whether you own it or want it, purchase price, when and where you got it, when you last cleaned it, whether it is a favorite, notes and tags. Device; our servers if signed in. Not shown to other users. |
| Search terms | When you search for a drink or a shop while signed in | Drink searches go to our drink database (Supabase, §8.3); they are not saved to your account, but our provider's request logs keep them, with your IP address, for the period in §11. Shop searches go to the mapping provider in §8.4 at that moment. Without an account, drink search runs on the library built into the app and sends nothing. |
| Saved places ("shops I want to visit") | When you save a place from Discover | Device; our servers if signed in. Includes the place name, category, address, and its coordinates. |
| Drinks you create (manual entry or barcode scan) | When you add one | Device; our servers if signed in. If you add a drink as a business, it is published to the shared drink database. |
| Reminder settings and alarms | Settings | Device; our servers if signed in. |
| Routines (a drink, its volume, an optional price, and the time and weekdays to log it automatically) | Settings → Routines & Reminders | Device; our servers if signed in. The drinks a routine logs are ordinary drink logs (see above). |
| Appearance, notification, and privacy preferences | Settings | Device; our servers if signed in. |
| Business application details | Adding a Business Account | Our servers: business name, business type (independent spot or brand), a contact phone or email you provide, and any note you write to support a brand application. Not shown to other users. |
| Business ownership verification | When you ask for the verified badge, or apply as a brand | Our servers: the channel you choose (the business's website, its social account, or the phone number on its public map listing), the public link you give us, the verification code we issue to your account, and our decision with any note explaining it. We look at the public page you link to; with the phone method we call the number shown on that public listing, never one you give us, and we do not record the call. We do not ask for ID or business documents. Not shown to other users — they only see the verified badge. |
| Business locations, menus, and shop page | Business Console | Our servers. Menu items are visible in search to every user (with the business name, the account's @username, and whether it is verified). The shop page — shop names, addresses, opening hours, phone numbers, and the shop page's own bio — is visible when you put the shop page live (Business Console → Page), and is separate from your personal profile. |
| Support correspondence | When you email us | Our email systems: your address, message, and anything you attach. |
We do not ask for and do not want: government ID numbers, payment card numbers, precise health records, biometric identifiers, or your contacts list. Drinkyin has no in-app purchases and processes no payments as of this version.
4. Information collected automatically
- Local storage. We store the app's state on your device as described above. On the web this uses
localStorageplus a service worker cache so the app works offline. These are strictly necessary storage mechanisms, not advertising or analytics cookies. We set no advertising cookies and no third-party tracking pixels. - Authentication session token. When signed in, a session token is stored on your device so you stay signed in.
- Server logs. Our hosting and database providers automatically record ordinary technical request data — IP address, timestamp, user agent, requested path, and error codes — for security, abuse prevention, and debugging. These logs are retained for a short period (30 days) and are not used to build a profile of you.
- Crash and diagnostic data. If the app crashes or hits an error, it sends a crash report to our crash-reporting provider, Sentry (Functional Software, Inc., United States). This happens whether or not you have an account. A report contains the error and where in our code it happened, the app version, basic device details (such as the device manufacturer and model, operating-system version, screen size, language and time zone, and memory, storage and battery state), and a short trail of what happened just before the error — the names of the screens you opened and buttons you tapped, and system events such as the app going to the background. The crash-reporting software may also send a short session record each time the app is opened (when the session started and ended, and whether it crashed — nothing you entered), and a random identifier for the app installation that the crash-reporting software generates itself and that is not connected to your account. Before a report leaves your device we remove coordinates, email addresses, usernames, sign-in tokens, profile fields (date of birth, gender, height, weight, allergy tags) and place names, and we do not attach your account ID, screenshots, or the contents of your drink log. For crashes in the app's native (non-JavaScript) code, the crash-reporting software builds the report itself and this on-device filter does not run; for those we rely on not passing this information to the crash-reporting software in the first place. We have configured Sentry not to store your IP address or a location derived from it. This filtering is automated and, like any filter, may not catch everything. Crash reports are kept for [[CRASH_RETENTION]]. Apple and Google may also give us aggregated crash statistics if you have enabled sharing with them in your device settings.
We do not use any advertising SDK, attribution SDK, or third-party product analytics SDK. The crash reporter above is used only to find and fix bugs. We do not collect the IDFA, the Android Advertising ID, or any cross-app identifier, and we therefore do not present an App Tracking Transparency prompt.
5. Device permissions and what each one actually does
Location and camera are used only by features that need an account (§2.1). Drinkyin asks for a permission only at the moment the matching feature is used, and every one of them is optional — declining disables that feature and nothing else.
| Permission | Why | What leaves your device |
|---|---|---|
| Location (approximate or precise) | Find drink shops near you; show local weather so the app can nudge you to drink more on a hot day | For search and weather: coordinates are sent at that moment to the mapping and weather providers in §8 to get results back. We do not store your device's location on our servers. |
| Camera | Scan a product barcode | The camera image is processed on your device. Only the decoded barcode number is sent to the product database (Open Food Facts). We never upload camera frames. |
| Photo library | Choose an avatar image | The image you pick is shrunk to 256 × 256 pixels on your device. It is uploaded to our file storage only if you are signed in, so that it follows you to your other devices, and is shown to other users only as described in §8.1. |
| Motion sensors | Tilt the water surface animation on the home screen | Nothing. Sensor readings are used in the render loop and are never stored or transmitted. |
| Notifications | Drink reminders you configure, and reminders from friends | Your own reminders are local notifications scheduled on your device — nothing leaves it. If you are signed in, we also register the device for push notifications so a friend's water reminder or a drink they shared can reach you: the push token (or web push subscription) and the device's time zone are stored on our servers (§3) and passed to the push services in §8.3. You can turn friend reminders and shared drinks off in Settings → Notifications. |
| Health Connect (Android, optional) | Mirror how much you drank into Google Health Connect so other health apps you use can count it toward your water intake. Only the volume is written — calories, sugar, caffeine and sodium never leave Drinkyin | Data is written to Health Connect on your device, under permissions Android grants you and you can revoke in system settings. We do not read anything back from Health Connect, and we never share Health Connect data with third parties or use it for advertising. |
You can change or revoke any of these at any time in your device's system settings. Revoking one does not delete data already saved.
6. Sensitive personal information
Some of what Drinkyin holds is more sensitive than the rest, and we treat it accordingly:
- Health-adjacent information — hydration and nutrition intake, caffeine, your allergy or "watch out for" tags, your personal intake goals, and your height and weight if you add them. Under Washington's My Health My Data Act and Nevada's SB 370 this is consumer health data; under several US state laws it can be sensitive personal data. See the Consumer Health Data Privacy Policy.
- Gender, if you choose to give it. Under some US state laws, being non-binary is sensitive personal data. It is optional ("Prefer not to say" stores nothing), only you can see it, and you can clear it at any time in Settings → Personal.
- Your date of birth — we use it only as described in §3; only you can see it, and it is never shown to other users.
- Precise geolocation — used only as described in §5, and never stored on our servers.
- Account credentials — your email and password hash.
We use sensitive information only to provide the features you asked for, to keep your account secure, and for the limited purposes permitted by Cal. Civ. Code § 1798.121(a) (such as security and preventing fraud). We do not use it to infer characteristics about you, and we do not use or disclose it for any purpose that would give you a right to limit that use. We do not sell it, share it for advertising, or use it to train machine-learning models.
We do not collect biometric identifiers, genetic data, immigration status, racial or ethnic origin, religious beliefs, union membership, or the contents of your mail, email, or messages.
7. How we use information
We use personal information only for these purposes:
- To run the Service — save and display your logs, calculate your hydration ring and daily nutrition totals, build your collection and badges, and show your history and weekly report.
- To sync your data across your devices when you sign in, and to restore it after a reinstall.
- To operate the community — show the check-ins you share, show your public profile and its sections, let people find a public profile by name or username, maintain the follow graph and follower lists, deliver friend water reminders, and act on reports and blocks.
- To answer your requests — support email, privacy rights requests, and confirming that a Business Account controls the business it names (§3).
- To keep the Service safe — detect and prevent abuse, spam, credential stuffing, and fraudulent business claims; enforce our terms.
- To improve the Service — diagnose bugs and fix them, using crash reports and error logs (§4) and what you tell us. We do not run behavioral analytics on your drink log.
- To comply with law — respond to lawful requests, keep required records, and establish or defend legal claims.
- To send service messages — sign-in codes, security notices, and material changes to this Policy. We send marketing email only if you opt in, and every marketing email identifies us, gives our mailing address, and carries a working unsubscribe link.
Automated decision-making. Drinkyin makes no decision about you that produces a legal or similarly significant effect. The reminders, nudges, and goal alerts you see are simple rules applied to numbers you entered, and you can turn all of them off.
No AI training on your data. We do not use your logs, profile, photos, or health-adjacent data to train, fine-tune, or evaluate machine-learning models, and we do not send them to any third-party AI service.
Legal bases (where required). For users in jurisdictions that require them, we rely on: performance of our agreement with you (running the Service); your consent (optional permissions, health-adjacent data, marketing, and any public posting); our legitimate interests (security, debugging, preventing abuse); and compliance with legal obligations.
8. When information leaves your device
We disclose personal information only in the situations below. We never sell it, and we never disclose it to data brokers or advertisers.
8.1 To other users — because you chose to publish it
Everything below is visible only to signed-in Drinkyin users, and never to anyone you have blocked or who has blocked you — blocking works in both directions and is enforced by our database, not just hidden in the app.
Your public profile is off by default. While it is off, other users cannot find you or see your profile, your sections, or your check-ins. When you turn it on (Settings → Account → Public profile), they can see your username, display name, avatar, and bio, and only the sections you switch on:
- Collection / Favorites — the names and categories of drinks you have tried or saved. How often and when you drank them is never shown.
- Stats — summary numbers such as how many different drinks you have tried.
- Check-ins — see the next point.
- Spots — the names of shops attached to check-ins you shared with the place shown (never the shop's location, and never from private logs or check-ins where you hid the place; a shop name stays in Spots after the check-in's 24 hours are over, until you turn Spots off), and the shops you saved as places you want to go (name, category, and the shop's address — no coordinates). Turning a section off empties our stored copy of it.
- Check-ins. Each log has its own share switch. When you are signed in, new logs start with sharing switched on, but nothing is visible to anyone unless you have also turned on your public profile and its Check-ins section, both of which are off by default. You can change the starting value in Settings → Privacy & Health ("Logs private by default"), and switch sharing off on any log. Logs made without an account are always private. A shared check-in is visible for 24 hours after the drink's time, and only while your public profile and its Check-ins section are on. It shows the time, your profile, and — unless you turned them off for that check-in — the drink (name and category) and the name of the shop you tagged. Volume, nutrition, and price are never shown to others. Making a check-in private again hides it from then on, but cannot recall what people already saw or captured.
- Follower and following lists. If your profile is public, signed-in users can open your Followers and Following lists. Those lists show only people whose own profiles are public (and leave out anyone who has a block with the viewer); the people not shown are counted ("N more aren't shown") but not named. You can hide your lists (Public profile → Followers & Following): then only people who follow you can open them, and you appear in other people's lists only to viewers who follow you. The counts stay visible. If your profile is private, nobody else can open your lists.
- One exception for private profiles. If your profile is private, your name and avatar (marked "Private") still appear in the follower and following lists of the people you follow or who follow you, when they look at their own lists — so they can unfollow you or remove you. They don't appear in anyone else's lists, and your profile page stays locked.
- Your avatar photo is stored in file storage that is readable by link: the link is random and cannot be guessed, and it appears only where your profile is visible as described above — but anyone who obtains the link can open the image without signing in, including if someone forwards it.
- Friend water reminders. If two people follow each other, either can send the other a 💧 reminder. The recipient sees who sent it. You can turn incoming reminders off in Settings → Notifications.
- Business shop pages — the business name,
@username, verified status, shop page bio, shops (name, address, hours, phone), and menu — are visible while the shop page is live. A business's menu items are visible in search to everyone. Its application and verification records are never shown. - Reports are seen only by us. The person you report or block is not told who did it.
8.2 To businesses — aggregate counts of public check-ins only
If a shop or brand operates a Business Console, it can see, for its own menu items: how many public check-ins those items received in a recent window, and how many distinct people made them. This is enforced at the database level so that private logs are invisible to businesses by construction. Businesses do not receive your identity, your email, your other drinks, your location, or any private log.
8.3 To service providers who process data on our behalf
| Provider | What it does | What it receives |
|---|---|---|
| Supabase (US, [[HOSTING_REGION]]) | Authentication and database | Your email, password hash, profile, synced logs, synced app state, business records, and request metadata including IP address |
| Vercel | Hosting for the web app / PWA | Standard request logs: IP address, user agent, requested path |
| Expo (Expo Application Services) | Builds and signs the mobile app | Build artifacts; no end-user personal information |
| Resend | Sends sign-in codes and service email | Your email address and the message content |
| Expo push service, Apple Push Notification service, Firebase Cloud Messaging | Deliver friend reminders and shared-drink alerts to the mobile app | The device's push token and the notification text (for example "Alex reminded you to drink some water" or "Alex shared Pepsi with you") |
| Your browser's push service (for example Apple, Google, or Mozilla) | Delivers friend reminders and shared-drink alerts to the web app | The device's push subscription and an end-to-end encrypted message the push service cannot read |
| Sentry (Functional Software, Inc., US) | Crash and error reporting — with or without an account | Crash reports and session records as described in §4, and request metadata. We have set it not to store IP addresses |
These providers act as our service providers / processors: they are bound by contract to use the information only to perform services for us, and never for their own purposes.
8.4 To independent third parties whose services you invoke
When you use certain features — all of which need an account (§2.1), except Health Connect, which never leaves your device — your device contacts these services directly. They are independent controllers of what they receive, under their own policies, and we receive nothing back about you.
| Service | Triggered by | What it receives |
|---|---|---|
| Open Food Facts | Scanning a barcode | The barcode number and your IP address |
| OpenStreetMap (Overpass, Nominatim) | Searching for nearby shops; naming a saved place | Your device's coordinates (accurate to roughly 100 m) or your search term, and your IP address |
| Open-Meteo | Weather-based hydration advice | Your device's coordinates (accurate to roughly 100 m) and your IP address |
| Google Places API (Text Search) | Searching for nearby shops, in builds configured with a Google key | Your search term, your device's coordinates (accurate to roughly 100 m), and your IP address. When Google is unavailable the search falls back to OpenStreetMap |
| Google Maps Static API | The map above nearby-shop results | Your coordinates (the centre of that map) and your IP address |
| Google Maps or Apple Maps (the app, or the website) | Tapping that map — in the iPhone app, Google Maps when it's installed, otherwise Apple Maps; in the web app (on iPhone too) and on Android, Google Maps | Your search term, the centre of the map rounded to about 100 m, and your IP address |
| Google favicon service | Fetching a brand logo | The brand's website domain and your IP address |
| Brand and product websites, and the image-hosting services those brands use (for example Shopify, Adobe, imgix, Cloudflare) | Showing a drink's product photo or official logo | Your IP address and standard request details (such as your device's user agent), when your device loads the image |
| Google Health Connect (Android) | Turning on health mirroring (works without an account; stays on your device) | Hydration records — volume only — written locally on your device |
| Apple App Store / Google Play | Installing and updating | Handled entirely by Apple and Google under their own policies |
Looking up drinks. When you are signed in, searching for a drink, opening a brand, and showing the drinks in your favorites, wishlist, pinned quick picks and logs ask our drink database (Supabase, §8.3) for those drinks' public details. The request carries your search term or the drink IDs and, like any request, your IP address, which our provider's request logs keep for the period in §11. Without an account the app uses the drink library built into it and sends no request for it.
If you would rather not contact these services, do not use the corresponding feature; the rest of Drinkyin continues to work.
8.5 Legal, safety, and corporate events
We may disclose information if we reasonably believe it is required to comply with a law, subpoena, warrant, or court order; to enforce our terms; to investigate fraud or abuse; or to protect the rights, safety, or property of anyone. Where we are legally permitted to, we will tell you first.
If we are involved in a merger, acquisition, financing, reorganization, or sale of assets, personal information may be transferred as part of that transaction. We will notify you before your information becomes subject to a materially different privacy policy, and you will be able to delete your account first.
9. We do not sell or share your personal information
We have not sold personal information, and have not shared it for cross-context behavioral advertising, in the twelve months before the effective date of this Policy, and we do not do so now. This includes the personal information of consumers we know to be under 16, for which US state laws would require opt-in consent — we do not have such a program at all.
We honor the Global Privacy Control (GPC) and other browser-level opt-out preference signals on our web app. Because we do not sell or share information in the first place, an opt-out signal produces no change in what we do; we recognize it as a valid opt-out request regardless.
10. Security
We protect personal information with measures appropriate to its sensitivity, including:
- TLS encryption in transit for every network request, with a hard timeout on cloud calls;
- Encryption at rest for our database and file storage;
- Row-Level Security in the database, so a signed-in account can read and write only its own logs and app state; other users' content is readable only through views that apply the visibility rules in §8.1 (public profile and section settings, the 24-hour window, and blocks);
- Salted password hashing by our authentication provider — we never store or see plaintext passwords;
- Account-switch isolation on shared devices, so one account's local data cannot be merged into another account's cloud data;
- Least-privilege access — administrative access is limited to personnel who need it, and privileged database keys are never shipped in the app.
No system is perfectly secure. Please use a strong, unique password and keep your device locked. If we become aware of a security incident affecting your personal information, we will notify you and the relevant regulators as required by applicable US state breach-notification laws.
11. Retention and deletion
| Data | How long we keep it |
|---|---|
| Local, on-device data (no account) | Until you delete it — Settings → Data → Clear data / Reset, clearing site data, or uninstalling. We never have a copy. |
| Account and profile | While your account exists |
| Synced logs and app state | While your account exists, or until you delete the individual entries |
| Note that a synced log was deleted (only its ID and the time it was deleted — none of what you logged) | 30 days, so your other signed-in devices remove it too the next time they sync; deleted with your account |
| Shared check-ins | Visible to others (in the feed and on your profile) for 24 hours after the drink's time; the underlying log is kept until you delete it |
| Public profile showcase (collection, favorites, stats, spots) | Until you turn that section or your public profile off, or delete your account |
| Avatar photo | Until you replace or remove it (the old file is deleted), or delete your account |
| Friend water reminders | 7 days |
| Push notification address | Until you sign out on that device or delete your account |
| Reports | While needed to review and act on them and to keep a record of moderation decisions (up to 24 months); a report you filed is deleted with your account |
| Blocks | Until you unblock, or either account is deleted |
| Business application and ownership-verification records | While the business account exists. Deleting your account deletes them immediately, together with your shop locations and menu items (see below). |
| Server and security logs | 30 days |
| Crash reports (§4) | [[CRASH_RETENTION]]. They carry no account details, so they are not matched to your account and are not removed when you delete it; they expire on this schedule |
| Support email | 24 months |
| Backups | Rolling backups are overwritten within 30 days |
You can delete your account yourself at any time in the app (Settings → Account → Delete account). That removes your profile, avatar photo, public profile showcase, logs, synced state, follows, blocks, friend reminders, shared drinks, push addresses, reports you filed, and business records from our live systems immediately. If you ask us by email instead, we do the same within 30 days of verifying the request. Either way, copies in backups are removed as the backups cycle out. We may retain a minimal record that a deletion request was made and fulfilled, which the law requires us to keep, and anything we must keep to comply with a legal obligation or to resolve a dispute.
12. Children and teens
Drinkyin is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has given us personal information, contact us at privacy@drinkyin.com and we will delete it promptly.
When you create an account we ask for your date of birth before anything else, and we don't create an account for anyone under 13. Your date of birth can't be changed in the app after you sign up (§3).
Users between 13 and 15 may use Drinkyin, but should do so with a parent's involvement. We do not sell or share the personal information of any user, and specifically not of any user we know to be under 16.
Alcohol. Drinkyin currently has no alcohol-logging feature: the drink library and the categories you can log do not include alcoholic drinks. Drinkyin does not sell alcohol or facilitate its purchase. If we add an alcohol feature later, it will be limited to users of legal drinking age (21 in the United States), and we will update this Policy before it launches (§19).
13. Your controls inside the app
You do not need to email us to exercise most of your choices:
- Delete a log — from Today's list or from History.
- Share or keep a log private — choose per log when you log it, or later from the log itself (within its 24 hours); hide what you drank or where you were on any shared check-in; set the default in Settings → Privacy & Health.
- Public profile — turn it on or off, choose its sections, and hide your follower and following lists in Settings → Account → Public profile.
- Report or block — from a profile, a check-in, or a business's drink; manage blocked accounts in Settings → Privacy & Health.
- Friend reminders and shared drinks — turn each off in Settings → Notifications.
- Turn off Health Connect mirroring — Settings → Privacy & Health, or revoke it in Android system settings.
- Turn off reminders — Settings → Notifications.
- Pause or delete a routine — Settings → Routines & Reminders. Drinks it already logged stay in your history until you delete them.
- Edit or remove your profile, allergy tags, and goals — Settings → Personal.
- Sign out — stops syncing on that device, removes its push notification address, and clears that account's data from the device.
- Clear local data — Settings → Data → Clear data / Reset. This clears the copy on that device; if you are signed in, your synced data returns on the next sync.
- Delete your account — Settings → Account → Delete account permanently deletes your account and everything synced to it, immediately. See our account deletion page.
- Revoke any OS permission — your device's system settings.
14. Not medical, nutrition, or safety advice
Drinkyin is a self-tracking and social tool for general wellness. Its hydration goals, nutrition totals, weather nudges, and goal alerts are informational only. They are not medical advice, not a diagnosis, and not a substitute for a qualified professional. Nutrition values are snapshots taken from public databases and from businesses, and may be incomplete or inaccurate. Never disregard professional medical advice because of something you saw in Drinkyin, and consult a professional before changing your fluid, caffeine, or alcohol intake — particularly if you are pregnant, have a medical condition, or take medication.
15. Interstate and international transfers
We operate from [[COMPANY_COUNTRY]] and store personal information on servers located in the United States ([[HOSTING_REGION]]). Crash reports are processed by Sentry in the United States. If you use Drinkyin from outside the United States, your personal information will be transferred to, stored in, and processed in the United States, where privacy laws may differ from those in your country and where courts, law enforcement, or national security authorities may be able to obtain access under the laws of the United States.
16. Your privacy rights in the United States
16.1 Rights available to you
Depending on where you live, you may have some or all of the following rights. We extend the core rights below to every US user, regardless of state.
- Know / access — what personal information we collect, the categories of sources, the business purposes, the categories of third parties we disclose to, and the specific pieces of information we hold about you.
- Portability — receive your information in a portable, machine-readable format.
- Correct — fix inaccurate personal information.
- Delete — have your personal information deleted, subject to legal exceptions.
- Opt out of sale, of sharing for cross-context behavioral advertising, and of profiling with legal or similarly significant effects. We do none of these.
- Limit the use and disclosure of sensitive personal information. We already use it only for the permitted purposes in §6.
- Withdraw consent, including consent to the processing of consumer health data.
- Non-retaliation / non-discrimination — we will never degrade the Service or charge you differently because you exercised a privacy right.
- Appeal — if we deny a request, you may appeal (§16.4).
These rights come from, among others, the California Consumer Privacy Act as amended by the CPRA, and the comprehensive privacy laws of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Rhode Island, Indiana, Kentucky, and other states as their laws take effect, plus the Washington My Health My Data Act and Nevada SB 370 for consumer health data.
16.2 California notice at collection
In the twelve months before the effective date, we collected the following statutory categories of personal information, for the business purposes in §7, from the sources in §§3–4, and disclosed them for a business purpose only to the recipients in §8:
| CCPA category | Collected? | Examples in Drinkyin |
|---|---|---|
| A. Identifiers | Yes | Email address, account ID, username, display name, IP address |
| B. Customer records (Cal. Civ. Code § 1798.80(e)) | Yes | Name, email, business contact details |
| C. Protected classifications | Yes | Age (from your date of birth) and gender, if you choose to give it |
| D. Commercial information | Limited | Drinks logged, prices you enter, wishlist and favorites |
| E. Biometric information | No | — |
| F. Internet or network activity | Yes | Server request logs, search terms, crash reports and session records (§4), feature usage needed to run the app |
| G. Geolocation data | Yes | Coordinates used at the moment of a search or weather lookup, not stored |
| H. Audio, electronic, visual, thermal, olfactory, or similar | Limited | Avatar photo you upload; camera used locally for barcode scanning |
| I. Professional or employment information | Limited | Business account contact details and ownership-verification records |
| J. Non-public education information | No | — |
| K. Inferences | No | We draw no profile or inference about you |
| L. Sensitive personal information | Yes | Account credentials; precise geolocation (sent to mapping providers at the moment of a search; not stored by us); health-adjacent intake and allergy tags |
We did not sell or share any of these categories. We retain each category for the periods in §11.
California "Shine the Light" (Cal. Civ. Code § 1798.83). We do not disclose personal information to third parties for their own direct marketing purposes.
16.3 How to make a request
Email privacy@drinkyin.com with the subject line "Privacy Request", or use the form at [[PRIVACY_REQUEST_URL]]. Tell us which right you want to exercise and which email address your account uses.
- Verification. We verify you by confirming control of the email address on the account, and by matching the details you give us against our records. For deletion and for specific pieces of information we may ask for a second confirmation. We will not create a new account or ask for extra identity documents just to verify you.
- Timing. We confirm receipt within 10 business days and respond within 45 days, extendable once by another 45 days where permitted, with notice to you.
- Authorized agents. An agent may submit a request with your signed written permission; we may still contact you to confirm.
- Deleting your account needs no request. Settings → Account → Delete account does it immediately; see our account deletion page.
- No account? If you have never signed in, we hold nothing linked to you to access or delete — your data is on your device, and Settings → Data → Clear data / Reset removes it. Crash reports (§4) carry no account details, so we cannot match them to you.
16.4 Appeals
If we deny your request, we will explain why. You may appeal within 60 days by replying to our decision or emailing privacy@drinkyin.com with the subject "Privacy Appeal". We will respond within 45 days with our decision and the reasons for it. If we deny the appeal, we will give you a method to file a complaint with your state Attorney General. California residents may also contact the California Privacy Protection Agency.
17. Where Drinkyin is offered
Drinkyin is currently offered only to users in the United States, and this Policy is written for them. We plan to make it available in more countries over time; before we do, we will add the information and rights that apply there and update this Policy as described in §19.
18. Other regions
Drinkyin is offered from and directed to the United States only. If you use it from elsewhere, you do so on your own initiative and are responsible for compliance with local law. We may add region-specific terms — for example for Canada, the UK, the EEA, or Australia — in a future version of this Policy.
19. Changes to this Policy
We will update this Policy when our practices change. The "Last updated" date at the top always reflects the current version, and we keep prior versions available at [[POLICY_ARCHIVE_URL]].
For material changes — a new category of personal information, a new purpose, a new disclosure, or anything that would reduce your privacy — we will give you notice inside the app and by email (if we have your address) at least 14 days before the change takes effect, and, where the law requires consent, we will ask for it rather than assume it.
20. Contact us
Drinkyin LLC Attention: Privacy Officer — [[PRIVACY_OFFICER_NAME]], [[PRIVACY_OFFICER_TITLE]] [[MAILING_ADDRESS]] Email: privacy@drinkyin.com General support: support@drinkyin.com
We aim to answer every privacy question within 5 business days, and always within the statutory deadlines in §16.
This document describes Drinkyin's actual data practices as implemented in version 1.0.0 of the Service. It is not legal advice. Have counsel qualified in your jurisdiction review it before you publish it or submit it to the App Store or Google Play.