Privacy policy

Last updated 12 October 2026

This site asks for an email address if you want an invite, and nothing else. The app keeps the coffee diary you write in it — and keeps it to yourself unless you share a brew with someone. Neither one runs analytics, sets a tracking cookie, or sells anything to anybody.

Who this is about

Jittery is run by Folva (938 341 591). This policy covers the site you are reading now at www.jitteryapp.co, and the Jittery app, on the web and on iPhone. Both versions of the app share one account and work the same way, so everything said about "the app" below applies to both.

If anything here is unclear, or you want something removed, write to hello@jitteryapp.co and a person will read it.

This site

The invite form

The "Request an invite" form on the front page asks for two things:

• Your email address, which is required — there is no way to tell you the app is open without it.
• A message, which is optional and entirely up to you. Whatever you write here, we read. Please don't put anything sensitive in it.

When you submit the form, those two fields are sent to an email inbox we control. Nothing is written to a database, an advertising audience, or a mailing-list tool — the request arrives as an email and sits in that inbox until it is answered or deleted.

The legal basis is your consent: you type an address in a box marked "request an invite" and press send. You can withdraw it at any time by asking us to delete the request.

Your IP address

The form is rate-limited, which means the server briefly holds your IP address in memory to count your requests. It is not written to a permanent log by us, it is not attached to the email that reaches the inbox, and it disappears when the counter expires or the server instance is recycled, whichever comes first. The legal basis is our legitimate interest in not having the form abused.

Nothing else

No cookies are set by this site. There is no analytics script, no tag manager, no advertising pixel, no session recording, no fingerprinting. If your browser shows a cookie banner on this page, something is wrong and we would like to hear about it.

The app

Signing in

There are no passwords. You enter your email address, we email you a one-time code, and you type it in to sign in. Your address is your account, and the code is the only way in.

Entering an address that isn't registered yet creates an account. Nothing else is asked for at that point. A display name is optional, and until you set one, your buddies see your email address in its place.

We also use your address to tell you about the app itself, for example if something breaks or this policy changes in a way you need to know about. There is no marketing list, and we don't send newsletters.

What it keeps

Everything below is something you typed, picked, or photographed. Nothing is inferred about you from anywhere else.

• Your account — your email address, the display name you choose, and optionally the city and country you call home.
• Your brews — the bean and roaster, the brew method, how you took it, your rating, your note, the date, the roast date, where you had it (manually, no location tracking), and a photo if you added one.
• Trips — if you use travel mode: the city or country and the dates. A brew logged during a trip is stamped with that place (manual tag, no location tracking), so your diary shows where you drank it.
• Brew buddies — who you're connected to. Buddy connections are made by exact email address, so both people's addresses and display names are stored on the connection.
• Shared brews — when you share a brew with a buddy, a copy of that brew's details is stored for them, alongside your name and email as the sender.
• Coffees you add to the catalogue — the coffee itself (see below), plus a record of which account added it. That record is there so that if someone fills the catalogue with junk, we can find and remove what they added. Who added a bean to the catalogue is not visible to other users.
• Suggested edits — if you suggest a correction to a coffee, the suggestion, any note you wrote with it, and which account sent it are saved and available to admins.
• Usage counters — the app limits how often an account can scan a label or add new coffees. To do that, it records that it happened and when. It never records what was in a scan. Only the last hour is ever counted. Older records are cleared the next time you do the same thing, and all of them go when you delete your account.

The legal basis for keeping your diary is our contract with you: it is the thing you signed up for. The record of who added a coffee, and the usage counters, rest on our legitimate interest in keeping a shared catalogue free of abuse.

Who can see it

Your brews are yours

Your diary is private by default. Unless you share a brew yourself, no other user can read your brews, your trips, your ratings or your notes.

Sharing changes that, for that brew

Sharing a brew with a buddy copies its details to them — bean, method, rating, your note, the café. They keep that copy, and it stays with them even if you later change or delete your own.

Your buddies see your email address

Buddying works by exact email address, so a buddy connection stores the address and display name of both people. If you send someone a buddy request, they learn the address you signed up with.

Beans and roasters are a shared catalogue

When you add a coffee or a roaster that isn't in the app yet, that entry becomes part of a catalogue everybody uses — readable by anyone, signed in or not, including its description and photo. Other users never see your name or email on it. The app keeps an internal link from a coffee to the account that added it, and that link can't be traced back to you by anyone else using the app. Your brews of it stay private. But the entry itself is public and stays in the app, because other people's brews point at it.

Photos sit in public storage

Photos you upload, such as a bag of beans, are stored in a bucket that allows anonymous reads. The file names are random, nothing links to them, and no listing of them is exposed. Treat an uploaded photo as something you have published rather than something you have filed. Do not upload a photo that you do not own: don't use images of bags found on the internet, don't use AI-generated images. If you need a photo taken down, request a change on a bean or email us.

What admins can see

