Saffra

Privacy Policy

Last updated: November 19, 2026

Your data is yours, not ours. This policy explains what Saffra collects, why, who else handles it, how long we keep it, and what you can ask us to do. We do not sell or share your data for advertising, and we do not show ads.

"We" and "Saffra" mean [Company legal name], which runs the Saffra website and app at getsaffra.com. "You" means anyone who visits our site or has an account. Saffra is for businesses in the United States and is not aimed at people in the European Economic Area or the United Kingdom.

Our role. For the invoices, recipes, prices and people's details that a restaurant puts into Saffra, the restaurant is the "business" or "controller" and we are its "service provider" or "processor": we handle that data to provide Saffra, as set out in our Terms of Service. For account, billing and website information about you, we decide how it is used.

What we collect and why

We collect only what we need to run Saffra.

Account. Your email address and, if you sign up with email, a password. We never store your password: we store a one-way hash of it. If you sign in with Google, we receive your email address and your Google account identifier. If you turn on two-step sign-in, we store your authenticator secret (encrypted) and hashed recovery codes. We use this to sign you in, keep your account secure, and contact you about your account.

Your kitchen's information. The business and location names, the time zone, the people you invite (their email address and role), suppliers, ingredients, recipes, menu prices, and the invoices you add: the photos or PDFs, plus the items, quantities, prices and totals read from them. We keep this so Saffra can work and so you can see your costs over time. Invoices can include supplier names, delivery addresses, account numbers and the names of supplier staff, such as a driver or sales representative. We handle that on your behalf. Owners: if you add other people to your kitchen, tell them what Saffra holds about them.

Payments. Payments are handled by Stripe. Your card details go directly to Stripe and never touch our servers. We keep your Stripe customer and subscription identifiers, the subscription status, the number of locations, and the billing period, so we can tell whether your kitchen is active.

Technical data. When you use Saffra, our servers receive your IP address, browser type and the pages or API calls you make. We use this to keep the service running, find errors, prevent abuse, and limit repeated sign-in attempts. We keep server logs for up to [N] days.

Messages to us. If you email us, we keep the conversation so we can help you and remember what we discussed.

Cookies

We use only the cookies Saffra needs to work: mise_session keeps you signed in; mise_oauth and mise_totp are short-lived and used while signing in with Google or confirming a two-step code. They are HttpOnly, Secure and SameSite=Lax. We do not use advertising or analytics cookies or trackers. Because these cookies are needed to provide the service you asked for, we do not show a cookie banner. If we ever add anything else, we will update this policy first.

Who else handles your data

We use a small number of companies to run Saffra. We choose them carefully, but we cannot promise how they run their own systems; their own terms apply to what they do.

CompanyWhat forWhat they receive
DigitalOcean (United States)Hosting our serversAll data stored in Saffra
[Storage provider]Backups of the database and storage of invoice filesCopies of the database and your invoice files
Anthropic (United States)Reading your invoices (turning the photo or PDF into items and prices)The invoice photo or PDF you add, plus our fixed reading instructions
xAI (United States)Reading your invoices, only while we use it in place of AnthropicThe same as Anthropic
StripeTaking payment and managing subscriptionsYour billing email, subscription details and the card and billing details you enter into Stripe
Google"Sign in with Google"Only what is needed to sign you in, if you choose it
[Email provider]Sending account emails such as email confirmation and password resetYour email address and the message

Invoice reading. When you add an invoice, we send the photo or PDF to Anthropic's API (Claude) to read it; if we switch invoice reading to xAI's API, it goes there instead, never to both. We send the file and our reading instructions, not your recipes, menu prices or account details. The company that reads it processes it for us and, under its API terms, [may keep it for up to 30 days to monitor for abuse, and does not train its models on it: to be confirmed against Anthropic's and xAI's current commercial terms]. The reading is automated and you always review the result before it is saved. No decision with legal or similar effect on you is made by software alone.

We do not use your invoices or recipes to train models of our own, and we do not sell or rent your data or share it for advertising. We do not "sell" or "share" personal information as those words are used in California law.

When we look at or share your information

  • To provide the service, through the companies above.
  • We limit who can see your content. Our team looks at it only for support you ask for, to fix an error that stops an automated process, to keep the service secure, or when the law requires.
  • To keep Saffra safe, including investigating abuse or security incidents.
  • When the law requires it. We will share information if we receive a valid legal request, and we will tell you first where we are allowed to.
  • If the business changes hands. If Saffra is acquired or merges, we will tell you before your information is transferred or becomes subject to a different privacy policy.
  • De-identified, aggregated data. We may use data that cannot identify you or your business (for example, how many invoices are processed in total) to improve the service.

How we protect your data

Data is encrypted when it moves between your device and our servers (HTTPS). Passwords are stored only as one-way hashes. Authenticator secrets are encrypted. We make continuous backups, kept for 30 days, so your data survives a server failure. Invoice files are served only through short-lived signed links. No system is perfectly secure. If a security incident affects your data, we will tell the account owner without undue delay. If you find a security problem, please tell us at [Contact email].

How long we keep it, and deleting your data

We keep your information while your account is active. You can delete invoices, recipes and suppliers inside the app. You can also delete your account yourself under More → Delete account. When you do, you are signed out, kitchens where you are the only member are deleted with everything in them, and your login details are removed: your email and name are replaced, and any Google link is cleared. Kitchens that other people still use stay, and you leave them; invoices you added there stay, now credited to "Deleted user". Our backups keep a copy for up to 30 days, then it is gone. If you cannot use the app, email [Contact email] and we will do it for you. Stripe keeps its own billing records for our books. We may keep limited records where the law requires or to resolve a dispute. If an account stays unpaid and unused after its trial, we may delete it after [N] months, and we will email you first.

You can also ask us for a copy of your data at any time at [Contact email].

Your rights

You can ask us to tell you what personal information we hold about you, give you a copy, correct it, or delete it, and you can ask us to stop using it for a purpose you object to. We apply these rights to everyone, including California residents, whether or not the law requires it. We will not treat you differently for using them.

To use any of them, email [Contact email]. We may need to confirm it is you first. If someone acts for you, we will need your written permission. We will reply within 45 days. If we say no, we will explain why and how you can appeal by replying to us.

If you are an employee or supplier contact whose details a restaurant has put into Saffra, please ask that restaurant first; we will help them answer you.

Where your data lives

Saffra is run from the United States and your data is stored there (DigitalOcean's San Francisco region).

Children

Saffra is for businesses and is not meant for anyone under 18. We do not knowingly collect information from children.

Changes and questions

If we make a material change to this policy, we will email the account owner and show a notice in the app before it takes effect, and update the date above. Questions or concerns: [Contact email], [Company legal name], [Mailing address].


This policy is adapted from the 37signals LLC privacy policy at https://github.com/basecamp/policies, licensed under Creative Commons Attribution 4.0 International. We changed it to fit Saffra.