Privacy Policy

This summary is here so you do not have to read nineteen sections to learn the important parts. It is a summary, not a substitute: the sections below govern.

• You can print a recipe without making an account. Do that, and your recipes stay in your own browser.
• The moment you import a recipe from a link, a photo, or pasted text, that content is sent to our recipe-reading service so it can be turned into a recipe card. That step is automated, and no human at Good Problem LLC reads your recipes as a matter of course.
• If you make an account and save a project, that project is stored under your account so you can reopen it on another device.
• Photos you add are uploaded to our file storage, and the resulting links are public to anyone who has them. See section 7.
• We use analytics to see which features work and which break. It is keyed to a random device identifier, not your name, and you can turn it off.
• We do not sell your personal information, we do not share it for cross-context behavioral advertising, and there are no advertising trackers on this site.
• Ask us to delete your account and everything in it, and we will.

RecipePrinter is operated by Good Problem LLC (“we”, “us”). This policy covers the RecipePrinter website at recipeprinter.com and everything you can do on it.

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

RecipePrinter is a separate product from CookPilot, a recipe app built by the same people. RecipePrinter uses CookPilot's recipe-reading service to interpret imports, which is described in section 6. Signing in to CookPilot to bring your library across is optional, and your CookPilot account is governed by CookPilot's own privacy policy.

Most of RecipePrinter works signed out, and that path collects the least. When you are not signed in:

• Your print queue, your project list, and your print settings are kept in your own browser's local storage. They are not stored in an account, and we cannot read them.
• Your browser generates a random identifier so that our recipe-reading service can apply usage limits per visitor, and so that photos you upload can be kept separate from other people's. It is a random string. It is not tied to your name or email.
• Recipes you import are still sent to the recipe-reading service, and photos you add are still uploaded. Those two steps require leaving your browser no matter how you are signed in.

Clearing your browser's site data for recipeprinter.com erases the local side of this, including your queue and your analytics opt-out if you have set one.

Things you give us

• Recipe content. The links, pasted text, photos, screenshots, and recipe-app export files you import, plus any edits, notes, titles, or arrangements you make afterwards.
• Account details. If you make 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, and never your password. If you use an email and password, the password is handled by Google Firebase Authentication and is never visible to us.
• Saved projects. If you choose to save, the contents of that project are stored under your account.
• Purchases. When you buy a cookbook or subscribe to RecipePrinter Pro, we receive a record of what was bought, its renewal status if it's a subscription, and the email address attached to it. Card numbers go to Stripe and never reach us.
• Feedback. If you use the feedback form, we store your message, your email address if you provide one, and the page you were on, along with your browser type, language, window size, and referring page so we can reproduce what you were describing.

Things collected automatically

• Product analytics. A deliberately small, fixed list of events: a page was viewed, an import started, an import succeeded or failed and why, a recipe was printed, a theme was chosen, a paywall was seen, a purchase completed, feedback was sent. We record the hostname of a recipe site you import from, so we can see which sites we fail on. We do not record the full address of the recipe you are cooking.
• A device identifier. Analytics is keyed to a random identifier your browser generates, so a return visit is not counted as a new person. If you sign in, your account identifier is attached too. Your email address is not sent to analytics.
• How you arrived. The referring site and any campaign parameters on the address you landed on, recorded once, so we know which sources bring people here.
• Device and connection details. Browser, operating system, screen size, language, and IP address. IP address is used by our analytics provider to derive an approximate city-level location and is not stored against your profile by us.
• Server logs and abuse limits. Our host records standard request logs. Our own usage limits count requests against your IP address in memory, briefly, so that one visitor cannot exhaust the recipe parser for everyone.
• Crash reports. When something breaks, we record the error and the page it happened on.

What we deliberately do not collect

There is no advertising network on this site, no third-party ad cookies, and no data broker involved. Session recording is off. Broad automatic capture of every click and keystroke, which our analytics tool offers and turns on by default, is switched off. We record only the specific events listed above. We do not collect payment card details, and we do not ask for information about your health, even though a recipe may reveal something about your diet.

We use what we collect to run the product, and for nothing else. If you are in the EU or the UK, the legal basis for each purpose is named alongside it.

• To turn your import into a recipe card, by reading the link, photo, or text you gave us and printing the result. Performance of a contract.
• To keep your saved projects and let you reopen them on another device. Performance of a contract.
• To take payment and unlock what you bought. Performance of a contract.
• To answer your feedback or your email. Legitimate interests, in responding to people who contact us.
• To understand which features are used and which fail, and to fix them. Legitimate interests, in improving a product people rely on, balanced by keeping the event list small and the identifiers anonymous. You can opt out; see section 13.
• To prevent abuse and stop one visitor from consuming a shared resource. Legitimate interests, in keeping the service available and affordable to run.
• To meet legal obligations, such as keeping tax records for a purchase. Legal obligation.

We do not use your recipes, photos, or notes to train machine learning models of our own, and we do not sell them or hand them to anyone beyond the service providers listed in section 9.

This is the part of RecipePrinter that most needs explaining, because it is the one step that always leaves your browser.

When you import a recipe, the link, text, photo, or export file goes to our recipe-reading service, which runs on Google Firebase and is shared with CookPilot. There, an automated system, including AI models that read images and text, extracts the title, ingredients, and steps and sends a structured recipe back to your browser. When you import from a link, that service, or in some cases our own server, also fetches the page at that address in order to read it. That request goes to the recipe site, and it will see it as a visit.

