Privacy

Your game stays in your browser

Kettle Quest has no accounts, no sign-up, no ads and no tracking scripts. Everything the game remembers is saved in your own browser's local storage, on your device, and is never sent to us, unless you join a party. Then only the short summary described under Parties is shared.

What your browser stores

Your table: the diet and the allergens you choose to avoid.
Your hero: name, class, the dishes you've logged, XP and titles.
Your week: the nights you cook, what's done, your party's first names if you type them, each day's d20 and your Hearthfire.
Your fridge: the ingredients you've ticked, plus whether sound is on.
Your book: recipes you import from other sites.
Your party key: if you start or join a party, a random key that lets this browser speak for you in it. A save code includes it, so don't share your save code.

Clearing your browser's site data erases all of it. Some browsers, Safari in particular, may clear it on their own if you haven't visited for a while, so your progress isn't guaranteed to last.

What the server sees

Like any website, the server that sends you these pages, and Cloudflare, which sits in front of it, see standard request details such as your IP address, the page you asked for and your browser type. These are kept only as ordinary server logs and are not used to profile you. The fonts load from Google Fonts, which sees the same kind of request.

Importing a recipe

When you import a recipe, the link you paste goes to our server, which fetches that page, reads the recipe card the site publishes for search engines and sends the recipe back to your browser. The server keeps neither the link nor the recipe, and its import log records only the recipe site's name and whether it worked. The recipe site sees a request from our server, not from you.

Parties

A party is optional. If you start or join one, our server keeps what the party needs to play together, and shows it only to the people in it:

your cook's name, class, level and title, and the party's name and invite code
each week: the nights you plan and cook, the dish names, the XP and the hits on the boss
the days your Hearthfire was lit over the last six weeks, and the table's d20 for each day
the toasts you give and the recipes you pass (picked from fixed lists: there is no chat)

It does not keep your email (there isn't one), your IP address or your location, and your diet, allergens, fridge, fitness answers and imported recipes stay in your browser. Week summaries are deleted after five weeks, toasts after 14 days, and a party nobody opens for 90 days is deleted whole. Leaving a party deletes everything you shared with it straight away. A party's leader can remove a member and change the invite code.

Health Connect and Apple Health

Only in the Kettle Quest phone app, and only if you turn it on: the app reads your daily step count and your workout sessions (type, start and length) from Health Connect or Apple Health, so a walk or a strength session your phone or watch recorded ticks off that day's road or forge. It reads nothing else: no heart rate, sleep, weight or calories. It is read on your phone and used on your phone. No step count or workout is stored by the app or sent to us or anyone else; only the tick is kept, and in a party your friends see a hit on the boss, the same as a day you tick by hand. You can stop it under Fitness road in “Adjust the week”, and remove the permission in your phone's Health settings.

What is never collected

No health data, no weight, no location, no email address and no payment details. The exercise and allergen settings never leave your device, even in a party. Steps and workouts read in the phone app stay on the phone.

If this changes

If accounts or a paid app arrive later, this page will say exactly what is stored on a server and why, before anything is collected.