Admins can see a list of accounts: each email address, display name, how many brews it has logged, and whether it has ever signed in. They can also see suggested edits and who sent them. They use this to run the app, help when something goes wrong, and deal with abuse. They do not browse anyone's diary.

Photos and what's stripped out

Every image is re-encoded before it is uploaded, which discards the metadata a camera writes into a file — model, timestamp, and on a phone with location services on, the GPS coordinates of where the photo was taken. If the re-encoding fails for any reason, the upload is refused rather than falling back to the original file. This applies equally to a photo picked from your iPhone's library, which arrives with its location data intact and is stripped the same way.

On your iPhone

The iPhone app asks for two permissions, and only when you use something that needs them: the camera, to photograph a coffee bag or a bean, and your photo library, to pick an existing photo of one. It sees only the photo you take or pick, never the rest of your library. You can turn either permission off in iPhone Settings and the rest of the app keeps working.

The app keeps a sign-in token in the app's own storage on your phone so you stay logged in. Signing out or deleting the app removes it.

If you are testing the app through Apple's TestFlight, Apple may send us crash reports and any feedback you choose to submit, under Apple's privacy policy. You control whether crash reports are shared in your iPhone's settings.

Reading a coffee bag

If you photograph a bag to fill the form in automatically, that photo is sent to Anthropic's API, which reads the label and returns what it says — the coffee's name, roaster, origin, process, tasting notes. The photo is sent for that reading and nothing else: it doesn't go into your taste profile, and no account of yours exists on Anthropic's side.

City suggestions

The city fields in travel mode suggest place names as you type, which means the few characters you have typed so far are sent to Open-Meteo's geocoding service. No account, no key, and nothing identifying goes with it — just the fragment. Both fields accept free text, so if the lookup is down or has never heard of the place, you type it anyway. Country names come from a list inside the app and are never looked up.

Who else sees any of this

Four companies handle your data on our instructions, and none of them may use it for their own purposes: Supabase (the database and the storage the photos sit in), Vercel (hosting), Brevo (handles emails), and Anthropic (reads a bag label, only when you scan one).

Two more are contacted by your browser rather than by us, so they see your IP address the way any server does when you fetch a file from it: Google Fonts loads two typefaces on this site (the app carries its own copies and never contacts Google), and Open-Meteo suggests city names while you type one. Neither sets a cookie.

Where it all lives

The database, the sign-in system and the uploaded photos are hosted in the EU, and Brevo, which sends the mail, is a French company. So the diary itself — everything you have typed into the app — stays inside the EEA.

Three of the companies above are US-based, so some things do leave: a bag photo you choose to scan goes to Anthropic, the hosting is Vercel's, and this site's typefaces come from Google. Those transfers run on the standard contractual clauses in each provider's data processing agreement — the arrangement the EU provides for exactly this.

No tracking, anywhere

Neither the site nor the app loads a third-party script — the app enforces that with a content security policy that permits scripts only from itself. There is no analytics package, no advertising network, no cross-site tracking, and no profile of you being assembled anywhere. The app stores a sign-in token in your browser, or on your phone, so you stay logged in. That is all it keeps on your device.

How long things are kept

• Invite requests — kept in the inbox until the invite is sent and answered, then deleted. Ask sooner and they go sooner.
• Your diary — for as long as your account exists.
• Usage counters — cleared once they fall outside the last hour, the next time you do the same thing, and all of them when your account goes.
• Catalogue entries and uploaded photos — these stay, because the rest of the app points at them. A photo that ends up attached to nothing — replaced by a better one, or left behind by a failed save — is swept periodically. See below for what that means when you leave.

Deleting your account

You can delete your account from your account settings, in the app, without asking anyone. It asks you to confirm, and then it goes.

What goes with it: your sign-in, your profile and your home city, every brew you have logged, your trips, your buddy connections, any brews you shared or were sent, your suggested edits, and your usage counters. The link between your account and any coffee you added is erased.

What stays: coffees and roasters you added to the shared catalogue, and the photos attached to them. Once your account is gone, nothing connects them to you. Other people's brews point at them, so removing them would take other people's diaries with them. If a photo of yours needs to come down as well, email hello@jitteryapp.co and we will remove it by hand.

One thing worth knowing before you share a brew rather than after: a buddy who accepted a brew from you keeps their own copy of it, and that copy records your name and email as the person who sent it. Deleting your account does not reach inside someone else's diary to edit their record of a cup you drank together — the same way deleting your own copy of a message doesn't remove theirs.

Backups roll off on their own schedule, so a copy may survive in one for a short period after deletion before it is overwritten.

Your rights

You can ask us to show you what we hold about you, correct it if it's wrong, delete it, or stop using it in a particular way. You can also ask for a copy of what you gave us in a portable form. Write to hello@jitteryapp.co and we will answer within a month.

If you are unhappy with how we handle that, you can complain to your own country's data protection authority. Ours, as a Norwegian company, is Datatilsynet.

Changes to this policy

If this policy changes in a way that matters, the date at the top changes with it.

Getting in touch

Questions, corrections, deletion requests: hello@jitteryapp.co.