Saucery

Legal

Privacy Policy

This policy explains what Saucery collects, where it is processed, how long we keep it, and how you can ask us to delete it.

Last updated: 5 June 2026

Data Controller

The data controller for Saucery is Trystan Morganschauer, trading as Saucery. For privacy requests, contact [email protected].

You also have the right to lodge a complaint with a supervisory authority. Because the controller is UK-based, the relevant supervisory authority is the UK Information Commissioner's Office (ICO).

What We Collect

Saucery collects the account email you use to sign in, the repository content you create or join, BYOK provider keys when you choose to add them, and recipe interactions such as saves, edits, imports, cook sessions, sharing, and sync activity.

We also keep basic operational records needed to protect accounts, debug sync, and understand whether product features are working as intended.

Where Data Goes

Recipe and account data is stored in Postgres on Railway. Error context may be sent to Sentry so we can diagnose crashes and reliability issues.

When you use AI features, relevant prompts, recipe text, or automation context may be sent to OpenAI for LLM operations. Anthropic may process task, spec, or review automation context used to build and operate Saucery. BYOK keys are used only for the provider operations you configure.

Retention

We keep account, repository, and recipe records while your account is active so sync, sharing, history, and collaboration continue to work. Operational logs and error reports are retained only as long as needed for security, support, and reliability.

If you leave a shared repository, content that belongs to that repository may remain available to other members according to their permissions.

Cookies & Local Storage

Saucery uses first-party cookies that are strictly necessary for authentication: an HttpOnly refresh-token cookie issued by the backend, a short-lived access-token cookie, and a session marker cookie used by the web auth proxy and middleware. These support sign-in, session refresh, and protected-route access, so no consent banner is required for them.

The web app uses localStorage for your theme preference and client-side product caches, including offline sync diagnostics, recipe display preferences, active account/repository state, and UI choices such as pinned or collapsed controls.

Saucery does not set third-party advertising, analytics, or tracking cookies.

Deletion Requests

To request deletion of your account or personal data, email [email protected]. Once L5.1 ships, Saucery will also support an in-app DELETE /account flow for account deletion.