Privacy policy

1. Information and purposes

Product feedback

When you submit feedback, we store your signed-in account identifier, category, message and submission time. A photo and reply email are stored only when you choose to provide them. Only the operator can review feedback. A reply email you provide is used only to respond to that feedback. Feedback, attachments and reply email are deleted when you delete your account. Feedback is optional.

Email and promotional consent

Contact emails support account notices and inquiries and are not public. Apple-linked accounts keep their previously saved contact email and preferences. If no contact is saved, we use the email verified by Apple, including Hide My Email addresses, without requesting name/email entry or additional verification. If neither source provides an email, signup and use remain available without email collection or promotional-email controls. For Kakao-linked accounts, we fill in an email shared with consent only when Kakao confirms that it is valid and verified, without additional verification. Previously saved contact emails are preserved. You can sign up without additional email entry or verification even if Kakao provides no verified email. Changing your contact email in account settings is optional. The new address is saved only after you verify a code sent to it; the old contact remains until then. Login connections and records remain unchanged. Changing to a different address turns off promotional consent; you can opt in separately for the new address. Promotional emails require a separate optional opt-in. We store the preference, consent version and change time. Declining does not affect service use; consent can be withdrawn in profile settings. Social sign-in or unrelated profile edits do not change saved contact emails or preferences. Deleting profile information or the account removes stored contact emails and preferences. Signing in with Kakao or Apple again may provide the email again with the applicable consent.

Account and sign-in

We use the Kakao app-specific user identifier, internal account identifier, and link creation time to identify accounts and authorize access to records. To simplify signup and support account notices, we store the Kakao email shared with consent and the time our server confirmed its verification. Deleting your profile information or account removes this information as well. We do not receive your Kakao password or store Kakao authentication tokens in the app database.

Nickname and records

We store your nickname and record details: drink name, category and classification, drinking date, place and place reference, photo, aroma, palate, finish, memo, price, alcohol percentage, rating, legacy preference markers, sharing setting, and creation/update times. These support saving, searching, editing, sharing, and summarizing your records. The price field is a diary entry, not payment information.

Optional profile information and age confirmation

Birth year, gender, and country are optional. Declining to provide them or consent to their collection does not restrict registration or core features such as journaling. Details voluntarily supplied with consent are used for membership and age-group statistics. Birth year is not automatically retrieved from Kakao or Apple; we do not invent or store a month or day for year-only entries. You can also remove a previously supplied full date of birth using Clear optional information in profile settings. Supplied information, derived age groups, consent versions and timestamps are retained until you remove the information or delete your account. Year-based age groups use the current year minus birth year and may differ from birthday-based age. These details are not public. Separately, users confirm that they are at least 19 and meet the service age requirement without having to disclose birth information. Confirmation is recorded through the saved registration version and timestamp. This is self-declaration, not verified adult identity.

Reports, blocks, and safety

We store reporter, author, and record identifiers; report reasons/details, submission and resolution times/status; and block relationships. These support report review, sharing restrictions, blocking, and request limits. The operator can inspect reported shared records and photos.

Connection and security information

We process sign-in cookies, server-side session token hashes, hashes of one-time login values, IP-derived request-limit hashes, account-identifier hashes and per-feature request counts, and per-account place lookup usage. Country codes and browser language help select the interface language. Hosting and security providers may process IP addresses and request information to deliver and protect the service.

Usage statistics

To calculate daily active users, first-record activation and day-7 retention, we process internal account identifiers, signup times, active dates in Korea Standard Time, last-access times and first-record save times. Active dates are stored once per member per day; background traffic does not count as a visit. The first-record timestamp remains for statistics after a record is deleted, without its content. Admin statistics show only aggregate counts and rates. Visit history and first-record timestamps are removed when profile information or the account is deleted.

Search and service diagnostics

To speed up search, the server stores characters and counts derived from records and nicknames. These are invalidated or removed when their sources change or are deleted; search results follow the original records’ access rules. App diagnostic logs contain route categories, response status and duration, not diary content, search queries or login tokens.

Email support

When you contact us, we use your sender email address, message, attachments, and correspondence to respond and handle privacy requests. Include only information needed for your request.

For accounts previously created with ChatGPT sign-in, the compatibility path may process that provider’s user identifier, email, and name. A name may remain as an author on older records.

Apple sign-in processes an app-specific identifier, link and authentication times, revocation status, and Apple-verified email and verification time. We request email permission, not name permission or your Apple password. Email supports onboarding without duplicate entry and contact, never account merging or identification. Refresh tokens needed for revocation are encrypted. A revocation notification removes the email and verification time from the Apple connection. Previously consented profile information remains until profile or account deletion.

Email verification

Verification emails are sent through Resend, which receives the email address and code. Codes expire in 10 minutes. Contact email changes are verified and saved together. We store a protected code digest rather than the code itself, plus the email, request time, attempt count and verification time. Expired requests are cleaned up during subsequent send requests or when profile/account data is deleted. Stored verification time changes or is removed when the email or profile is changed/deleted. Resends require one minute and are rate-limited by account, address and connection. Each code permits up to five attempts. Resend Privacy Policy

