Privacy Policy

This summary highlights the main points. The full sections below govern.

• You can print recipes without an account. When you are signed out, your recipes, projects, and photos are kept in your own browser.
• When you import a recipe from a link, a photo, or pasted text, that content is sent to our recipe-reading service, which processes it automatically to produce a recipe card.
• If you create an account and save a project, the project and its photos are stored under your account so you can open them on other devices. Stored photo links are accessible to anyone who has the link. See section 7.
• We use product analytics to understand which features are used and where problems occur. You can opt out at any time.
• We use Google Ads, Reddit Ads, and Meta Ads to measure which of our ads lead to a purchase. We do not use them in the EU, the UK, or Switzerland, and the analytics opt-out and Global Privacy Control stop all three, anywhere.
• We do not sell your personal information. Google and Reddit may not use what they measure here for personalized ads. Meta may not in California and the other states where Meta applies its Limited Data Use; elsewhere, Meta may use it under its own terms. See section 16.
• You can ask us to delete your account and the information stored under it.

RecipePrinter is operated by Good Problem LLC (“we”, “us”, or “our”). This policy covers the RecipePrinter website at recipeprinter.com and the services offered on it.

For the purposes of the EU and UK General Data Protection Regulation, Good Problem LLC is the data controller for the information described in this policy. You can contact us at recipeprinter@goodproblem.studio.

RecipePrinter is a separate product from CookPilot, a recipe app from the same team. RecipePrinter uses CookPilot's recipe-reading service to process imports, as described in section 6. Signing in to CookPilot to import a recipe library is optional, and your CookPilot account is governed by CookPilot's own privacy policy.

Most of RecipePrinter works without an account, and that is the way to use it that collects the least information. When you are not signed in:

• Your print queue, projects, print settings, and the photos you add are stored in your browser's local storage and IndexedDB. They are not stored in an account, and we cannot access them.
• Your browser generates a random identifier so that our recipe-reading service can apply per-visitor usage limits and count imports (see “Import counts” in section 4). It is not linked to your name or email address.
• Recipes you import are still sent to our recipe-reading service, because reading a recipe requires it.
• If you later sign in and save a project, the photos in it are uploaded to your account at that point.

Clearing your browser's site data for recipeprinter.com deletes this locally stored information, including any unsaved work, and any analytics opt-out you have set.

Information you provide

• Recipe content. The links, pasted text, photos, screenshots, and recipe-app export files you import, and any edits, notes, titles, or arrangements you make.
• Account information. If you create an account, your email address and an account identifier. If you sign in with Google or Apple, we receive your email address and basic profile details from them, but not your password. If you sign in with an email and password, the password is handled by Google Firebase Authentication and is not visible to us.
• Saved projects. If you save a project, its contents and photos are stored under your account.
• Purchases. When you buy a cookbook or subscribe to RecipePrinter Pro, we receive a record of the purchase, the renewal status of any subscription, and the associated email address. Card details are handled by Stripe and are not received by us.
• Feedback. If you use the feedback form, we store your message, your email address if you provide one, the page you were on, and your browser type, language, window size, and referring page, so that we can investigate the issue you describe.
• Gallery submissions. If you submit a photo of your printed recipes to the homepage gallery, we store the photo and your email address if you provide one. A submitted photo is reviewed before anything is published, and it may appear publicly on the site if approved.

Information collected automatically

