What RecipeMirror holds, and what it refuses to.

Who is responsible

Rivoryn Ltd (CRO 815118) operates RecipeMirror and is the data controller for personal information collected through this website and the web app. We are based in Ireland and comply with the GDPR and the Irish Data Protection Acts 2018 — the same arrangement as DrySpell. For anything about your data, write to privacy@recipemirror.com. Product questions go through the contact form. A registered office will be added here when it is published, rather than invented on this page.

What is held

The sources you bring in, the guides built from them, what you have said you have in your kitchen, your cooking history and any corrections you make. Your display name and email, if you have signed in. Messages you send through a form, so somebody can reply.

What is not held

RecipeMirror does not store the videos it reads from public links. It reads them where they live and links back. It does not build an advertising profile, does not sell lists, and does not use your cooking to train a public model.

Recordings of other people

A recording of a family member is consented for private analysis only. It is never published, never shared with other users, and never used to train anything. The share control does not appear at all on a guide built from one.

What stays on your device

Your theme, your mise-en-place ticks, your kitchen equipment list, demo mode, and your cookie choice. Those describe a device and a room rather than an account, and a cook using the app at someone else’s house should not have their own pans follow them there. See the cookie policy for the exact keys.

Why we hold it (legal bases)

• Contract / steps you asked for. Creating a guide, scaling a recipe, naming foods in a photo, signing in, exporting or deleting your account.
• Consent. Analytics events (only after you accept), a family recording (the in-app gate), and the native-app waitlist (one email when there is something to install).
• Legitimate interests. Reading a contact message so we can reply, keeping the service secure, and diagnosing a failure you reported. You can object; we will stop unless we have a compelling reason to continue.

Who else sees anything

Processors act on our instructions. They are not given a kitchen or a dish unless that is the job you asked us to do.

• Hosting. The website is served from our host (Vercel when deployed). They see ordinary web logs.
• Accounts and dishes. Supabase, when you sign in — guides, cooks and profile data for your account.
• Email. Resend delivers a contact-form or waitlist message to us. The inboxes themselves are privacy@recipemirror.com and hello@recipemirror.com, hosted on Zoho Mail. No auto-reply. Zoho and Resend see the address and the text so they can hold or deliver it.
• Analytics. PostHog on EU hosting, and only if you allowed analytics. Named actions and a path. Never a recipe, transcript, email or message body.
• Reading a source. An AI provider, through our own API, when you ask us to analyse something. What is sent is the source and the prompt — not your name or email. The provider in use is named in the product where a source is analysed.

How long

Account data until you delete the account. Contact messages until we have replied and no longer need the thread. Waitlist addresses until you ask us to remove them or we send the one email and close the list. Analytics events according to PostHog’s retention on our project, and they stop when you withdraw consent. Device storage until you clear the site data.

Your rights

You can ask to access, correct, delete or export what we hold; restrict or object to processing; and withdraw consent (analytics, waitlist, a recording) without affecting anything that happened before you withdrew. Kitchen Profile already has an export and a delete that genuinely deletes rather than hiding. For anything else, email privacy@recipemirror.com. You can also complain to the Data Protection Commission in Ireland (dataprotection.ie), or your local supervisory authority if you live elsewhere in the EEA.

Children

The product is not directed at children under 13. If you believe we have collected data from a child, email privacy@recipemirror.com and we will delete it.

Cookies

Analytics do not run until you opt in. Details, including how to change your mind, are on the cookie policy.