TASSE
For cafes Guides Baristas Rooms

Privacy Policy

Last updated August 9, 2026

This policy describes what the Tasse iOS app and this website (tasse.coffee) actually do with your data. It's written in plain language and kept accurate to the app's real behavior, not aspirational — where something isn't built yet, we say so.

What we collect, and where it goes

Photos. Photos you take of coffee bags and cups are stored only on your device by default. They leave your device only when you explicitly choose to post a check-in to the Tasse website ("Check in") — up to 8 photos per check-in, uploaded to cloud storage. Once published, a photo's web address is not guessable and not listed publicly, but it is not private: today, deleting or editing a published check-in does not delete its already-uploaded photos. We're aware of this and plan to fix it; until then, please treat "Check in" as a one-way, public action for the photos you include.

Location. The app uses your device's location, when you allow it, to record where you drank a cup and to fetch local weather. This stays on your device — cross-device sync isn't built yet, so today it never leaves your phone as part of your tasting history. Three exceptions, used only in the moment you ask for them: searching for nearby cafes sends your current coordinates either to Google's Places API, when a Google Places key is configured for the build, or otherwise to Apple Maps (MapKit) — which is what a build with no Google Places key configured uses, the default in this repository's own project settings; turning your coordinates into a neighborhood or city name for display uses Apple's own reverse-geocoding service; and weather lookups send your coordinates to the Open-Meteo weather service (no account, no authentication, in any of the three cases). A check-in you post never includes your personal location, weather, or who you were with — only the cafe's own address.

Accounts. You can sign in with Apple, Google, or an emailed one-time code. We store your email address, display name, an optional bio and location you type in yourself (not GPS), an avatar color, and an identifier from your sign-in provider so we can recognize your account. We do not store a profile photo, and the iOS app itself does not include any third-party analytics or crash-reporting SDK — there is no such tracking code in the app. (The website's own lightweight, first-party measurement is described separately below.)

What you publish. Posting a check-in to tasse.coffee is always something you choose to do, one check-in at a time. Only a curated part of your tasting is sent: the cafe, when you were there, and — if you add them — your cupping score, brew method, the coffee's name, your notes, brew details, and any photos you pick — never your private location, weather, or companion notes, and never your full local history.

The website itself (tasse.coffee). Beyond what's described above for published check-ins, the website sets a few cookies: one to keep you signed in, one to remember your language preference, and — for visitors to the cafe-guide pages — a 30-day cookie that assigns you to one of two page-layout treatments for a small, first-party experiment. We record aggregate, non-identifying counts for that experiment (which treatment, what happened, and when — no user ID, no cross-site tracking) to see which layout works better; we do not use any third-party analytics or advertising SDK on the website or in the app. Separately, the website lets you choose to do more than publish check-ins: creating a public barista profile (with photos, work history, and competition record), submitting a hire enquiry to a barista (this shares your note, and a job-posting link if you include one — not your email address; if you instead request the barista's hiring contact email and they approve, it's their own email, which they've chosen to make available for hiring purposes, that gets revealed to you), connecting with other tasters, and posting in community rooms and threads are all things you actively choose to do, and each publishes what you write in the same opt-in spirit as "What you publish" above.

Third-party services we use

These are the third-party services we use, and what each one receives:

  • Apple — for signing in with Sign in with Apple; for turning your coordinates into a neighborhood or city name (reverse geocoding); and, whenever a build has no Google Places key configured (the default in this repository), for finding nearby cafes from your current location via Apple Maps.
  • Google — for signing in with Sign in with Google, and, when a Google Places key is configured for the build, for finding nearby cafes from your current location via Google Places.
  • Open-Meteo — weather for your current coordinates, no account information sent.
  • Open Food Facts — the barcode number when you scan a bag, to look up product information. No account information sent.
  • Roaster websites — a plain, one-way page fetch when the app reads a bag's product page for details. No account information sent to the roaster.
  • Our cloud hosting and storage provider (Amazon Web Services) — two things: the photo bytes for a check-in's photos, once you post it, so they can be served back to anyone with the (unguessable but not private) link; and, because the service runs on AWS infrastructure, our database — which holds account data (like your email address and display name), your published check-ins, and the other content you create on the website described above — is continuously backed up to AWS storage as a routine, automatic part of running the service.
  • Our email delivery provider — your email address, only to deliver a sign-in link or one-time sign-in code.
  • YouTube and Vimeo — some guide pages include a video, embedded directly from youtube.com or player.vimeo.com. If you view one of those pages, your browser loads the video player straight from YouTube or Vimeo, which can set their own cookies and receive your IP address and browser details, governed by their own privacy policies — not ours. This is separate from the analytics/advertising SDKs mentioned above: we don't add any tracking of our own to these pages, but the video itself is served by YouTube/Vimeo, not by us.

Your choices

Publishing is always opt-in and reviewed by you before it happens, check-in by check-in. To request that we delete your account or the data we hold about it, email us — see Contact below. In-app self-service account deletion and data export are planned but not built yet; until they ship, email is the way to reach us for this.

Children's privacy

Tasse is not directed at children under 13, and we do not knowingly collect information from them.

Changes to this policy

If this policy changes in a way that matters, we'll update the "last updated" date above. This is a young, actively-developed app — expect this page to keep pace with what's actually built, including the gaps we've called out above as they get fixed.

Contact

Questions, deletion requests, anything else: greatgatsby@gmail.com