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.
Providing the Service. Account information, recipe and book content, billing data, and order information are processed to deliver the features you use and fulfil your print orders. Legal basis: performance of a contract.
Payment processing. Billing data is shared with Stripe to process subscription and one-off payments. Legal basis: contract performance.
Print fulfilment. Your name, address, phone number, and book PDF are shared with our print partner to manufacture and ship your book. Legal basis: contract performance.
Communications. We use your email address to send transactional emails (order confirmations, shipping updates, account notices) via Resend. Legal basis: contract performance and legitimate interests.
Newsletter. If you subscribe and confirm, we email you Notes from the studio about once a month. Legal basis: consent, which you withdraw with the unsubscribe link in every issue.
Waiting list. If you join it, we email you once to confirm and once the day we deliver to your country. Legal basis: consent, which you withdraw by replying to either email.
Reminders about your book. If you save a book to an account and leave it unfinished, we email you at most twice about that book: about a day later, and once more three days after that if you have not come back to it. We stop as soon as you return to the book or order it. Legal basis: legitimate interests (helping you finish the book you started); stop them with the link in either email.
Product analytics. Behavioral data (PostHog events, session replays, lifecycle timestamps) is used to understand how people use the Service, identify bugs, and prioritise features. Legal basis: in the app, your consent in the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec; elsewhere, our legitimate interest in understanding how the Service is used, which you can object to at any time under Your privacy choices. On the public content pages, which store nothing on your device, legitimate interests.
Marketing attribution. UTM data, click IDs, and referrer data are used to measure the effectiveness of our marketing campaigns and advertising spend. They are recorded only while analytics is on. Legal basis: as for product analytics.
Ad measurement. While ad measurement is on, Google Ads and Reddit Ads measure whether an ad click led to a sign-up or an order (Reddit also counts a new book). Neither is used for remarketing, and we do not upload customer lists or email addresses to advertising platforms. Legal basis: your consent in the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec; elsewhere, our legitimate interest in knowing what our advertising achieves, which you can object to under Your privacy choices.
Fraud prevention and security. Technical data (IP address, user-agent) and usage patterns are used to detect abuse, spam, and fraud; on sign-in and sign-up, Cloudflare Turnstile checks that a person rather than a script is signing in. Legal basis: legitimate interests.
Legal compliance. Order data is retained to comply with tax and accounting obligations. Legal basis: compliance with legal obligations.
AI usage enforcement. Usage logs are processed to enforce per-tier AI usage limits. Legal basis: contract performance.
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:
Training data. Under Google's current API terms, inputs submitted through the Gemini API are not used to train Google's AI models. This is a commitment in Google's API usage policy, not a commitment we can independently guarantee in perpetuity. If Google's policy changes in a way that affects how your data is handled, we will notify you and update this section. You can review Google's current API data-use policy at ai.google.dev/gemini-api/terms.
Review before printing. AI output can contain inaccuracies. Your book is printed from what you approve — read it before you order. Mise is not responsible for errors in AI-parsed content that you save without reviewing.
Our processors
Who else touches your data.
We share the minimum required with each partner. Nothing is sold for profit.
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.
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.
Delete. You may delete your account at any time in Studio → Settings → Your data → Delete account. This deletes all recipes, books, photos, and support data. Order records are retained for 7 years as described under Data retention. You may also request deletion of specific data by writing to legal@misebook.io.
Access. You may request a copy of the personal information we hold about you. We will provide it in a structured, commonly used, machine-readable format within 30 days.
Correct. If any personal information we hold about you is inaccurate or incomplete, you may update most of it directly in your account settings, or request a correction by writing to us.
Portability. You may download your recipes as a structured file at any time, at no cost, from within the app.
Withdraw consent, or turn it off (analytics and ad measurement). You may withdraw consent for PostHog analytics and the Google Ads and Reddit Ads measurement at any time, or, where they are on by default, turn them off, under Your privacy choices at the bottom of our pages of the Mise app or in Studio → Settings → Your data. For the newsletter, use the unsubscribe link in every issue. Withdrawal does not affect the lawfulness of processing before withdrawal.
Object to processing. You may object to processing based on legitimate interests (such as the security checks, or measuring which public pages are read) by writing to legal@misebook.io.
Ask us anything. Write to legal@misebook.io and we will answer in plain language within 30 days.
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:
Encryption in transit. All data exchanged between your browser and our servers is encrypted via TLS (HTTPS).
Encryption at rest. Data stored in Supabase and Cloudflare R2 is encrypted at rest by those platforms.
Access controls. Database access is restricted by row-level security policies ensuring users can only access their own data. Administrative access requires separate authentication.
Minimal data sharing. We share only the minimum data required with each third-party processor.
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
Right to Know. You may request that we disclose the categories and specific pieces of personal information we have collected about you, the sources, the purposes, and any third parties with whom we have shared it.
Right to Delete. You may request deletion of your personal information, subject to certain legal exceptions (including the 7-year order retention described under Data retention).
Right to Correct. You may request correction of inaccurate personal information we hold about you.
Right to Opt Out of Sale / Sharing. Use Your privacy choices at the bottom of our pages or in Studio → Settings → Your data, or send the Global Privacy Control signal: either turns off the Google Ads and Reddit Ads measurement and PostHog analytics.
Right to Limit Use of Sensitive Personal Information. We do not use sensitive personal information for purposes beyond those necessary to provide the Service.
Non-discrimination. We will not discriminate against you for exercising any CCPA rights.
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.
Cookies & local storage
What stays in your browser.
We use a small number of cookies and browser-storage values, listed below. Essential ones keep you signed in and are needed for the Service to work. In the app, whether analytics (PostHog) and ad measurement (Google Ads and Reddit Ads) are on depends on where you are. In the European Union, the European Economic Area, the United Kingdom, Switzerland and Quebec, and whenever we cannot tell where you are, they are switched on only if you press Accept: until you choose, nothing of theirs is stored on your device, and ignoring the banner counts as no. Everywhere else they are on by default, and you can turn them off at any time. Either way, a browser that sends the Global Privacy Control signal keeps them off, and if you say no, or turn them off later, what they stored is deleted. To know which applies, the app asks our own server once per visit. The server looks up only the country (and, in Canada, the province) that your connection comes from, in our copy of a public database, and answers yes or no. Neither your address nor the answer is kept, on our server or on your device. Our public content pages set no analytics cookie and no persistent identifier at all; they keep one session-scoped key, mise_utm, which is cleared when you close the tab. Separately, the app sends our own server anonymous counts: when you arrive from one of our ads; when the cookie banner is shown and answered; each step of making a book that you reach (for example opening the Recipes step or adding a first recipe) and problems such as an import that failed; and, when you leave, how far you got and roughly how long you stayed (in bands such as two to five minutes). Each count says which ad brought you, the page, the kind of device (phone, tablet or computer), your approximate location (country, state or region, and city) and that step or answer. The location is looked up on our own server, in a copy of a public database (IP Geolocation by DB-IP), from the address your connection comes from; the address itself never leaves our server and is not kept. It carries no identifier and no cookie, the counts cannot be joined to each other or to you, nothing is stored on your device, and your IP address is not kept, so it does not need your choice; a browser that sends the Global Privacy Control signal sends none. We use these totals to see how many people our ads bring, where people stop while making a book, and how many say no to cookies.
Changing your choice: use Your privacy choices at the bottom of our pages of the Mise app, or Studio → Settings → Your data. Google Ads and Reddit Ads are used only to measure what an ad led to (a sign-up, a new book or an order), not for remarketing.
Ad-blocker proxy note: PostHog analytics requests are routed through a first-party path on misebook.io (specifically /ingest) so that they reach our analytics server even when ad-blocking browser extensions are active. This means PostHog analytics data is collected at approximately the same rate regardless of whether you use an ad blocker. In the app, events are sent only while analytics is on (where we ask, only after you accept) — the proxy does not bypass your choice. Before analytics is on, the analytics library loads its settings once from PostHog’s EU servers through that same path; nothing is stored on your device and no event is sent. On the public content pages there is no consent requirement to bypass, because nothing is stored on your device.
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:
When you click "Save to Recipe Box": the recipe (title, description, ingredients, instructions, prep/cook times, servings, category, hero image URL, source page URL) and your Mise account access token are sent to
https://misebook.io/api/recipes/saveover HTTPS, where the recipe is stored in your Mise account.When your sign-in session expires: the extension sends a refresh token to
https://misebook.io/api/extension/refresh-sessionto obtain a new access token. No recipe content is transmitted on this call.
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
No tracking of your browsing history. The extension does not record which pages you visit.
No analytics or telemetry from inside the extension. No PostHog, Google Analytics, or any third-party scripts run in the extension.
No data is transmitted on page load. The toolbar badge updates locally; nothing is sent to our servers until you explicitly click Save.
No advertising, no data brokers, no sale or sharing with third parties.
No access to cookies, passwords, financial information, health information, or location.
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.