• Product analytics. A defined set of events, such as page views, imports started, imports that succeeded or failed and why, prints, theme choices, paywall views, purchases, and feedback sent. For imports from a website, we record the website's hostname so we can see which sites fail, and the address of the recipe page you imported, so that a recipe we read incorrectly can be reproduced and fixed.
• Session replay. We may record how pages respond to your interactions, such as scrolling, clicks, and layout changes, to diagnose problems. Text you type into form fields is masked and is not recorded. The analytics opt-out in section 13 also stops session replay.
• Device identifier. Analytics is linked to a random identifier generated by your browser, so a return visit is not counted as a new visitor. If you sign in, your account identifier is also attached. Your email address is not sent to analytics.
• Referral information. The referring website and any campaign parameters in the address you arrived at, recorded once, so we understand how visitors find the site.
• Device and connection information. Browser, operating system, screen size, language, and IP address. Our analytics provider uses the IP address to estimate an approximate, city-level location.
• Advertising measurement. Outside the EU, the UK, and Switzerland, a Google Ads tag, a Reddit Ads pixel, and a Meta pixel record the pages you visit on this site and whether you arrived from one of our ads on Google, Reddit, Facebook, or Instagram, so that when you buy a cookbook we can tell which ad, if any, led to it. They also record when you start a cookbook and when you open its checkout. For a purchase, they send the amount, the currency, and a transaction number. Reddit is also sent your approximate country and state, which tells it which privacy law applies. When you buy a cookbook from a browser where the Meta pixel ran, our payment system also sends Meta the same purchase directly, with the Meta cookies described in section 8, your browser's user agent, and your approximate country and state, so the sale is counted even if the pixel was blocked; Meta counts the two copies once. None of them is sent your name, email address, photos, or the content of your recipes or cookbooks. See section 8 for the cookies it uses.
• Server logs and usage limits. Our hosting provider keeps standard request logs. Our usage limits briefly count requests by IP address in memory, to keep the recipe-reading service available to everyone.
• Import counts. We count successful recipe imports for each browser, or for each account when you are signed in, to apply the free import allowance and show you how much of it you have used. For each import we keep the time, the kind of import, and a short one-way fingerprint of the link or text, so importing the same recipe again is not counted twice; the recipe itself is not kept. The analytics opt-out does not stop these counts.
• Error reports. When an error occurs, we record the error and the page where it happened.
• Failed and corrected imports. When an import fails, we keep a copy of what was imported, such as the link, the pasted text, or the images, along with the reason it failed and, if you are signed in, your email address. When an import succeeds but you then rewrite much of it by hand shortly afterwards, which usually means we read it incorrectly, we keep a copy of what you pasted, what we read, and your corrected version. We use these copies only to diagnose and improve how recipes are read.

What we do not collect

We do not use remarketing, personalized advertising, or data brokers, and the only advertising tags on the site are the Google Ads, Reddit Ads, and Meta Ads measurement described above. The Meta pixel's automatic event setup, which reads buttons and page details, is turned off. Automatic capture of every click, which our analytics tool offers, is turned off, and we record only the events described above. We do not collect payment card details, and we do not ask for health information, although a recipe may indicate something about your diet.

We use the information we collect only to operate and improve RecipePrinter. For users in the EU and the UK, the legal basis for each purpose is shown alongside it.

• To turn your import into a recipe card by reading the link, photo, or text you provide and formatting the result. Performance of a contract.
• To store your saved projects and make them available on your other devices. Performance of a contract.
• To process payments and provide what you purchased. Performance of a contract.
• To respond to feedback, messages, and gallery submissions. Legitimate interests, in responding to people who contact us.
• To understand which features are used and diagnose problems, including failed imports and imports that were read incorrectly. Legitimate interests, in maintaining and improving the service, balanced by limiting what we collect and using random identifiers. You can opt out of analytics; see section 13.
• To measure which of our ads lead to purchases, so we spend on advertising that works. Legitimate interests, in understanding our own advertising. We do not do this in the EU, the UK, or Switzerland.
• To prevent abuse of shared resources, and to enforce the once-per-person free allowance and our Terms. Legitimate interests, in keeping the service available and fair.
• To meet legal obligations, such as keeping tax records for purchases. Legal obligation.

We do not use your recipes, photos, or notes to train our own machine learning models, and we do not sell them or share them with anyone other than the service providers described in section 9.

When you import a recipe, the link, text, photo, or export file is sent to our recipe-reading service, which runs on Google Firebase and is shared with CookPilot. An automated system, including AI models that read images and text, extracts the title, ingredients, and steps and returns a structured recipe to your browser.

When you import from a link, the recipe-reading service, our own server, or a page-fetching provider retrieves the page at that address in order to read it. The website will see this as a visit.

Imported content is processed to produce your recipe and, when an import fails, to diagnose the failure. It is not used to build a public recipe database, it is not sold, and it is not used to train our own models. The AI providers behind the service process content on our instructions as service providers.

Paprika export files are unpacked and read entirely within your browser, and their contents are not uploaded.

When you are signed in, photos you add to a recipe, a chapter, or a cookbook cover are uploaded to our file storage on Google Firebase, and only a link to each photo is kept in your project. When you are signed out, photos stay in your browser and are uploaded only if you later save the project to an account.

