Cupnote
Scope
This policy describes data use in Cupnote development and test releases. Feature availability depends on the distributed version and server configuration. The operator is identified below.
Accounts and guest use
Registered accounts process email, display name, a password hash, and session records. First/last names and email verification fields may be added as those flows are developed. Passwords are stored as bcrypt hashes, not plain text. Guest use creates a server account with an anonymous/device identifier; guest records are not stored only on the phone. Transferring guest records to an account depends on the registration choice.
Coffee records and preferences
Beans, brew logs, recipes, tasting notes, ratings, caffeine records, preferences, and optional image URLs are stored on the server to provide app features. Session tokens are kept in platform secure storage such as iOS Keychain; theme, language, and some favorite settings may remain in local storage. Web storage protections differ from the native app.
AI assistant
AI questions are sent to OpenAI and conversation history is stored on the server. Personal mode may also send summaries of recent brews, highly rated records, active beans, and recommendations. Do not add emails, passwords, or unnecessary sensitive details to messages. Clear disclosure and permission must be implemented before sharing personal data; this policy alone is not consent. AI and caffeine outputs are not definitive health assessments.
Subscriptions and advertising
When enabled, RevenueCat and the store provider process user identifiers and purchase/entitlement information to verify subscription status. Our app does not collect card details. If advertising is enabled, free users may see Google AdMob ads; relevant consent and privacy options depend on the release configuration. Premium status and permissions are verified with the server.
Providers, transfers, and purposes
AWS hosting, PostgreSQL, and configured email infrastructure support the service. Enabled features may use OpenAI, RevenueCat, Apple, and Google. Processing may take place in different countries; transfer mechanisms and specific legal grounds must be assessed by the operator under applicable law. Data is processed to provide the service, protect security, answer requests, and meet relevant legal obligations.
Deletion, retention, and requests
Some deleted records are initially soft-deleted; this is not immediate permanent database removal. The current account deletion UI does not yet implement a complete deletion flow. Contact support for account/data deletion requests so they can be verified and handled. This option does not replace the required in-app deletion flow. Retention, backup removal, and legal exception periods must be finalized before release. Deleting an account does not automatically cancel a store subscription.
Your rights and contact
Contact the operator for access, correction, deletion, information about processing, and objection requests under applicable law. We may need to verify that a request comes from the account owner.