Privacy Policy
Last updated 14 September 2026
RecipeGo is made by Taralia LLC. This policy says what we collect, who else touches it, how long we keep it, and how to take it back. We do not sell your data and we do not advertise in the app — there is no business reason for us to want more of your information than the app needs to work.
On this page
1. What we collect
Things you give us
- Account: your email address, and a password — stored only as a cryptographic hash, never as text we can read. If you sign in with Google we receive your email address and name from Google; we never receive your Google password.
- Profile: a display name, and the preferences you set — measurement units, temperature scale, household size, dietary preferences, allergens you tell us about, and your preferred language.
- Your cooking content: recipes, ingredients, steps, private notes, ratings, cook logs, cookbooks, meal plans, grocery lists and any photographs you add.
- What you import: the web address, photographs or text you give us to turn into a recipe.
Things the app produces
- Usage counters: how many AI imports you have used in the current period, so the plan limits can be applied. Counts, not content.
- Import records: for each import — the source address, which method was used, whether it succeeded, any error, which AI model ran and what it cost us. This is how we find broken imports and control our own spending.
- Billing state: your plan, when it expires, the identifier your purchases are recorded under, and a log of billing events from the store. We never receive or store your card details.
What we do not collect. No location. No advertising identifiers. No contacts. No browsing history outside the pages you explicitly ask us to import. No analytics profile of how you move around the app. There are no advertising or tracking SDKs in RecipeGo.
2. Why we use it
- To run the app — store your library, sync it between your devices, search it, and show it back to you.
- To import recipes — read the page, photograph or text you gave us and turn it into structured data.
- To apply your plan — count what you have used against your allowance, and record what you have bought.
- To email you about your account — confirming your address, resetting your password, and telling you about changes to these documents or to pricing.
- To keep the service working and honest — find failures, prevent abuse of the free tier, and understand our own costs.
We do not use your recipes or your account information to advertise to you, and we do not sell or rent personal data to anyone.
3. AI processing
This section matters more than the rest, so it is separate and specific.
When you confirm an AI import, the content you are importing — the text of a web page, the photographs you chose, or the text you pasted — is sent to an AI provider to be read and turned into a structured recipe. Depending on the type of import and availability, that provider is one of:
- Google (Gemini), our primary model
- OpenAI, used when the primary is unavailable
- Anthropic, used for some import types
YouTube videos. When you import a YouTube video, we may read the recipe page its creator links in the description. If neither that page nor the description has the recipe, we send the video's web address to Google, and Google's model watches the video itself. We never download or store the video. The commitments below apply to this too.
What is true of all three, and what we commit to:
- Nothing is sent without you confirming it. The fast path for sites that publish machine-readable recipes involves no AI at all, and it is always tried first.
- We send the content being imported. We do not send your email address, your name, your library, your notes or your other recipes.
- We use these providers through their business APIs, under terms that do not permit your content to be used to train their models.
- We do not keep a copy of the prompt. What we retain is the structured recipe you chose to save, plus the cost and token counts of the call.
Ingredient text is also sent to the United States Department of Agriculture FoodData Central service to look up nutrition information. That request contains the name of an ingredient and nothing about you.
4. Who else processes your data
We use a small number of companies to run RecipeGo. They process data on our instructions, for the purposes below and nothing else. This is the complete list.
| Company | What it does for us | What it receives |
|---|---|---|
| Supabase | Database, accounts, file storage, server functions | Everything in section 1. This is where RecipeGo lives. |
| Google (Gemini) | Reads imports | The content of an import you confirmed |
| OpenAI | Reads imports when the primary model is unavailable | The content of an import you confirmed |
| Anthropic | Reads some import types | The content of an import you confirmed |
| USDA FoodData Central | Nutrition lookup | Ingredient names only |
| Resend | Sends our email | Your email address and the message |
| RevenueCat | Manages subscriptions and entitlements | An account identifier and purchase events. No card details. |
| Google Play | Takes payment | Your payment details, which go to Google and never to us |
We will also disclose information if the law genuinely requires it, and we will tell you unless we are prohibited from doing so. If RecipeGo is ever sold or merged, your data may transfer as part of that, and we will tell you before it does.
Our servers and these providers are located in the United States. If you use RecipeGo from elsewhere, your information is processed in the US.
5. The shared import cache
This is unusual enough to state plainly rather than leave in a definition.
When someone imports a recipe from a public web address, we keep the structured result against that address. If another person later imports the same address, they get the stored result instead of us paying to read the page again. It makes popular recipes instant and free, and it is a large part of how the free tier can exist.
What that means for you:
- It applies only to public web addresses you import, never to your photographs, your notes, your edits or your pasted text.
- The cached entry contains the recipe as published at that address. It contains nothing about you, and no way to tell who imported it.
- Your own copy stays yours. Editing it changes only your copy.
Photographs you import are cached too, but only against your account, so that re-importing the same picture does not charge you twice. That cache is never shared with another user.
6. How long we keep it, and deletion
- Your library and profile — kept until you delete them or close your account.
- Import and billing records — kept while your account exists, because they are how allowances and purchases are calculated.
- The shared import cache — kept as long as it is useful, and not linked to you.
Deleting your account is in the app, at Settings → Data & export. It removes your account, your library, your photographs, your notes and your profile. Some billing records are retained where we are required to keep them for tax and accounting, without the content of your library attached.
Exporting your data is on the same screen and produces a JSON file of your whole library. You do not have to ask us, and you do not have to be a subscriber.
7. Your rights
Wherever you live, you can ask us to give you a copy of your data, correct it, or delete it. The export and delete buttons in the app do the first and third immediately; for anything else, write to us.
If you are in the European Economic Area or the UK, our lawful bases are: performing our contract with you (running the app, and billing), your consent (each AI import you confirm), and our legitimate interests (keeping the service secure and working). You may object to processing, ask us to restrict it, and complain to your data protection authority.
If you are in California, you may request the categories and specific pieces of personal information we hold, request deletion, and not be discriminated against for asking. We do not sell or share personal information as those terms are defined by the CCPA, and we never have.
To exercise any of this: contact@recipego.taralia.com. We will reply within 30 days.
8. Security
Everything travels over encrypted connections, and is encrypted at rest by our hosting provider. Passwords are stored only as hashes. Access to a recipe is enforced in the database itself by row-level security, so one account cannot read another's library even if the app were wrong about who is asking.
No system is perfect. If we discover a breach affecting your personal data, we will tell you and the relevant authority as the law requires.
9. Children
RecipeGo is not intended for children under 13 and we do not knowingly collect their information. If you believe a child has created an account, write to us and we will remove it.
10. Changes and contact
If we change this policy materially, we will tell you by email before it takes effect, and the date at the top will change.
Taralia LLC — contact@recipego.taralia.com