Privacy
Last updated 20 October 2026
Slurp is a cupping instrument. It keeps your scores on your device, and it sends data to our servers only when a feature needs another device to see it. There are no ads, no analytics SDKs and no tracking.
Who we are
Slurp is made and run by Edgar Gonzalez, an individual trading as Slurp, of 62 Kendal House, Collier Street, London N1 9DE, United Kingdom, who is the controller of the data described here. "We" and "us" in this policy mean him. For anything about your data, write to the address below.
What stays on your device
Your cuppings — scores, descriptors, notes, coffee names and session codes — live in a local database on the phone (or in your browser, on the web). Sign-in tokens live in the platform keychain. You can delete everything from Settings, and uninstalling the app removes it all.
Live cupping rooms
When you host or join a table with a session code, the names cuppers enter and their scores are relayed through a room on our servers so the host can see progress and reveal identities. Cuppers never see each other's scores before the reveal. Room data is kept until the host ends the event or deletes the room.
Cloud backup of past cuppings
With Pro (or a team, or the trial), finished cuppings are backed up to our servers under your account and sync across your devices; on Free they stay on the phone. "Clear all past cuppings" in Settings, signed in, deletes your account's copies on the server too. Until 17 October 2026 the app also backed finished cuppings up under a random device identifier it generates, with or without an account; those copies stay on our servers until you ask us to delete them (slurping.coffee/delete-data).
Signing in
Accounts are optional. Signing in uses your email address and a one-time code we email you; the code expires in ten minutes and the sign-in lasts thirty days unless you sign out. We store your email address to identify the account. Emails are delivered by Resend, our email provider.
Teams
A team shares one cloud. When you create or join one, your cloud cuppings, register, events and documents become the team's, and every member can read them and the team's Insights; members see each other's email addresses. If you leave or are removed, what you brought stays with the team. The cuppings on your phone stay yours.
Payments
Slurp’s paid plans are sold by Paddle, our merchant of record. Paddle receives the email address and the account's id with the payment details given to it, and keeps the records of the sale the law asks of a seller, under Paddle's own privacy policy; we receive from Paddle the plan, its dates and its status, or the Championships bought, never the card.
Demo requests
If you ask for a demo of the Championship, what you type in the form (your name, email address, organisation, the event’s date and size and your message) is emailed to us through Resend and kept only in our mailbox, to answer you; nothing of it is stored on our servers but, for one minute, a one-way hash of your address and of your connection, so the same request is not sent twice. Write to us to have it deleted.
Event backups
An organizer's event is saved to our servers so another device can carry it on. It opens with the event's host link or host code, or for the account that created it; we can read it, as we can read the scores of a live table. A setup that has not started yet is saved the same way. We keep, beside the backup, the event's name and the account that created it, so its other devices can list it, and we email that account the event's links and a printable event pack when it starts, its results report when the results are out, and a note when another device takes control of the event or its host link is reset. A backup is deleted when its event is cancelled or closes, when its setup is discarded, when the account is deleted, or ninety days after its last update. The event's record stays after its backup goes: its name, the account that created it, when it started and closed, and, for an event started on the web or in the desktop app, roughly where it was started from (the country, region and city its connection came from, as our hosting provider places it; never GPS or the device's location; the phone apps never record it). It is deleted with the account.
Sharing an event
An organizer can share a finished event with one other account, by a link made for that account’s email address or through our support. The email address goes in the invitation, which is valid for thirty days and kept until ninety days after that, with whether it was emailed or accepted; if the organizer asks us to send it, the email goes through Resend. Accepting copies the event’s tables — every judge’s sheet and name, as the organizer holds them — into that account’s cloud (its team’s, when it belongs to one), where they stay as its own until it deletes them.
Error reports
When the app or the site hits an error it cannot recover from, it sends us what broke: the error's message and where in the code it happened, the app's version and build, the platform and its version (on the web, the browser's), and the page you were on. Nothing that names you or your device travels with it, and nothing of a cupping. We keep these reports for thirty days and, for up to a minute, a one-way hash of your connection and of the message, so one fault is not reported over and over.
Where data is processed
Everything runs on Cloudflare (Workers, Durable Objects and D1), which processes requests at the edge location nearest the device and stores account and backup data in Cloudflare's regional storage.
App updates
The phone apps check Expo (expo.dev), our update provider, for fixes we publish between store releases. Each check sends the app's version and platform and a random identifier the update system creates for the installation; it carries none of your cuppings, your account or your email.
Notifications
If you allow them, a phone that joins an event as a judge gives that event's room a push address for the phone, with the app's language, so the room can tell you when the organizer resumes an event they paused. The address is kept on your seat in that room only and is deleted with the room, or as soon as your phone leaves the event; switching Event notifications off in Settings, or refusing them in the phone's settings, takes it back the next time the phone connects. Notifications travel through Expo's push service (expo.dev) and then Apple's or Google's; they carry the event's name and that it has resumed, never your scores.
Cookies and browser storage
Slurp sets no cookies. On the web, the sign-in and your settings are kept in the browser's own storage, which the site needs to work. Paddle's checkout, when you open it, sets its own cookies under Paddle's policy.
Security
Everything travels encrypted (HTTPS and secure WebSockets) and is stored on Cloudflare, which encrypts it at rest. Sign-in codes and session tokens are kept on our side only as one-way hashes, so a copy of the database cannot sign anyone in.
Transfers outside the UK and the EEA
Cloudflare, Resend, Expo and Paddle may process data outside the United Kingdom and the European Economic Area, the United States included. Each does so under its data processing terms, which carry the European Commission’s Standard Contractual Clauses and the UK’s International Data Transfer Addendum, or under the EU–US Data Privacy Framework and its UK extension where the provider is certified.
What we never do
We do not sell data, show ads, run analytics or advertising SDKs, fingerprint devices, or share your data with anyone other than the providers named here, which act only on our instructions.
Your rights
You can export your cuppings as PDF, delete them, and delete your account in Settings or by writing to us. Requests under GDPR or similar laws — access, correction, erasure, portability — go to the contact below and are answered within thirty days. You can also complain to the Information Commissioner’s Office (ico.org.uk) or to the data protection authority where you live.
Children
Slurp is a professional tool and is not directed at children under 16.
Changes
If this policy changes in a way that matters, the app and the site show a notice and the date above moves.
Contact: hello@slurping.coffee