Legal
Last updated July 9, 2026
Family recipes carry stories, and stories carry people. We treat what you share with EverySpice — recipes, photos, memories about honorees who've passed on — with the same care we'd want for our own family's history. This policy explains what we collect, why, who we share it with, and how you stay in control of it.
EverySpice is operated from the United States, and the data described below is processed and stored there. We do not run ads on EverySpice and we do not sell your personal data or your family's recipes to anyone, ever.
Account basics. Your email address (used for magic-link sign-in — we don't store a password), and the profile details you choose to add: handle, display name, avatar, kitchen title, and a short bio.
Phone number — optional. If your family turns on Conversational Legacy Harvesting (letting a relative text a recipe in), we receive the phone number that texts our number and the message content, so we can attach the draft recipe to the right family vault. This feature is off by default and only active where a family has enabled it.
Family recipes and stories. Recipe titles, the story behind them, the original verbatim text (including handwriting quirks and margin notes when you're transcribing a card), the modern cookable version, and any notes about uncertainty in the transcription.
Photos and other media. Recipe card scans, finished-dish photos, honoree portraits, and voice memos you upload — stored as recipe media attached to a recipe or an honoree.
Honorees. When you add the person a recipe comes from — a name, relationship (like “Nana” or “Pop-Pop”), a photo, and an optional remembrance you write about them.
Activity and notifications. Records of family-circle activity that generates a notification for you (a member joining, a recipe request, a request being fulfilled) so we can show you what you've missed.
Payment records. If you subscribe to EverySpice Plus or buy a Hosting Kit, Stripe processes the transaction and we store a reference to your Stripe customer and subscription status. We never see or store your full card number.
To run the service: show your recipes back to you, apply the visibility settings you choose, send notifications, and process payments.
AI recipe transcription and reconstruction. When you ask EverySpice to help turn a recipe card photo, a voice memo, or a loose memory into a structured, cookable recipe, we send that content to Google's Gemini models to do the transcription or reconstruction. This only happens when you initiate it (for example, from the Rescue flow) — we don't run your private content through AI in the background without your action.
We do not use your family's recipes, photos, or stories to train our own models, and we don't sell them to data brokers or advertisers.
We don't sell your data. We do use a small set of infrastructure and service providers (“processors”) to run EverySpice, each bound to process your data only on our instructions:
We may also disclose information if required by law, to protect the rights and safety of our users, or in connection with a merger, acquisition, or sale of assets — in which case we'd tell you first.
Every recipe and every piece of recipe media has a visibility setting you control, one recipe at a time: private (only you can see it — the default), family (visible to the family circle you designate), or public (visible to anyone using EverySpice, after it clears our content review). You can change this at any time.
Photos and scans live in a private storage bucket, not a public one. When you or someone you've shared with needs to view a photo, we generate a short-lived signed URL for that specific request rather than making the file permanently public.
Data is stored with Supabase (Postgres) behind row-level security policies that enforce the visibility rules above at the database level, not just in the app's interface. Traffic to EverySpice is encrypted in transit. Access to production data is limited to the people who need it to operate the service.
We keep your content for as long as your account is active. You can delete individual recipes, photos, or honorees at any time from within EverySpice. To delete your account and the personal data associated with it, email hello@everyspice.com — we'll confirm and complete the deletion, aside from information we're required to retain briefly for backups, fraud prevention, tax records, or other legal obligations.
EverySpice is not directed at children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child has provided us information, contact hello@everyspice.com and we'll delete it.
EverySpice is currently in beta. Our data practices are substantially as described here, but as we add features (including ones already noted above, like Conversational Legacy Harvesting) this policy will be updated to match — check back, or watch for an email when something material changes.
Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. You can exercise most of these directly inside EverySpice (editing your profile, changing recipe visibility, deleting content) or by emailing hello@everyspice.com.
If we make a material change to this policy, we'll notify you by email or with a notice in the app before it takes effect.
Questions about this policy or your data? Reach us at hello@everyspice.com. For terms of use, see our Terms of Service.