Privacy policy

Your account. Email address, and your name if you give one. Handled by Clerk, who manage sign-in for us. We never see or store your password.

What you capture. The link, text or screenshot you give us, and the recipe we make from it — title, ingredients, method, notes, and any image. Images from a source page are copied into our own storage so the recipe does not break when the original moves.

How much you use it. A count of captures per account for the current calendar month, to enforce the monthly allowance. Not what you captured — just how many.

Marketing consent. Whether you have opted in, and when you last changed it.

Whether a capture worked. A count of how far each attempt got, holding nothing that can be tied to you. See section 6.

Signed-out visitors. See section 5 — no account, but not nothing.

To provide the service you asked for: keeping your recipes, reading new ones, making PDFs, and taking payment. To enforce the monthly allowance and stop abuse of an endpoint that costs us money on every request. To send newsletters and offers only if you opted in — you can withdraw that at any time in Account settings, and everything else keeps working.

We do not sell your data or share it for advertising. We use these providers to run the service:

These providers are in the United States, so your data is processed there.

Polar knows the email address and billing details you gave it at checkout, and tells us only which account bought what. We do not send them your recipes.

When you paste text, a link to a video, or a screenshot, that content is sent to an AI provider — currently NVIDIA, with Anthropic as a fallback — which returns the structured recipe. This is the only way the feature works, and it applies to the whole of what you send, including anything incidental caught in a screenshot.

So: please do not paste anything you would not want processed by a third party. Crop screenshots to the recipe.

Links to sites that publish structured recipe data are handled entirely by us and are never sent to an AI provider.

Signed-out visitors get two free extractions. To count them without knowing who you are, we set a cookie holding a random token, and store a salted hash of your IP address — the address itself is never written down, and the hash cannot be turned back into it. We also keep a single daily total across everyone, which identifies nobody.

A recipe you capture before signing up is held for 24 hours so it can be added to your account if you make one. If you do not, it is deleted.

We keep a count of how far each capture gets — that one started, that a recipe came out of it, that it was saved, or that it failed — so we can tell how often the thing this app exists to do actually works.

Those rows cannot be tied to you. They hold no account, no cookie, no IP address, and nothing you pasted or captured — not the text, not the link, not the title. Each capture gets a random number so its own steps can be counted as one attempt, and that number is never written anywhere else and means nothing once the request has finished. What is recorded beyond it is whether the visitor was signed in, and whether they submitted text, a link or a photograph.

It is stored in our own database. There is no analytics company involved and nothing about your use of Spatterbook is sent anywhere else.

No advertising or analytics cookies — the counting described above uses no cookie at all. Three functional ones, all server-set and not readable by scripts:

Recipes and account data: until you delete them, or delete your account.

Unclaimed captures: 24 hours, then removed automatically.

Free-use counters: the per-visitor count for up to 30 days; the per-network and site-wide counts reset daily. All are cleared automatically.

Capture counts (section 6): one year, then deleted automatically. They identify nobody, but a number nobody is going to look at again is not worth keeping either.

You can see everything we hold about you in the app itself — it is your recipes. You can correct or delete any of them, and you can delete your account entirely from Account settings. That removes your recipes, images, cookbook settings and sign-in immediately and permanently — there is no backup we can restore from.

You can download everything we hold as a single JSON file from Account settings, without asking us: your recipes, your cookbook settings and your purchases. Photographs are linked rather than included, and those links stop working once the account is deleted — so save any pictures you want to keep first.

You can withdraw marketing consent at any time, or ask us to correct something, by writing to privacy@spatterbook.com.

Depending on where you live you may also have the right to object to processing, to restrict it, or to complain to your data protection regulator.

Spatterbook is not intended for children, and we do not knowingly collect data from them. If a child has given us data, write to us and we will remove it.

If we change how we use your data in a way that matters, we will say so here and update the date at the top before it takes effect.