Deleting a saved project deletes the photos stored for it, except any photo that another of your saved projects also uses. Deleting your account deletes all of your stored photos. You can also ask us to delete any specific photo at recipeprinter@goodproblem.studio.

When you export a cookbook, the PDF is generated on our servers and stored temporarily so that you can download it. Exported files are deleted automatically after a few days.

RecipePrinter does not use cookies for remarketing or personalized advertising. The cookies and browser storage it uses fall into four categories.

• Strictly necessary. Your print queue, projects, print settings, photos you add while signed out, the random visitor identifier, and your sign-in session if you are signed in, stored in your browser's local storage, session storage, and IndexedDB. These are required for the service to work, so they cannot be turned off other than by clearing site data.
• Analytics. Our analytics provider sets a cookie and a local storage entry containing the random device identifier described above. You can opt out at any time; see section 13.
• Advertising measurement. Outside the EU, the UK, and Switzerland, Google Ads, Reddit Ads, and Meta set first-party cookies on recipeprinter.com (named starting with _gcl, _rdt, and _fb) that hold a random identifier and the click identifier from an ad you followed, and each may read its own cookies on google.com, reddit.com, or facebook.com, so that a later purchase can be matched to that ad. The analytics opt-out and Global Privacy Control both stop these tags from loading; see section 13.
• Purchases. If you make a purchase, identifiers for your purchase record are stored locally so that your access continues after a page reload.

Analytics requests are routed through recipeprinter.com rather than sent directly to our analytics provider's domain, so that content blockers do not distort our measurements. The data is still received by PostHog, as described in section 9.

We do not sell personal information. We use the service providers below, each of which receives only what it needs to perform its function and may use it only on our instructions. The one exception is Meta outside the states where it applies Limited Data Use, where it may also use our ad measurement under its own terms (see section 16). Each provider's name links to its own privacy policy.

We may also disclose information where required by law, such as in response to a valid legal request or court order, where necessary to establish or defend a legal claim, or to protect someone's safety. If RecipePrinter is sold or merged, information may be transferred as part of that transaction, and we will update this policy before that takes effect.

Good Problem LLC is based in the United States, and our service providers process data in the United States and other countries where they operate. If you are in the EU, the UK, or Switzerland, your information will be transferred outside your country.

Where a transfer requires a safeguard, we rely on the European Commission's Standard Contractual Clauses and, for UK transfers, the UK Addendum, which our service providers include in their data processing terms. You can request details of the safeguards that apply to you at recipeprinter@goodproblem.studio.

• Unsaved work, including photos added while signed out, is kept only in your browser for as long as your browser keeps it. Clearing site data deletes it.
• Saved projects and their photos are kept until you delete the project or ask us to delete your account. They are not deleted on a schedule, so that a cookbook you saved remains available.
• Exported cookbook PDFs are deleted automatically after a few days.
• Account information is kept while your account exists.
• Purchase records are kept for as long as tax and accounting laws require, generally seven years, including after an account is deleted.
• Analytics data is retained by our analytics provider under its retention schedule, currently up to seven years for events and one year for less frequently used data.
• Copies of failed and corrected imports are kept until they have been reviewed and resolved. You can ask us to delete them at any time.
• Feedback messages and gallery submissions are kept until we have responded to or reviewed them, and for a reasonable period afterwards. An approved gallery photo is kept for as long as it is displayed.
• Import counts are deleted automatically 31 days after your most recent import.
• Server logs are kept by our hosting provider for a short period, typically about a month.

The site is served over HTTPS. Accounts and sign-in are handled by Google Firebase Authentication, so we do not store passwords. Payment card details are handled directly by Stripe. Our database access rules restrict each saved project to the account that owns it, and the cookbook export service verifies both your identity and your purchase before it runs.

No system is completely secure, and we cannot guarantee absolute security. If a breach affects your personal information, we will notify you and the relevant authorities where required by law.

