2.1 Members (email signup)
Required: email, password (stored in encrypted form), account identifier, signup/access logs
Optional: display name (if provided)
2.2 Members (social login)
Required: social provider identifier, email (within provider scope), signup/access logs
Optional: profile information (within provider scope)
Supported providers: Google, Kakao
2.3 Guests (token-link users)
Required: tasting inputs (scores/keywords/comments), token identifier (random string), access logs
Guests are asked not to include personal information (for example, contact details) in comments. If personal data is included, it may be deleted or masked as needed. Memos and 'what fell short' notes left by guests may be transmitted to the AI inference providers listed in Section 5 when the summary line is generated, which can happen automatically when a member closes the session or when the session expires.
2.4 Automatically collected data
IP address, access logs, device/browser information, cookie/session identifiers, error logs
(with optional consent) GA4 event data and cookie identifiers (for example, _ga)
2.5 Automatically collected data (mobile app)
Android app: in-app usage events (sign-in, coffee saved, session created, insights viewed, and similar) and their parameters (sign-in method, language, internal coffee/session numbers), device/app information (device model, OS version, app version, app instance identifier), error and crash logs
iOS app: does not include analytics or crash-reporting tooling and does not collect the items above.
In-app usage analytics can be turned off at any time under "Share usage data" in the Account tab (on by default). Account identifiers and email addresses are never sent.
Error and crash records cannot be turned off, as they are required to diagnose failures; they are collected only to the extent needed to maintain service quality.
Some in-app usage events are also recorded on the Service's own servers, stored together with the account identifier.