Privacy

Who handles the data

The Baristat team is responsible for the data described in this notice. Reach us at the address at the bottom of this page — we reply through that channel.

Launch-notification signup

By registering your email, you request a Baristat launch update. The website records your address; it does not send an email confirmation. This is not a newsletter subscription.

The record includes language and page context. Optional source attribution depends on analytics consent. Duplicates keep the original record and consent version. Earlier Android-specific registrations are not automatically extended to iOS.

Usage measurement

The site measures usage anonymously with Umami on every visit, with or without acceptance: pages visited, traffic sources, device type and clicks on actions such as downloading the app. Umami does not use cookies or store personal data.

With your acceptance in the consent notice, the site also stores a random identifier in your browser that links your visits in Umami. If you decline, the identifier is deleted; the choice can be changed at any time from the footer link.

Baristat never sends your email, form content or recipe parameters to the measurement tool. Your choice is stored only in your browser.

Form protection

Form submissions pass through the Cloudflare Turnstile challenge, which tells people apart from automated submissions. Challenge data is processed by Cloudflare under its own privacy policy; the site does not store it.

How long

The launch-notification signup is kept until the availability notice is sent. The site has no automatic deletion: if you ask for removal through the contact below, we delete the record manually.

Measurement data is retained by Umami under its privacy policy. The consent preference stays in your browser until you clear site data.

The Baristat app

Coffees, grinders, recipes, brews and evaluations stay in a local database, without cross-device sync. Free allows brewing without sign-in. The app uses Firebase for authentication, including anonymous access, and request protection. Federated sign-in may process a name and email.

With your optional consent, the app records acquisition and onboarding events linked to the Firebase identity, separately from pseudonymous collective contributions. Enabled notifications use a device token. The Brew Engine decides adjustments locally, without sending that decision to a language model.

Structured collective contribution (app)

Structured contribution and usage measurement are optional. On new installs they start on: the app shows the choice at the end of onboarding, after the demo, and you can turn them off at any time in Settings → Usage and brewing data without losing app access. Installs that already finished onboarding stay off until you turn them on. Disabling discards pending queues. Re-enabling does not upload earlier brews. Disabling does not erase already submitted data; use account deletion or the contact below for those records. Brewing and evaluation events use a pseudonymous installation identity, separate from account and billing identities.

Contributions exclude email, Firebase UID, RevenueCat identity, personal free-text observations, custom free-text flavor notes and local database keys. Transmission may wait for connectivity without blocking local brewing. Data is processed on Google Cloud.

Account deletion erases the data linked to the account. Collective contribution is independent from the account and stores no UID: this installation’s events are kept while the account exists and, when you delete your account, the app registers on the server the deletion of those contributions — the request remains even if the app closes or the account deletion has to be retried. After the deletion, the server keeps only a technical marker for the installation, without events, to prevent old records from being resent. Other installations and data whose local identity was lost cannot be reached; the contact address on this page remains the path for those cases.

Bari and Brew Engine (app)

Bari is an AI assistant that needs internet. To answer, it sends messages and relevant coffee, brew or recipe context to the backend and AI provider DeepSeek. It can consult local records relevant to your question within your plan’s access. Avoid adding unnecessary personal information to messages.

Before the first send, Bari asks for specific permission to share this data. You can withdraw it using the privacy button in Bari; new sends stop, but already transmitted requests may finish. Withdrawal does not erase history or previously submitted data. Raw messages, visible responses and reports stored by Baristat expire after 30 days; TTL deletion is asynchronous and may occur after expiry. This period does not describe DeepSeek’s independent retention. Local conversations, operational records and reports have separate handling; they are not collective contribution data. Bari does not decide Brew Engine adjustments. Account deletion does not imply erasure of infrastructure records without a searchable account link.

Pro subscription (app)

Google Play on Android and the App Store on iOS process subscriptions. On iOS, you can purchase and restore through the App Store without personal registration; Sign in with Apple is optional. RevenueCat verifies Pro access with a platform-specific technical Firebase identity, including anonymous identities on iOS. It is neither your email nor the collective identity. Baristat does not receive card details. Pro does not transfer between Android and iOS.

Sharing and international transfer

These services use Cloudflare for the website and signup, Google/Firebase for authentication, protection and backend, Umami for website analytics, DeepSeek for Bari, and RevenueCat and the stores for subscriptions. Providers may process data in other countries. Infrastructure logs may include IP, browser agent and URL; they are separate from product records.

Your rights

You can ask for access, correction or removal of data that identifies you, and revoke any consent you have given, through the contact below. We reply through the same channel. Signup removal is done manually by us, on request.

What we do not collect

The launch form does not ask for card details, address, telephone number or precise location. Our website events exclude email, Bari messages and free text. Account, billing and collective contributions keep separate identities.

Changes to this notice

If this notice changes, the new version is published on this page with an updated effective date.