Privacy

There are no analytics, no advertising, no tracking cookies and no third-party scripts. Nothing you do here is measured for anyone’s benefit but yours. The one cookie is the one that keeps you signed in.

Photographs on your camera’s memory card are read by your browser and never uploaded. When you import a recipe from a photo, the settings are extracted on your machine and only those few hundred bytes are sent. The only pictures that reach the server are the ones you deliberately attach to a recipe or use as your avatar.

The controller for the purposes of the GDPR is Philip Stapelfeldt, Germany. Questions about your data go to me@ph1p.dev, which is read by a person.

You can read this site without an account. Creating one stores:

Your email address and a password hash

Needed to sign you in and to send a password reset. The password itself is never stored — only a hash of it.

A display name, and optionally a username, avatar, location, bio and links

Whatever you choose to put on your public profile. All of it is optional except the display name, all of it is editable, and anything you leave blank is simply not stored.

Two-factor secrets, if you turn 2FA on

Stored so a code can be verified. Turning 2FA off removes them.

Sessions

One row per browser you are signed in on, with its IP address and user agent at sign-in, so you can recognise and sign out of a device you no longer have.

The legal basis is Art. 6(1)(b) GDPR — performance of a contract. You asked for an account; these are the fields an account is made of.

Recipes, sets, photos, bookmarks and likes are stored against your account. A recipe is private by default: it is visible only to you until you publish it.

Publishing something makes it and your public profile readable by anyone, including people who are not signed in and search engines. Unpublishing it takes it back out of the feed, but cannot recall a copy somebody already made.

Example photos you attach to a recipe, and your avatar, are uploaded and stored on the server. They are re-encoded on arrival, which drops everything embedded in the original file — EXIF data, GPS location, camera serial number. A photo on a published recipe is public like the recipe itself.

The site records which recipes are on which of your cameras, keyed by a fingerprint of the body, so it can tell you what you have already written to a slot. That fingerprint identifies a camera, not a person.

Connecting a camera is a permission your browser grants to this site through WebUSB. It is granted per device, it can be revoked in your browser’s settings, and it does not require an account.

Photographs on the card are read directly by your browser. They are not uploaded, not stored on the server and not seen by us. When you import a recipe from a photograph, the film-simulation settings are read out of the file on your own machine and only those settings are sent.

One cookie, set when you sign in, holding your session. It is necessary for the site to work — you cannot be signed in without it — so it needs no consent banner under §25(2) TDDDG. There is nothing to opt out of, because nothing else is set.

Your theme preference is stored in your browser’s local storage, on your machine, and is never sent to the server.

The server and its hosting provider record requests — IP address, time, the page requested, the browser’s user agent — for the short period needed to keep the service running and to deal with abuse. The legal basis is Art. 6(1)(f) GDPR, our legitimate interest in an operating website. These logs are not used to build a profile of you and are not combined with your account.

• Hosting. The site and its database run on infrastructure operated by a hosting provider, who processes data on our instructions under Art. 28 GDPR.
• Email. Password-reset messages are sent through an SMTP provider. It sees your email address and the message. If no mail server is configured, the site does not offer resets at all.

Nothing is sold, and nothing is shared with anyone for advertising — there is no advertising.

Account data is kept while the account exists. Deleting your account deletes your recipes, sets, bookmarks, likes and profile with it — the database cascades from your user row, so this is a real delete and not a flag.

One thing survives on purpose: if somebody remixed a recipe of yours, their copy is theirs and stays. It simply forgets where it came from.

Under the GDPR you may ask for access to your data (Art. 15), correction (Art. 16), deletion (Art. 17), restriction (Art. 18), a portable copy (Art. 20), and you may object to processing based on legitimate interest (Art. 21). Most of these you can exercise yourself: your profile is editable, your account is deletable, and under Settings → Account → Download your data you get a ZIP of everything stored about you — profile, sign-ins, recipes, sets, photos, bookmarks and likes, as JSON plus the image files. Only the keys to the account are left out: the password hash, session tokens and two-factor secrets.

For anything else, write to me@ph1p.dev. You also have the right to complain to a data protection supervisory authority in the country where you live or work.

If this policy changes, the date at the top changes with it. Material changes to how your data is used will be told to you rather than left for you to find.