Privacy · Last updated November 15, 2026

Your data, handled honestly.

What we collect, why we keep it, how long, and how to make it leave. No dark patterns, no hidden clauses.

The changes about analytics and ad measurement outside the EU, EEA, UK, Switzerland and Quebec take effect on 16 November 2026; until then everyone is asked first.

This Privacy Policy explains what information Mise collects when you use the Mise website and application (misebook.io), why we collect it, how long we keep it, who we share it with, and the choices you have.

Mise is operated by GAT (trading as “Mise”), a sole proprietorship (eenmanszaak) registered with the Dutch Chamber of Commerce (KvK) under number 84170891. GAT is the data controller for your personal data. Because we are established in the EU, the General Data Protection Regulation (GDPR) governs all of our processing, wherever you are located. If you are a California resident, the CCPA/CPRA rights below also apply.

Controller: GAT (eenmanszaak) · KvK: 84170891
Privacy contact: legal@misebook.io — a real person replies.

If anything below is unclear, write to us at legal@misebook.io — a real person replies. For California-specific rights see California residents below; for children’s privacy, see Children’s privacy.


What we collect

Everything we actually collect.

1. Account information

When you create an account or place an order we store your name, email address, country, and optionally a profile photo. We also store your membership tier (BASIC or PRO) and whether you have completed onboarding. If you sign in with Google, Google shares your name, email address and profile photo with us; we never see your Google password.

2. Billing and Stripe data

When you subscribe or place an order, Stripe processes your payment. We never see or store your full card number. We do receive and store from Stripe: your Stripe customer ID, subscription ID, card brand (e.g. Visa), card last four digits, and next billing date. These are stored solely to manage your subscription and display billing status in your account settings.

3. Recipe and book content

The recipes (title, ingredients, instructions, cooking times, servings, source URL), photos, and notes you add are stored so we can show them in the 3D preview and bind them into a printed book. We also store the raw HTML or OCR text you submit through the AI parser, for debugging and re-processing. Book content includes your cover images (front and back), dedication text and photo, cover author name, and any back-cover text you write. Nothing you write or upload is used to train AI models — see AI processing below.

4. Order and shipping information

When you place a print order we collect your full shipping address, phone number, and print specifications (cover type, paper quality, page count, quantity, add-ons). See Data retention below for how long order data is retained.

5. Technical and device data

When you visit or use the Service, we automatically collect: your IP address (used to determine your country at signup via a third-party geolocation service and to flag internal traffic), your device type (mobile, tablet, or desktop), and your browser user-agent string. We retain the full user-agent string for bot detection and future browser-compatibility analysis.

6. Marketing attribution and UTM data

To understand how users find Mise, we capture and store the UTM parameters (source, medium, campaign, content, term) present in the URL when you first land on our site, together with the referring domain, landing page URL, and raw referrer URL. This first-touch attribution is stored to your profile at signup. We also record last-touch UTM values at the moment you create a checkout session.

7. Advertising click identifiers

If you arrive from a paid-advertising link, your URL may contain ad-platform click identifiers. We capture and store the following when present: gclid / gbraid / wbraid (Google Ads), fbclid (Meta / Facebook), ttclid (TikTok Ads), msclkid (Microsoft Advertising), li_fat_id (LinkedIn), twclid (Twitter / X), rdt_cid (Reddit), and epik (Pinterest). These identifiers are used for advertising attribution and marketing ROI analysis. They are not sold to third parties.

8. Behavioral and usage analytics

We use PostHog to record how you interact with the Service. In the Mise app this happens only with your consent in the regions where we ask for it, and elsewhere unless you turn it off (see Cookies & local storage below). On our public content pages — the guides, template, comparison and “cookbook for” pages — we measure which pages are read and which lead to a sign-up WITHOUT storing anything on your device: no cookies and no persistent identifier, so there is nothing to consent to under the cookie rules, and the basis is our legitimate interest in knowing whether our own writing is read. Those page measurements are not linked to you across visits. Events we track include: page views, recipe creation, AI-feature use, editor session duration, template changes, checkout steps, and interaction with the 3D preview. After you log in, PostHog events are linked to your account (they are pseudonymous before login and identified afterwards). We also maintain internal lifecycle timestamps — first login, first recipe created, first book ordered, last active time — to understand product engagement and support our business planning. The Service sends a periodic heartbeat to refresh your "last active" timestamp while the app is open in your browser. Where analytics is on, PostHog may also record a replay of how you use the app (clicks, scrolling and page changes), with what you type into fields hidden, as well as your email address and address suggestions; replays are kept for 30 days, and you can turn this off under Your privacy choices.

