Legal

Privacy Policy

Last updated: September 5, 2026

1. Who We Are (Data Controller)

Teample is a tea cataloging platform that lets you explore teas from around the world, track your personal collection, and contribute to a shared catalog.

The data controller is Teample OÜ, a private limited company registered in Estonia (registry code: [REGISTRY CODE], registered address: [REGISTERED ADDRESS]). For any matter concerning your personal data, contact privacy@teample.org.

2. Data We Collect

Account data: Your email address (encrypted at rest using AES-256-GCM), a display name you choose, and a username. We do not store your password; Firebase Authentication handles credential verification independently.

Tea data: Your teashelf entries, brew sessions, packs, purchases, and preferences. This data is stored in your private Firestore document tree and is readable only by you. Brew sessions may include optional mood tags: during a steep you can tap an emoji describing how the brew feels. Providing a mood is always optional — the prompt dismisses itself if ignored — and you can clear a mood from any past steep. Mood tags are saved to your private brew history and, unless you have opted out, contribute to the anonymized community statistics described below.

Catalog contributions: If you submit catalog entries, the submission is linked to a cryptographic ownership token derived from your identity, not your email or user ID directly. Camera submissions also include the photos you take of tea packaging (see Section 3).

Community statistics (enabled by default; opt out anytime): Anonymized brew session data contributed to global aggregates. No individual brew session is ever stored in the global dataset: only mathematical accumulations that cannot be reversed to identify you.

Approximate location: We derive approximate coordinates from your IP address at login, for weather context and time-of-day calculations. The IP address is processed transiently in encrypted form and deleted once the coordinates are derived; the coordinates are stored encrypted at rest.

Device location (off by default; you turn it on, per device): If you switch on Location Access in Settings, your device asks your browser or operating system for its position and we store that instead of the coordinates derived from your IP address. We ask only at the moment you use the switch, never when a page loads, and your browser or operating system asks you again in its own words before anything is shared. The position is rounded to two decimal places, which is roughly one kilometre, before it is encrypted; we do not keep the finer reading your device offers. It is used for the same purposes as the approximate coordinates above: weather context on your brews, the daylight bands in your Journal, time-of-day calculations, and, unless you have opted out, the anonymized community statistics described below, where it is reduced to a grid cell of about five kilometres. Switching Location Access off stops the collection, erases the stored coordinates, and returns you to the approximate coordinates derived from your IP address. Because the permission belongs to the browser, the setting is per device.

How your coordinates are protected: Coordinates of either kind are encrypted at rest with a key derived from your account, and no other user can read them. They are decrypted on your own device to show you weather and daylight, and transiently on our servers when a brew session is recorded, in order to compute your local solar time and the community grid cell. They are never shown to anyone else, never sold, never used for advertising, and never used to build a profile of you.

Guest sessions: If you use Teample as a guest, we process your email address (encrypted; a hashed form is used for lookup), a device identifier, and a temporary session token. Guest session data is automatically deleted 7 days after creation. One-time verification codes are deleted immediately after use.

3. Photos & AI Processing

When you add a tea pack using the camera feature, you photograph the front and back labels of the tea package. These images are uploaded to our EU-region cloud storage and processed automatically to extract the information printed on the label (tea name, producer, origin, harvest, certifications):

• Google Cloud Vision performs text recognition (OCR) on the images
• Google Gemini (via Vertex AI, EU region) structures and verifies the extracted text

Google acts as our data processor under the Google Cloud Data Processing Addendum; your images are not used by Google to train its models. The extracted information becomes a draft catalog submission. Registered users review and edit the extraction before deciding to submit; guest submissions are created directly from the extraction and reviewed by Teample administrators before any publication.

Photos taken with the in-app camera contain no embedded location or device metadata. Please avoid including people or personal information in your photos: photograph only the tea packaging.

4. How We Use Your Data & Legal Bases

Under the GDPR, each use of your data rests on a legal basis:

Performance of contract (Art. 6(1)(b)): providing your personal tea tracking experience, authenticating you, storing your teashelf and brew history, and processing the catalog submissions you make.

