Privacy

You can read every recipe and water profile on this site without an account, and without telling me anything about yourself.

If you make an account, I store what is needed to sign you in and whatever you choose to publish. There is no advertising here, nothing is sold or shared with data brokers, and there are no advertising or tracking cookies.

The section you should actually read is What other people can see. Some of it is less obvious than it looks.

One-way Valve operates this site and decides what is done with the information described here. Questions, requests, or complaints: connect@onewayvalve.coffee.

If you are just browsing

Nothing you hand over directly. My host receives the ordinary technical details any web server receives in order to answer a request — your IP address, your browser, and the page you asked for.

If you create an account

• Your email address and a password, if you sign up with email. Accounts are handled by Supabase Auth; your password is stored by them as a hash, and this site never sees it.
• Your Google account's name and email address, if you sign in with Google instead.
• A username you choose (email sign-up) or the name on your Google account (Google sign-in). This is the name shown beside anything you post.

What you do while signed in

• Recipes and water profiles you submit — every field you fill in, including notes, tags, source links and image addresses.
• Comments you post, including the grinder and grind size, which are optional. These are kept so they can later be turned into grind suggestions on a recipe.
• Which recipes and water profiles you favourite.
• Which comments you upvote.
• The time each of those happened.

Nothing is inferred about you, and no profile of your interests is built or sold.

Anyone at all — signed in or not — can see the following. Please read this before you sign in, not after.

• Your username or display name.
• Every recipe and water profile you submit, shown with your name.
• Every comment you post, shown with your name.
• How many people have favourited a recipe or water profile, and how many have upvoted a comment — as a total only, never as a list of who.

Not visible to other users: your email address, your password, which recipes and water profiles you have favourited, and which comments you have upvoted. Those last two are readable only by you.

• A sign-in cookie, set when you log in and refreshed while you are using the site, so you stay signed in between pages. Clearing it signs you out. It is the only cookie this site sets.
• Your light/dark preference, saved in your browser's local storage so the site does not flash the wrong theme on load.
• An offline cache of pages, images and data, stored by the site's service worker so it keeps working without a connection and loads faster on repeat visits. It stays on your device. Clearing your browser's site data removes it.

No advertising cookies, no tracking pixels, and no session or screen recording.

• Supabase — the database and the account system. Everything in What is collected is stored there.
• Vercel — hosting. Receives the ordinary request data needed to serve a page.
• Vercel Speed Insights — measures how quickly pages load. It runs on every page and reports timing measurements. It is used to find slow pages, not to identify you.
• Google — only if you choose to sign in with Google.
• YouTube — recipe pages can embed the source video, but only once you have allowed it. Until then nothing is requested and Google is not contacted at all. After you allow it, opening a recipe with a video sends a request to Google, which can see your IP address and browser; it goes through the no-cookie player, so the cookies it would otherwise set for advertising are held back unless you play the video. That processing is Google's and is covered by Google's privacy policy, not this one. You can change your mind below.
• Whoever hosts a recipe's image — images are loaded straight from the address whoever submitted the recipe entered, usually a roaster's own site. Your browser contacts that server directly, so it can see your IP address and browser, exactly as if you had visited it. These hosts are not chosen or controlled by me.

Embedded videos are the only thing here that needs permission before it loads, so it is the only thing you are asked about. The sign-in cookie is needed to keep you signed in, and the light/dark preference is something you set yourself — a question about either would be noise that teaches people to dismiss the box without reading it.

Account details are kept for as long as the account exists. Recipes, water profiles and comments are kept until they are deleted — by you, or by a moderator if something breaks the rules. Favourites and upvotes are kept until you undo them or the account is deleted.

• A comment: delete it from the comment itself. It is removed from the database, not hidden.
• A recipe or water profile you submitted: delete it from its page.
• Your whole account: there is no button for this yet. Email connect@onewayvalve.coffee and it will be done by hand. Deleting an account removes your profile, comments, favourites and upvotes. Recipes and water profiles you submitted are a separate decision, because other people may have favourited or built on them — say in your email whether you want them removed as well or left in place without your name, and that is what will happen.

Depending on where you live, you may have the right to ask for a copy of your data, to correct it, to have it deleted, to restrict or object to what is done with it, or to have it sent to you in a portable form. To exercise any of these, email connect@onewayvalve.coffee. There is no charge, and a reply should come within 30 days.

If you are in the UK or the EU and are unhappy with the response, you can complain to your national data protection authority.

This site is not aimed at children and accounts are not knowingly created for anyone under 16. If you believe a child has made an account, email the address above and it will be removed.

When this changes, the date at the top changes with it. Anything material — a new service receiving data, a new category of information collected — will also be noted in the changelog, so it is visible rather than quietly edited in.