9. Email engagement data

Our email provider (Resend) tracks whether you open transactional emails we send and whether you click links within them (including which link you clicked). This data is stored in our database to measure email deliverability and to improve our communications. Transactional emails include welcome, order confirmation, shipping notification, and subscription emails.

10. AI usage logs

Each time you use an AI feature (recipe parsing, OCR, or image generation) we log: the feature type, the AI model used, input and output token counts, an estimated cost, and a timestamp. These logs are used to enforce usage limits per tier and to manage our AI API costs. They are not shared externally.

11. Support communications

If you submit a support ticket we store the subject and description you write, any screenshots you attach, and the conversation thread with our team. If you cancel Mise PRO, the reason you choose and any comment you add on the cancellation page are stored the same way, as a ticket, so we can read them and reply. Support tickets are hard-deleted when your account is deleted.

12. Newsletter (only if you subscribe)

If you sign up for Notes from the studio, we store your email address, the page you signed up on, the sentence you agreed to, and when you asked and when you confirmed. Nothing is sent until you press Confirm in the email we send you, so nobody can sign up an address that is not theirs. Every issue has a one-click unsubscribe link, and unsubscribing deletes your address from the list. A request you never confirm is deleted after 30 days, and deleting your Mise account deletes the subscription too. The legal basis is your consent. Emails are sent through Resend.

13. Waiting list (only if you join)

If you join the waiting list for a country we do not deliver to yet, we store your email address, the page you joined from, your country (looked up from your IP address through ipinfo.io; the IP address itself is not kept) and your browser’s user-agent string. We send one email to confirm, and we will write once more, the day we deliver to your country. Reply to any of these emails and we delete your address. Emails are sent through Resend.

14. Pre-account session tracking

Only while analytics is on (see Cookies & local storage below), a random distinct_id is stored in your browser’s localStorage (not a cookie), together with the link or ad that brought you (kept 30 days). This lets us attribute pre-signup page views and marketing data to an eventual account. At signup, the anonymous session is linked to your profile. If you say no, nothing is stored; if you turn analytics off later, these values are deleted. Clearing your browser storage also removes them.

How we use it

Why we process your data.

AI processing

The parser, explained.

We use the Google Gemini API to parse recipe text, process images (OCR), and generate recipe photos. When you use these features, the text or image you submit is sent to Google's servers for processing. Two things to know:

Our processors

Who else touches your data.

We share the minimum required with each partner. Nothing is sold for profit.

ProcessorPurposeRegion
Netcup Hosts the servers that run misebook.io; every request to the site passes through them. EU (Germany)
Supabase Hosts our database (your account, recipes, books, orders) and file storage (uploaded images) on cloud infrastructure. EU (Germany)
Stripe Processes subscription payments and one-off print orders. Stores your payment method. US
Google Gemini Receives recipe text, images, and URLs you submit for AI parsing or image generation. US
Google (sign-in) If you choose “Continue with Google”: confirms who you are and shares your name, email address and profile photo with us. US
Google Maps Platform Suggests addresses while you type your shipping address; what you type is sent to Google. US
Google Ads In the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec, only if you accept; elsewhere, unless you turn it off: measures whether an ad click led to a sign-up or an order. Not used for remarketing. US
Reddit Ads In the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec, only if you accept; elsewhere, unless you turn it off: measures whether an ad click led to a sign-up, a new book or an order. With each event it receives Reddit’s click id, its own browser identifier and your browser’s details (as any request does, including its IP address), and for an order its id and amount; never your name or email address. Not used for remarketing. US
RPI (print partner) Receives your name, shipping address, phone number, and book PDF to manufacture and ship your printed book. US
Cloudflare Stores the generated print-ready PDFs (R2) before they are sent to RPI, and runs Turnstile, the check on sign-in and sign-up that tells people from automated scripts (it receives your IP address and browser signals). US
PostHog Collects pseudonymous / identified product analytics. Inside the app: opt-in in the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec, on unless you turn it off elsewhere; on the public content pages, storage-free page counts under legitimate interests. Hosted in the EU. EU
Resend Sends transactional emails, reminders about a book you saved, and the newsletter if you subscribe; tracks open and click events. US
ipinfo.io Receives your IP address at signup, and when you join the waiting list, to determine your country. US