Legitimate interest (Art. 6(1)(f)): contributing anonymized brew data to the global community statistics. Our legitimate interest is maintaining an open, free, community-driven body of knowledge about tea: public for everyone, contributor or not. Contributions are pseudonymized before aggregation, published only in irreversible aggregate form with a minimum-contributor threshold, and you can opt out at any time in Settings → Privacy. We also rely on legitimate interest for service security and abuse prevention.

Public Catalog activity: Teample records aggregate counts when public Catalog entries are opened. These counts are not linked to your Teample account. This counter does not measure reading duration or external-link clicks.

Consent (Art. 6(1)(a)): publishing brew sessions to your public profile (you choose to publish, and can unpublish at any time). Note that published sessions are public web pages and may be indexed by search engines; unpublishing removes them from Teample immediately, but third-party search results and caches may take some days to clear, which is outside our control.

Consent is also the basis for device location (Section 2). It is off until you switch it on, your browser or operating system asks you separately before your device shares anything, and withdrawing consent is the same switch: turning Location Access off stops the collection and erases the coordinates it stored. Withdrawing it is as easy as giving it, and doing so does not affect anything that was lawful while it was on.

We do not sell, rent, or share your personal data with third parties for marketing purposes. We do not run ads. We do not track you across other websites.

5. Data Storage, Security & Processors

Your data is stored in Google Cloud Firestore and Cloud Storage (EU region: europe-west1). Email addresses are encrypted at rest using AES-256-GCM with a server-side master key. Location coordinates are encrypted at rest using AES-256-SIV with a key derived from your account. Firestore Security Rules enforce strict per-user access boundaries: your data is never accessible to other users.

Authentication is handled by Firebase Authentication. Passwords are never stored by Teample; Firebase manages credential hashing and verification.

Our processors are Google Cloud / Firebase (hosting, storage, authentication) and Google Cloud Vision and Vertex AI (image text extraction, Section 3), each under the Google Cloud Data Processing Addendum.

6. Your Rights (GDPR)

Under the General Data Protection Regulation, you have the right to:

Access: Download the account data available through Teample as one verified ZIP containing machine-readable JSON and CSV files from Settings → Privacy → Export My Data.

Erasure: Permanently delete your account and all associated personal data from Settings → Privacy → Delete My Account. This is irreversible and removes your teashelf, brew history, preferences, pending submissions, profile, and authentication record. See Section 7 for what happens to catalogued contributions.

Portability: Your data export is provided as documented JSON and CSV files in one verified ZIP archive, suitable for inspection and processing by compatible services.

Objection: You can opt out of community statistics at any time from Settings → Privacy. Opting out stops future contributions; events already queued may be processed at the next aggregation cycle (within approximately 30 minutes).

Rectification: You can update your profile, preferences, and tea data at any time through the application.

Restriction: You may ask us to restrict processing in the cases set out in Art. 18 GDPR by contacting privacy@teample.org.

Complaint: You have the right to lodge a complaint with a supervisory authority — in our case the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee) — or with the authority of your country of residence.

7. Data Retention

Your personal data is retained for as long as your account is active. When you delete your account, your personal data is permanently erased: teashelf, brew history, preferences, profile, pending and draft submissions, and your authentication record.

Catalogued contributions (submissions accepted into the public catalog) are retained as part of the shared catalog, but are de-identified: the ownership token and any encrypted contact data linking them to you are removed, so they are no longer personal data.

Submission images: photos of tea packaging from withdrawn, dismissed, or deleted submissions may be retained in de-identified form — all data linking them to you is removed — for catalog quality, deduplication, re-processing, and improving our automated text-recognition and extraction systems. De-identified images are anonymous and contain no personal data. If a photo accidentally contains personal information, contact privacy@teample.org with a link or description and we will delete it.

Anonymous statistical aggregates you contributed to are retained; they contain no personally identifiable information and cannot be reversed.

Guest data is deleted automatically 7 days after the session is created.

8. Cookies & Local Storage

Teample uses browser local storage and session storage for authentication tokens and application state. We do not use third-party tracking cookies. No advertising or analytics SDKs are loaded.

9. Changes to This Policy

We may update this policy from time to time. Significant changes will be communicated through the application. The "Last updated" date at the top reflects the most recent revision.

10. Contact

If you have questions about this privacy policy or your personal data, you can reach us at privacy@teample.org.