Privacy

Roux is a personal cooking app. Your recipes, menus, ratios, and notes stay attached to your account. Nobody else sees them unless you share a link, or the person who runs Roux looks at your account to fix a problem (more on both below). We don't sell your data, and we only pass it to the services named on this page, to run Roux. You can delete your account and everything in it, from inside the app or by emailing us.

• Anyone with a share link: when you share a recipe, menu, notebook, or group of ratios, anyone with the link can see it, along with your display name, or "a Roux cook" if you haven't set one. Your email address is never shown. People can also save a copy to their own Roux, and that copy stays theirs even if you later delete yours. A link keeps working until you stop sharing it or delete what you shared, or until we take it down after someone reports it. A recipe in a menu you've shared can also be seen through that menu's link. Shared pages ask search engines not to list them.
• Support access: to look into a problem, usually one you've reported, the person who runs Roux can sign in as your account and see the app just as you do, including everything you've saved. They can also view or download a copy of your account's data, and keep short private notes or labels on your account to help with support (these go when your account does). We only do this to fix problems. Roux doesn't yet keep a record of when any of this happens.

• Account: your email address (we email you a code to sign in) and an optional display name.
• Content you save: recipes, menus, ratios, notebooks, notes, and any photos you upload to those.
• Preferences: theme, units, pantry-staple list, bookmarks. Stored to make the app feel like yours across devices.
• Recipe imports: when you import a recipe from a web page, we note the page address and whether the import worked, so we can improve the importer.
• Messages to us: when you send something from Help & Support, we keep your message, your account if you're signed in, any screenshot you attach, and some technical details: app version, browser, screen size, time zone, the page you were on, and the app's last few errors. You can read the technical details before you send.
• Reports: if you report something someone shared, we keep your reason, any note you add, the IP address you sent it from, and your account if you're signed in.
• Usage events: sign-in timestamps and basic error logs (which page, which error). No analytics tracker, no ad pixels, no third-party cookies.

• Account + content: Supabase (database + file storage), hosted in the EU. Screenshots you send us are stored privately, where only we can open them.
• Sign-in emails: Roux's email-sending service sees your address only long enough to deliver your code.
• Messages to us: a copy of each message, with its technical details and your email address, is emailed to us through Resend.
• Recipe imports: our server fetches the page for you. If the site blocks that, we ask the Internet Archive (web.archive.org) for its saved copy of the page instead. Either way, they see the page address, not who you are.
• Reading a recipe from a photo: this happens on your device, and the photo isn't sent anywhere. To do it, your browser downloads the scanning files from jsDelivr (for printed text) or Hugging Face (for handwriting), usually just the first time. Like any website, they see your IP address, but not your photo.
• Rate limits: Upstash counts requests by IP address, or by account for some actions, so nobody can flood Roux. Those counts delete themselves within about two hours.
• Error reports: Sentry, used to triage crashes. Includes a stack trace and the URL you were on when it happened. Strips request bodies by default.
• Hosting: Vercel. Standard server logs (IP address, page requested, response code) are kept for a short time for abuse prevention and debugging.

In Roux, open your profile, tap Edit next to your name, then Schedule deletion. You're signed out straight away, and we wait 30 days in case you change your mind: sign back in any time before then and you can cancel. Until then, anything you've shared stays visible to people with the link. After 30 days we permanently delete:

• Your account and the email address tied to it.
• Every recipe, menu, ratio, notebook, and note you've saved, and the photos in them. A photo stays where someone saved their own copy of something you shared.
• Your messages to us and their screenshots, reports you've sent, and your recipe import history.

A few things aren't tied to your account, so they stay: messages and reports sent while signed out, and the emailed copies of your messages in our inbox (ask and we'll delete those too). Photos you removed from an item, or replaced with another, can also be left behind until we clear them. Ask and we'll do that straight away. Sentry error events are kept for up to 90 days and contain no recipe content, only technical details about the error.

Using Roux without an email? That's a guest account. If a guest account hasn't been used for 3 months, we delete it automatically, with everything in it. Adding an email to your account stops that. The steps above also need an email, so add one first, or email contact@heyroux.com and we'll delete your account for you.

If you want it gone sooner, or the in-app steps don't work for you, email contact@heyroux.com and we'll delete it for you without the 30-day wait.

• Auth cookies: set by Supabase to keep you signed in. Required for the app to work.
• Browser storage: we cache your library locally (IndexedDB) so the app works offline. Cleared when you sign out or delete your account.
• No tracking, advertising, or analytics cookies.

If you're in the EU, UK, or California: you have the right to access, correct, or export your data, and to ask us to delete it. You can export your library from your profile, under Export. Deletion is the flow above. For anything else, email contact@heyroux.com.

We'll update this page when what we collect changes. The "last updated" date at the top is the source of truth. For material changes (new processor, new data category) we'll surface a notice in the app before the change takes effect.