Content sent for reading is processed to produce your recipe and to diagnose failures. 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 that service process the content on our instructions as service providers.

A Paprika export file is different, and better: it is unpacked and read entirely inside your browser, and its contents are never uploaded.

Photos you add to a recipe or a cookbook cover are uploaded to our file storage on Google Firebase. Only the resulting link is kept in your project, which is what keeps a saved cookbook small enough to store.

Deleting a project deletes the photos uploaded with it. You can also ask us to delete any photo at recipeprinter@goodproblem.studio.

RecipePrinter uses no advertising cookies and no third-party tracking cookies. What it does use falls into three groups.

• Strictly necessary. Your print queue, project list, print settings, the random visitor identifier, and, if you are signed in, your login session, all held in your browser's local and session storage. Without these the product cannot work, so there is nothing to consent to and nothing to switch off short of clearing site data.
• Analytics. Our analytics tool sets a cookie and a local storage entry holding the random device identifier described above. You can opt out at any time; see section 13.
• Purchases. If you buy something, identifiers for your purchase record are stored locally so the unlock survives a page reload.

Analytics requests are routed through recipeprinter.com rather than being sent to our analytics provider's own domain. This is so that content blockers do not silently distort the numbers. The data still goes to PostHog, as described in section 9; the routing changes the path, not the recipient.

We do not sell personal information and we do not share it for advertising. We do use a small number of service providers, each handling only what its job requires and each bound to use it only on our instructions.

Beyond these, we will disclose information if the law requires it, such as a valid legal request or a court order, or where it is necessary to establish or defend a legal claim, or to protect someone's safety. If RecipePrinter is ever sold or merged, information may transfer with it, and we will say so here before that takes effect.

Good Problem LLC is in the United States, and the providers above process data in the United States and in other countries where they operate. If you are in the EU, the UK, or Switzerland, this means your information is transferred outside your country.

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

• Unsaved work stays in your browser only, for as long as your browser keeps it. Clearing site data removes it immediately.
• Saved projects and uploaded photos are kept until you delete them or ask us to delete your account. They are not on a timer, because a cookbook you built two years ago should still open.
• Account details are kept while your account exists.
• Purchase records are kept for as long as tax and accounting law requires, generally seven years, even after an account is deleted. This is the one category we cannot erase on request.
• Analytics events are retained by our analytics provider under its own retention schedule, currently up to seven years for events and one year for less-used data.
• Feedback messages are kept until we have acted on them and for a reasonable period afterwards.
• Server logs are kept by our host 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 never store your password. Payment card details go directly to Stripe. Access rules on our database restrict a saved project to the account that owns it, and the paid cookbook renderer checks both your identity and your purchase before it will run.

No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects your personal information, we will notify you and the relevant regulator where the law requires it.

• Use it signed out. The whole printing flow works without an account, and nothing is stored under your name.
• Turn analytics off. Visit recipeprinter.com/?optout and this browser stops sending analytics entirely, including pageviews. The choice is remembered in your browser's local storage, so it survives reloads but not clearing site data. We also honor the Global Privacy Control signal where your browser sends one.
• Delete a project. Deleting a saved project removes it and the photos uploaded with it.
• Delete your account. Email recipeprinter@goodproblem.studio from the address on the account and we will delete the account and everything stored under it, other than purchase records we are required to keep.
• Clear local data. Clearing site data for recipeprinter.com in your browser removes your queue, settings, and local identifiers.

Wherever you are, you can ask us to give you a copy of what we hold about you, correct it, or delete it. Write to recipeprinter@goodproblem.studio and say what you want. We do not charge for this, and we will not treat you differently for asking.

We will need to be reasonably confident you are who you say you are before acting, which usually means writing from the email address on the account. If you are asking on someone else's behalf, tell us and we will explain what we need. If we cannot fulfil a request, we will tell you why.

Under the GDPR and UK GDPR you have the right to access your data, have it corrected, have it erased, restrict or object to how we use it, receive it in a portable format, and withdraw consent where we relied on consent. Where we rely on legitimate interests, meaning analytics and abuse prevention, you can object, and the analytics opt-out in section 13 gives immediate effect to that objection.

No decision with a legal or similarly significant effect on you is made about you by automated means. The automated reading described in section 6 interprets a recipe; it does not evaluate you.

If you think we have handled your data badly, please tell us first at recipeprinter@goodproblem.studio so we can put it right. You also have the right to complain to your national supervisory authority, or to the Information Commissioner's Office in the UK.

California residents have rights under the CCPA as amended by the CPRA, and 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 described in section 4: identifiers, internet and device activity, approximate location derived from IP address, commercial information about purchases, and the content you choose to upload.

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

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We have not done so in the preceding twelve months, and we do not do this for anyone under 16. Because there is nothing to opt out of, there is no “Do Not Sell or Share My Personal Information” link on this site. We do not use or disclose sensitive personal information for any purpose that would give rise to a right to limit it.

If we decline a request, you may appeal by replying to our response. In the states that provide one, you may also complain to your state Attorney General.

RecipePrinter is not directed to children, and it is not designed 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 given us personal information, write to recipeprinter@goodproblem.studio and we will delete it.

When this policy changes, we update the date at the top. If a change materially affects what we collect or who we send it to, we will make that clear on the site before it takes effect, and where the law requires consent we will ask for it rather than assume it.

Write to recipeprinter@goodproblem.studio and a person will read it. We aim to reply within a few days, and within any deadline the law sets for the kind of request you are making.

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 cover what you can do with RecipePrinter and what we promise in return.