2. What other members can see

New records default to “Shared”. You can change this to “Only me” before saving or edit it later. Shared records display your nickname, photo, place, date, drink information, and notes to other signed-in members. Prices and cocktail ratings are visible only to the record’s author. Public average ratings exclude cocktails and unrated entries.

Blocks, moderation, and account deletion restrict access to affected records. The app cannot retrieve copies another person has already saved outside the service. Check photos, notes, and places before sharing, as they may contain sensitive information about you or someone else.

3. External services and data transfers

Kakao

Selecting Kakao sign-in authenticates you with Kakao and returns information needed to identify the account. Kakao’s policies apply within its service. Kakao privacy policy

Apple

Apple authenticates you when you select Apple sign-in. The app receives results needed for authentication and revocation. Apple privacy policy

NAVER · Google Maps

Pressing Search sends your query to the selected provider. “View place” can send the saved query to Naver or a place identifier and display language to Google for a lookup. We do not include app member identifiers, photos, or notes in map requests. Directly entered places do not trigger map lookups. Map provider policies and information

Hosting and storage

The service uses OpenAI site hosting and Cloudflare-based application, database, and photo storage services. Account information, records, photos, and requests are processed on this infrastructure to provide the service. OpenAI · Cloudflare

Support mailbox

Support correspondence is received and stored in Google Gmail and reviewed by the operator. Google privacy policy

External providers may process information outside your country, including the United States. Their policies and service terms govern processing locations and retention/deletion of security logs and backups. Deleting app records does not mean provider logs and backups are erased at the same moment. Contact us below with questions about international processing or retention.

AI translation is currently unavailable and notes are not sent for translation. If introduced, information about the data sent and its use will be updated first.

4. Retention and deletion

Apple refresh tokens are stored encrypted while linked and removed on revocation notification or account deletion. We request Apple revocation during deletion; if communication fails, remove the connection in iPhone Settings → your name → Sign in with Apple. Your Apple account itself is not deleted. One-time app return data is valid for two minutes. Hashed Apple identifiers and revocation times block delayed authentication for up to seven days; expired data is cleaned up on subsequent login or revocation processing.

• Account links, nickname, records, and photos: retained while you use the service and removed from active app data when deletion of the item or account completes. Replacing or removing a photo also triggers deletion of the old photo.
• Gender, date of birth, age band, country, and consent: retained until you remove them or account deletion completes. Updates replace previous answers.
• Sign-in sessions are valid for 30 days; one-time login information for 10 minutes. Expired values cannot authenticate you. Expired server records are cleaned up during subsequent login processing.
• Reports, blocks, and moderation information support safety and access restrictions. Relevant information is removed when a block is removed or the associated record/account is deleted. Closed reports have no separate automatic expiry.
• Per-account usage counters are replaced on the next use in a new quota period and removed upon account deletion.
• Request-limit records are valid for up to one day, depending on the feature; expired rows are cleaned in batches during later usage. Account-specific request counters are removed on account deletion. Retention of app diagnostic logs follows the hosting service configuration.
• Deletion status: the internal account identifier, deletion start time, and completion flag remain to prevent access and writes through the old identity. This status has no automatic expiry and does not include records, photos, or nicknames.
• Support email: correspondence is stored in the support mailbox. Email us to request deletion of your correspondence.

Starting account deletion disables new entries and public visibility. Account data is deleted after in-progress photo writes and cleanup finish. If you see a pending or error message, use “Account → Continue deletion” to finish. Completion is not guaranteed while the screen is closed. Completed deletion cannot be undone in the app.

Your Kakao account and consent retained by Kakao are separate and are not removed by deleting your diary account.

5. Your choices and rights

Open a record to edit, delete, or change its sharing setting. Edit your birth year, gender, and country or clear optional birth year, previous date of birth, gender and country details on the profile form. You can start full account deletion from Account settings.

You may also email requests for access, correction, deletion, restriction of processing, or withdrawal of consent. We may ask for the minimum information needed to verify you or an authorized representative. Withdrawing consent or deleting information needed for the service can limit related features.

Account deletion steps · Edit or delete demographics

6. Cookies and device permissions

Cookies maintain sign-in and verify login requests. You can sign out or clear site data in your browser. Blocking cookies may prevent sign-in from working.

We process photos you choose or take to attach to a record. You can grant camera access when choosing to take a photo, or decline and create a record without one. The app does not request your current GPS coordinates or contacts.

We use HTTPS for sign-in information, store server-side session tokens as hashes, and check record, photo, and administrative access on the server.

7. Contact and policy changes

Privacy contact: My Drinking Diary operator

mydd.cloud@gmail.com · Support page

When processing changes, this page and its effective date will be updated. Changes requiring separate consent will go through the relevant consent process.