• Use RecipePrinter signed out. The printing flow works without an account, and nothing is stored under your name.
• Opt out of analytics. Visit recipeprinter.com/?optout and this browser will stop sending analytics, including page views and session replay, and will stop loading the Google Ads, Reddit Ads, and Meta Ads measurement tags. The setting is saved in your browser's local storage, so it remains after a reload but is removed if you clear site data. If your browser sends the Global Privacy Control signal, we treat it the same way, with nothing to set.
• Delete a project. Deleting a saved project removes it and its stored photos, except photos another of your saved projects also uses.
• Delete your account. Email recipeprinter@goodproblem.studio from the address on your account, and we will delete the account and the information stored under it, except purchase records we are legally required to keep.
• Clear local data. Clearing site data for recipeprinter.com in your browser deletes your queue, settings, locally stored photos, and local identifiers.

Wherever you live, you can ask us for a copy of the personal information we hold about you, and ask us to correct or delete it. Send your request to recipeprinter@goodproblem.studio. We do not charge for requests, and we will not treat you differently for making one.

We will need to verify your identity before acting on a request, which usually means that the request comes from the email address on your account. If you are making a request on someone else's behalf, let us know and we will explain what we need. If we cannot fulfill a request, we will explain why.

Under the GDPR and UK GDPR, you have the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, to receive it in a portable format, and to withdraw consent where we rely on consent. Where we rely on legitimate interests, such as for analytics and abuse prevention, you may object, and the analytics opt-out in section 13 takes effect immediately.

We do not make decisions with legal or similarly significant effects about you by automated means. The automated processing described in section 6 interprets recipes and does not evaluate individuals.

If you have a concern about how we handle your data, you can contact us at recipeprinter@goodproblem.studio. You also have the right to lodge a complaint with your national data protection authority or, in the UK, the Information Commissioner's Office.

California residents have rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act. Residents of Colorado, Connecticut, Indiana, Montana, Oregon, Texas, Utah, Virginia, and other states with comprehensive privacy laws have comparable rights. In the past twelve months, we have collected the categories of information described in section 4: identifiers, internet and device activity, approximate location derived from IP address, commercial information about purchases, and content you choose to provide.

You may request to know what personal information we have collected and why, to receive a copy of it, to correct it, and to delete it. California residents may also request the specific pieces of personal information we have collected. You may use an authorized agent, and we will not discriminate against you for exercising these rights. Send requests to recipeprinter@goodproblem.studio, and we will verify them as described in section 14.

We do not sell personal information. We have not done so in the past twelve months, and we do not do so for anyone under 16. We do not use or disclose sensitive personal information for any purpose that would give rise to a right to limit its use.

In California, we do not share personal information for cross-context behavioral advertising, and have not in the past twelve months, because every advertising platform we use processes it there as our service provider (see below). For that reason, there is no “Do Not Sell or Share My Personal Information” link on this site.

Opting out of targeted advertising. Wherever you live, Global Privacy Control or the analytics opt-out (see section 13) stops all of our ad measurement in your browser, and a cookbook you buy from that browser is not reported to Meta by our payment system either. We treat either one as your request to opt out of targeted advertising under any state law that gives you that right.

Our Google Ads measurement runs with Google's restricted data processing turned on and ad personalization turned off, and our Reddit Ads measurement runs with Reddit's Limited Data Use turned on for every visitor. So Google and Reddit process that data as our service providers, to measure our own ads, and may not use it to build a profile of you or show you personalized ads. Our Meta Ads measurement, from the pixel and from our payment system, is sent with Meta's Limited Data Use, which Meta applies by your location in California and the other states it covers; there, Meta processes that data as our service provider on the same terms. In other places, Meta may also use it under its own terms, which can include improving the ads it shows. Global Privacy Control and the analytics opt-out both stop all of it.

If we decline your request, you may appeal by replying to our response. In states that provide for it, you may also contact your state Attorney General.

RecipePrinter is not directed to children and is not intended for anyone under 13. We do not knowingly collect personal information from children under 13, or under 16 in the EU and UK. If you believe a child has provided us with personal information, contact recipeprinter@goodproblem.studio and we will delete it.

We may update this policy from time to time. When we do, we will update the date at the top of this page. Where the law requires your consent to a change, we will ask for it.

Questions and requests can be sent to recipeprinter@goodproblem.studio. We aim to respond within a few business days, and always within any deadline the law sets for the type of request.

Good Problem LLC operates from Indiana, United States. A postal address for formal notices is available on request at the address above.

See also our Terms of Service, which govern your use of RecipePrinter.