International transfers. Several processors above are located in the United States (Stripe, Google, Reddit, Resend, Cloudflare, RPI, ipinfo.io). Where we transfer personal data outside the European Economic Area, we rely on the EU Standard Contractual Clauses and/or the processor’s EU–US Data Privacy Framework certification, as applicable. You can request details of the safeguards for any transfer at legal@misebook.io.

No advertising lists. We do not upload customer lists or email addresses to advertising platforms, and we do not sell your personal information.

Data retention

How long we keep it.

Account deletion (Studio → Settings → Your data → Delete account) hard-deletes your recipes, books, photos, PDFs, and support tickets. PII on your profile is cleared, and your Stripe customer profile and any saved payment methods are deleted at Stripe, which also ends any subscription. However, order records are retained for 7 years because they are required for tax and accounting compliance and as evidence in the event of a Stripe chargeback. This is a legal obligation we cannot waive on request. Records of the payments and refunds themselves stay with Stripe, which keeps them under its own legal obligations. Backups. For disaster recovery we keep a nightly backup of our database and a copy of uploaded photo originals for 14 days, on our own server. If you delete your account, your data leaves the live service immediately and drops out of these backups as they expire, within about two weeks. The table below details retention for each data category.

DataRetentionBasis
Account profile (PII fields) Active account duration. On deletion: PII fields (name, email, avatar) are immediately cleared; non-PII fields (tier, acquisition data, timestamps) are retained for pseudonymous cohort analytics. GDPR Art. 17(3)(b) carve-out for analytics / legal obligation
Recipes, books, and uploaded photos Deleted immediately when you delete an individual recipe or book, or when you delete your account. User request
Orders (full record including shipping address) 7 years from order date, even after account deletion. EU VAT/tax retention obligation; Stripe chargeback evidence (180 days)
Stripe customer profile and saved payment methods Deleted at Stripe when you delete your account; any subscription ends with it. User request
Payment and refund records (held by Stripe) Retained after account deletion, for as long as Stripe's own legal obligations require. Tax and accounting compliance; chargeback evidence; Stripe's regulatory obligations
Email send logs Retained; recipient address anonymised on account deletion. Deliverability analytics, anonymised
Email engagement events Retained in anonymised form. Deliverability analytics
Behavioral analytics (PostHog) Kept for up to 1 year (our PostHog retention setting); deleted from PostHog, with its events, when you delete your account. Daily totals in our own database are kept, with nothing that identifies you. Product analytics
Attribution / session data Retained; fingerprintable fields (raw UA, raw referrer, distinct_id) cleared on account deletion. Cohort analytics, pseudonymous
AI usage logs Retained indefinitely (pseudonymous). AI cost management and tier enforcement
Support tickets and messages Deleted immediately on account deletion. No legal retention obligation
Newsletter subscription Until you unsubscribe (the address is then deleted). An unconfirmed request is deleted after 30 days; deleting your account deletes it too. Consent
Waiting list for your country Your email and country, until we write to say we deliver there, or until you ask us to delete it. Consent
Print-ready PDFs (Cloudflare R2) Deleted on account deletion (recipes are also deleted). User content
Backups (database and uploaded photo originals) Nightly copies kept for 14 days on our own server, then deleted automatically. If you delete your account, your data leaves the live service immediately and drops out of the backups as they expire, within about two weeks. Disaster recovery

Your rights

Yours to exercise.

Under the GDPR you have the following rights over your personal data. We respond to verifiable requests within one month (or tell you if we need more time). Exercising a right is free.

Right to complain. If you believe we have mishandled your data, you have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or with the data-protection authority in your own EU country. We’d appreciate the chance to resolve it first — legal@misebook.io.

Security

How we protect your data.

We implement reasonable technical and organisational security measures appropriate to the risk:

No method of transmission over the internet or electronic storage is completely secure. While we strive to protect your personal information, we cannot guarantee its absolute security.

Data breaches

What happens if something goes wrong.

In the event of a personal-data breach that is likely to result in a risk to your rights, we will notify the Dutch supervisory authority (the Autoriteit Persoonsgegevens) within 72 hours of becoming aware of it, as required by GDPR Art. 33. Where the breach is likely to result in a high risk to you, we will also inform affected users without undue delay (GDPR Art. 34) — describing the nature of the breach, the data affected, and the steps we are taking.

California residents

Your CCPA / CPRA rights.

If you are a California resident, the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA) give you additional rights over your personal information.

Categories of personal information collected

In the past 12 months we have collected: identifiers (name, email, IP address, device IDs, cookie identifiers); commercial information (order history, subscription status); internet or other electronic network activity (browsing behavior on our site, analytics events, email engagement); geolocation data (country derived from IP); and inferences drawn from the above to create a profile about you.

