Privacy

Generation Recipes keeps your family's recipes. This explains exactly what that means for your information — what is collected, who else ever sees it, and how to get it back or have it removed.

It is written to be read rather than to be defensible. Where something might surprise you, it is said plainly instead of being placed where you would not look.

Who we are

Generation Recipes is operated by Life Ascension LLC, a limited liability company registered in Idaho. Generation Recipes is a trading name of that company.

What we collect

What you give us

Your name and email address, and a password we store only as a hash — we cannot read it and cannot tell you what it is. If you sign in with Google instead, we store the account identifier Google gives us and the URL of your profile picture. We never receive your Google password.

What you put in

Your recipes: titles, ingredients, instructions, notes, timings and any links you paste. And your photographs — which for this service usually means handwriting, and sometimes whatever else happened to be on the table.

What is collected automatically

When you are signed in, we store the IP address and browser identification string of your session, because that is how the sign-in itself works. When anyone looks at our front page we record that a visit happened, where it came from, and nothing else — no cookie, no identifier, nothing that could later be tied to a person. That page carries no analytics or advertising scripts of any kind.

We do the same when a shared recipe link is opened, and it holds even less: that an opening happened, and the page it was followed from if there was one. We do not record which recipe was opened, whose it was, or anything about whoever opened it. It is a count of openings, not of people — we cannot tell one reader from another, or a stranger from the person who made the link. It exists so we can tell whether sharing works at all, and it is the only thing on a shared page that is recorded.

Your photographs are read by another company

This is the part worth knowing, so it is not buried further down.

When you ask us to read a recipe card, the photograph is sent to Anthropic, whose software transcribes the handwriting and returns the text. We keep a copy of what it returned alongside your recipe. Photographs are sent only when you ask for a card to be read — uploading a photo without asking for it to be read never sends it anywhere.

If you would rather no photograph ever left our systems, type the recipe in yourself. Everything else works the same.

Who else processes your information

• Laravel Cloud — runs the service and hosts the database.
• Object storage — holds your photograph files.
• Anthropic — reads recipe cards, as described above.
• Resend — sends email: sign-in confirmations, password resets, and the link to a data export.
• Stripe — takes payment, if you subscribe. Described in full below.
• Google — only if you choose to sign in with it.

We do not sell your information, share it with advertisers, or use it to build a profile of you. There is no advertising on this service and no plan to introduce any.

If you subscribe

Payment is handled by Stripe. Your card details are given directly to them and are never sent to us: we do not see, store or process a card number at any point, and we could not produce one if you asked.

We give Stripe your name and email address so they can identify the payment as yours and send you a receipt. Stripe gives us back an identifier for you as their customer; the state of your subscription — which plan, and whether it is active, or when it ended if it has; and, once you have a card on file, its type and last four digits — the way "Visa ending 4242" appears on a receipt, never enough to be a card number. We do not keep a record of exactly when your subscription next renews; only Stripe does. That is the whole of what we keep about your payments.

Stripe also collects information of its own when you pay, including your card details and billing address, under their own privacy policy. If you never start checking out — never so much as click subscribe — nothing of yours is ever sent to them; clicking it opens a Stripe customer record in your name even if you back out before paying.

Who can see your recipes

Your recipes are private to you. Three things change that, and each one is your choice:

• Recipes you share with a household are visible to every member of it. Your private notes on a recipe are visible to them too.
• A recipe you share by link can be read by anyone holding that link, without an account. Your notes are never shown on a shared page. You can revoke a link at any time, and the old link stops working.
• If you leave a household, it keeps a copy of the recipes you had shared with it, credited to you by name. You keep yours.

How long we keep things

While your account exists, we keep your recipes — that is the entire point of the service.

A recipe you delete is kept for thirty days and then destroyed. It disappears from your box immediately and from every screen, and during those thirty days we can still put it back if you ask us to — deleting the wrong card should be a recoverable mistake. After that it is gone from our systems along with its photographs, and we cannot restore it. If you would rather it went sooner, tell us.

A data export you request is stored until you request another, which replaces it, and its download link expires after seven days.

The subscription state described above is kept for as long as your account exists. Closing your account cancels the subscription and removes our copy of it. Stripe keeps its own record of transactions it has processed, for as long as its own obligations require — that is not ours to delete, and a payment that actually happened is a thing both of us are required to be able to account for.

Your rights over your information

These apply to everyone who uses the service, wherever you live. We have not tried to work out which of them we are legally obliged to offer you; it was easier to offer all of them to everybody.

• Get a copy. Ask for an export from your profile page. You get a file containing your recipes, your photographs at full resolution, and a page that opens in any browser — no account, no software, no us.
• Correct it. Edit anything, at any time.
• Delete it. Delete individual recipes yourself; ask us to close your account entirely.
• Take it elsewhere. The export includes a machine-readable file of everything, intended to be usable by something that is not us.
• Ask what we hold. Write to us and we will tell you.

Security

Traffic is encrypted in transit. Passwords are hashed. Photograph files are private and served only to people entitled to see them — never by a public URL you could guess. Photographs are stripped of embedded metadata when uploaded, including the GPS coordinates phones record, so a shared photo does not reveal where it was taken.

No service is perfectly secure, and this one is operated by a very small team. If you find a problem, please tell us rather than anyone else first.

Children

This service is not intended for children under 13, and we do not knowingly collect their information.

Changes

If this policy changes in a way that matters, we will say so on this page and update the date at the top. We will not quietly broaden what we do with your information and rely on you not re-reading.

Contact

Write to carlee@generationrecipes.com about anything here, including deletion requests.