1. Scope
This Policy explains how Santa Hirose (the “Operator”) handles information in the Cuppest coffee-recording app (the “App”).
2. Information we handle
- Account: Firebase UID, Google or Apple authentication identifiers, and account details supplied by the provider.
- Coffee content: CoffeeRecords, ratings, Taste Balance, Favorite, flavors, notes, brew details, dates, prices, visibility, and Bean/Shop relationships.
- Shared catalog: Bean, Shop, Roaster, and Offering metadata, locations, contact links, images, and internal audit fields.
- Other data: selected or captured images, stated preferences, explicit foreground location use, local recent searches, reports, moderation and deletion-job records, analytics events, and SDK diagnostics.
3. Purposes
We use information to authenticate users; synchronize, back up and display records; operate the shared catalog, search and Map; calculate Taste, Preference and deterministic Recommendations; process images; prevent abuse; handle reports and deletion; secure the service; and improve reliability and usability.
4. Public and private data
The canonical CoffeeRecord is private and account-linked. Only a Record marked public and active is copied to an anonymous public projection. That projection contains no owner UID, email address, or public-profile identifier. Bean, Shop, Roaster and Offering metadata is a shared catalog; internal creator and updater identifiers are retained for audit and moderation.
5. Location
The App requests foreground location only after an explicit current-location or Near action. It does not request background location or continuously track movement. Current coordinates are used on-device for distance, Map and Recommendation and are not saved to Firebase or Analytics as the user’s location. A UID-scoped offline Recommendation snapshot may remain locally.
6. Photos and OCR
The App processes only images the user selects or captures. It removes EXIF metadata and uploads compressed display and thumbnail images, not the source original. Private Record images remain owner-only; eligible public Records have a public rendered mirror; Shop images are shared catalog images. Google ML Kit performs text recognition on-device and OCR output is not stored as a separate cloud document.
7. Analytics
Firebase Analytics receives automatic app/session information and enumerated interaction events. Cuppest does not put raw searches, notes, Bean/Shop names, URLs, images or current coordinates in custom events and does not set the Firebase Auth UID as an Analytics user ID. There is no advertising SDK, ATT request or cross-company tracking.
8. Service providers
The App uses Google Firebase (Authentication, Firestore, Storage, Cloud Functions, Analytics and App Check), Google Sign-In, Sign in with Apple, Google Maps SDK for iOS, Google ML Kit Text Recognition, and Apple Core Location, Photo Picker, Camera and Share Sheet. App Check processes App Attest or DeviceCheck attestation data to verify legitimate app access. See External Transmission.
9. Retention
Personal records, private images, profile data and preferences are retained while the account is active or as needed for sync, safety and service delivery. Account deletion hard-deletes owned records and related images and public projections. Shared catalog entries and safety/audit records may be retained for integrity, abuse prevention and legal claims. Firebase Analytics and SDK retention follows the applicable service settings and policies.
10. Account deletion
Deletion is available in the App after reauthentication. A durable server job deletes owned CoffeeRecords, private Storage, public projections and mirrors, the private user document, stated preferences, legacy profile data and private community observations, then deletes Firebase Authentication. Applicable Apple authorization is revoked. Shared catalog, reports/audit records and deletion-job records may remain. See Account Deletion.
11. Your choices and rights
You can view, edit, change visibility and delete your own Records, revoke system permissions, and delete your account in the App. Contact us for requests available under applicable law. We may verify identity and limit a request where required by law, safety or the rights of others.
12. Security
We use Firebase Authentication, Firestore and Storage Rules, owner isolation, anonymous public projections, App Check, image processing and deletion jobs as reasonable safeguards. No method of transmission or storage can be guaranteed completely secure.
13. Children
Users must obtain parental or guardian consent where required by local law. The App is not intended to knowingly collect personal data from children below the age at which consent is legally required.
14. International processing
Firebase, Google and Apple may process information outside the user’s country. Processing is subject to applicable law and the safeguards provided by those service providers.
15. Changes
We may revise this Policy when the App, law or data handling changes. Material changes will be communicated in the App or by another appropriate method, and the effective date will be updated here.