Sale and sharing

We do not sell your personal information. Google Ads and Reddit Ads measure whether an ad click led to a sign-up, a new book or an order; California law may treat that as “sharing”, and outside the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec it is on by default. You can opt out at any time under Your privacy choices at the bottom of our pages, or in Studio → Settings → Your data. We upload no customer lists to advertising platforms, and the measurement is not used for remarketing. We honor the Global Privacy Control signal: if your browser sends it, no tracking data is written or sent.

Your CCPA rights

Do Not Sell or Share My Personal Information

To opt out, open Your privacy choices at the bottom of our pages (or in Studio → Settings → Your data) and press Turn off; a browser that sends Global Privacy Control is opted out already. If you would like your choice confirmed for your account, email legal@misebook.io and we will reply within 15 business days.

The processors listed above (Stripe, Resend, Supabase, Google, our print partner and the rest) act on our instructions to provide the Service; that is not a sale or a share. In the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec, PostHog analytics and the Google Ads and Reddit Ads measurement are off unless you accept them; elsewhere they are on unless you turn them off. Either way, you can change it under Your privacy choices.

To submit a verifiable consumer request under the CCPA, write to legal@misebook.io. We will verify your identity using the email address on your account. You may designate an authorised agent to make a request on your behalf.

Children's privacy

No data from children.

The Service is not directed to children. Under the GDPR, the age of digital consent in the Netherlands is 16 — we do not knowingly collect personal data from anyone under 16 without the consent of a parent or guardian. For users to whom US law applies, the equivalent COPPA threshold is 13.

If you are under the applicable age, a parent or legal guardian must have agreed to these Terms and this Privacy Policy on your behalf before you use the Service.

If we learn that we have inadvertently collected data from a child below the applicable age without the required consent, we will delete it as quickly as possible. If you believe we have done so, please notify us at legal@misebook.io.

Browser extension

The Mise Recipe Saver Chrome extension.

Mise publishes a free Chrome extension that detects schema.org/Recipe structured data on food blogs and lets you save the recipe to your Mise Recipe Box in one click. This section describes the data flows specific to the extension. Everything in the rest of this Privacy Policy still applies — the extension is a thin client over the same Mise account you use on misebook.io.

What the extension reads from third-party sites

When you visit a webpage, a small content script reads only the page's structured Recipe data — the same machine-readable JSON sites publish for Google's rich-results indexing. The extension never inspects, transmits, or stores any other part of the page. If no Recipe data is present, the extension does nothing.

When data leaves your browser

The extension transmits data to Mise's servers in exactly two cases, both initiated by you:

What the extension stores locally

Your Mise account session token (received from misebook.io's session bridge) is stored in chrome.storage.local, encrypted at rest by Chrome and isolated from other extensions. A short-lived per-tab cache of detected recipes is held in chrome.storage.session (cleared when you close the browser). Both stores are local to your device.

What the extension never does

Permissions explained

Host permission for all URLs — required to detect <script type="application/ld+json"> tags on third-party food blogs. The content script reads only this structured data; page content is never transmitted to Mise unless you click Save.

storage — persists your Mise session token and per-tab recipe cache locally on your device.

activeTab — lets the popup read the currently detected recipe from the tab you have open when you click the icon.

AI processing on save

Recipes saved via the extension are passed through Mise's AI ingredient parser (Google Gemini) to convert free-text ingredient lines into structured {name, amount, unit, note} fields before storage. This is the same processor used by the main app's import feature, and uses count against the same monthly AI import limit (see AI processing above for our AI training-data policy).

Uninstalling and deletion

Recipes you have already saved are part of your Mise account — uninstalling the extension does not delete them. To remove them, delete the recipes in your Mise Recipe Box, or delete your account (see Your rights). Removing the extension from Chrome clears all locally-stored tokens and the per-tab cache.

Policy updates

When this policy changes.

We may update this Privacy Policy from time to time. For material changes — changes that affect your rights or the way we use your personal information — we will provide at least 14 days' advance notice by email to your registered address before the new policy takes effect. For non-material corrections, we may update the policy immediately. The "Last updated" date at the top of this page always reflects the current version. Continued use of the Service after the effective date of a material change constitutes acceptance of the updated policy.

Your privacy choices

In the Mise app, PostHog, Google Ads and Reddit show us which of our ads bring people who make a book. We never sell your data.

Analytics and ad measurement: …