Privacy Notice — Pinjula
Effective date: 29 October 2026
Contact: support@pinjula.com
This notice is published in English, French, Spanish, German, Italian and Turkish. The English text is the original; where a translation differs from it, the English text prevails. For residents of Québec, however, the French version is the version you accept unless, after receiving it, you expressly choose the English version.
Summary
This is the short version of our Privacy Notice; the full notice applies if the two differ. Each line says what we collect, where it goes, why, and how long it is kept.
- Stays on your phone. What: the people you cook for and what you enter about them (names, age bands, portion sizes, allergies with severity, intolerances, diets, disliked ingredients), your pantry, shopping list, calendar, cookbook, ratings and notes, and settings. Goes to: nobody. We never receive your allergies, diets, dislikes, household or ratings; the items that can leave are the names of the dishes whose pictures the app downloads (see "Dish pictures"), the dishes an AI feature needs, a dish name you type and the number of people you cook for (inside an AI request), the app's language (with AI requests and reports) and a report you choose to send. Why: so the app can filter and plan on your phone. Kept: until you delete it, delete your account or uninstall. Your phone's own backup to your Google or Apple account may include it.
- Dish pictures. What: the app asks our server for the pictures of the dishes it shows; the request names the dishes suggested to you, so it can show that some foods were left out, but not which, for whom or why; it also shows your IP address. Goes to: our server, on Cloudflare. Why: the pictures are not inside the app. Kept: Cloudflare's request record, up to 7 days, used only for faults and attacks.
- Signing in (only if you sign in). What: from Google, your name, email address, profile-picture address and account ID; from Apple, your email address (or relay address) and account ID, and on Android your name if Apple shares it; your sessions. Goes to: our sign-in service (Supabase, Frankfurt, Germany). Why: to run your account, which Premium and the AI features need. Kept: until you delete your account (sessions: until you sign out or they expire); Supabase's own logs of sign-in requests and events, under Supabase's retention (see "How long we keep things").
- Premium (only if you subscribe). What: your purchase records from the store, under your account ID, and your email address for the notices we must send. Goes to: RevenueCat and Resend (both United States) and our database. The store takes the payment; we never see your card. Why: to confirm Premium, send subscription notices and show that you agreed to the subscription. Kept: our records while active and 12 months after; a minimal record of each charge, with no name, email address or account ID, three years, even after you delete your account; RevenueCat until you delete your account; Resend under its own terms.
- AI features (only after you allow them). What: the dish names and details the feature needs, or a dish name you typed — never your allergies, diets, pantry or who is in your household (only how many people you cook for), though the dishes sent to plan how to cook a menu can show that your household leaves some foods out (not which, for whom or why); the dishes sent to mix cuisines are chosen without your household's allergies, diets or dislikes. Goes to: our server, then Google's Gemini. Why: to mix cuisines in one menu, plan how to cook a menu, or write a recipe for a dish you typed. Kept: Google, up to 55 days; we keep a count of dish names we had no recipe for, and how many AI requests your account sent each month, for Premium's monthly limit (until the end of the following month).
- Reports (only when you send one). What: a reason, your note, and a recipe's code or, for a recipe the app wrote, its text. Goes to: our database in Frankfurt. Why: to correct recipes. Kept: 12 months, with nothing that says who sent it.
- Usage statistics (off until you say yes). What: counts of screens and features used, under a random ID for the phone; never anything about your allergies, diets or household. Goes to: PostHog's EU cloud, Frankfurt. Why: to see what to improve. Kept: one year.
- Emails you send us. Goes to: our mailbox, hosted by Porkbun. Kept: 12 months after the last message.
No advertising, no sale of data. The app has no advertising library and no crash-reporting library, and the statistics library's own error reporting is switched off. (If your phone shares diagnostics with developers, Apple or Google may give us crash reports under their own policies.) We do not sell your information or share it for targeted advertising. Adults only: Pinjula is for people 18 and older; if your app store tells the app you are under 18, the app goes no further. You decide: the free version works without an account, statistics and the AI features each ask first, and you can export your data and delete your account in the app.
Who we are
Pinjula is published by Alpaslan Özlütürk, an individual developer trading as "Pinjula", Ankara, Türkiye ("we", "us"). We decide why and how the personal information described in this notice is used. You can write to us at support@pinjula.com, or by post to Çakırlar Mahallesi, 2210. Sokak No: 7B, Daire 30, 06370 Yenimahalle/Ankara, Türkiye. Our seller details are at pinjula.com/provider-information/.
The app is offered to people living in the United States and Canada. This notice applies to everyone. Two supplements add what the law of a place requires: United States and Canada and Québec. Where a supplement gives you more than this notice, it applies to you. Our separate Consumer Health Data Privacy Policy says that we collect no consumer health data.
We collect as little as we can. The rest of this notice follows the information: what we collect, why we use it, who receives it, how long we keep it, and what you can do about it.
What stays on your phone
Most of what the app knows about you never leaves your phone. It is stored in the app's own storage, mostly its local database. We never receive the people you cook for, their allergies, diets or dislikes, your pantry or your ratings and notes. A few items below can travel when you use a feature, and they are marked:
- The people you cook for, you included: the name typed for them, age band, portion size, whether they eat from a separate plate, an optional goal, and their allergies with severity, intolerances (lactose included), diets and disliked ingredients. Some of these people may be children. While you set the app up, the diets step and the allergies step each tell you that this stays on your phone. Only the number of people you cook for can leave, with a "Write me a recipe" request.
- Your profile and settings (the app's language goes with AI requests and reports); your kitchen equipment and staples; your pantry, shopping list, calendar (a dish name you typed onto it goes with the AI features that use it) and week plans, and your cooking history; your Cookbook and the recipes you saved to it; your ratings with their notes. Ratings are not added up across users.
- Your badges and a short log of the actions they count, by day and never by time, never with what you typed or shared.
- A recipe the app wrote for a dish you typed, for seven days.
- Your sign-in session, if you are signed in. Its access token is not private from us: it goes to our server when the app asks for a Premium ticket or when you delete your account, and to our sign-in service when the session renews.
- Your reminder settings and what is prepared for reminders and widgets; your answers to the app's permission questions, with their dates; the dish pictures the app has downloaded, up to about 80 MB; a small record that keeps the app's occasional Premium suggestions rare; and, while usage statistics are on, the random ID the statistics library created.
Reminders and widgets are made on your phone from this data. Nothing is sent to make them, and there is no push service behind them. Anyone who can see your screen can see them, so they never name an allergy, a diet, an intolerance or the person who declared it. The same goes for the reminder two days before a free trial that will renew ends: a card in Settings and, only if you have turned reminders on, a notification, each giving the day the trial ends and the price that will then apply. The email notices described under "Premium, payments and subscription emails" do not depend on this setting.
Sharing. The share button hands a plain-text recipe or menu, or a photo of a dish you cooked, to your phone's share sheet. Where it goes is your choice; we are not involved and see nothing of it. The photo comes from your phone's own picker, is reduced in size, is never uploaded, and may carry whatever your phone stored in the file, such as when and where it was taken. The app never asks for your location.
Device backups. Your phone may include this app's data in its normal backup to your own Google or Apple account, and in a transfer to a new phone. Your phone makes that backup; we receive nothing from it and cannot read it. This means the backup may hold the allergies, diets and other health-related or belief-related information you entered, in your own account with Google or Apple. You can turn the backup off in your phone's settings.
You can change or delete most of this in the app. Deleting your account deletes the app's data from the phone you delete it on, with three exceptions: the small record that keeps the Premium suggestions rare is trimmed, not deleted; the membership library keeps its own on-device cache of your plan; and on iPhone, Google's own sign-in session in the keychain can outlast uninstalling the app. Uninstalling the app deletes what it keeps in its own storage.
The information we collect
Without an account. Nothing about you is sent to us, with two exceptions that need no account: the app downloads dish pictures from our server, and you can send a report about a recipe. If you allow usage statistics, those go to PostHog.
Technical data every connection shows. Every request to our server shows it your IP address and technical headers, such as the version of the software making it. Cloudflare, which runs our server, keeps a record of each request — the time, the address requested, the response status, your IP address, the request's technical headers and the approximate location Cloudflare works out from the IP address (country, region, city, postal code and coordinates) — for up to seven days. Cloudflare blanks out the headers whose names suggest a credential, such as Authorization and Cookie; the short-lived Premium pass the app sends with an AI request is not blanked, so the record can include it. The pass names no account and expires within an hour. It also carries the sealed code described under "The AI features and your permission". The record is kept to deliver the request and to find faults and attacks. It does not include the body of a request. Our server's own log lines hold counts and error codes only, never an IP address, an account, a dish name you typed or anything the AI wrote. To stop abuse, our server also keeps short-lived counts of requests per address in memory; it does not store the address for this. Separately, it stores how many AI requests each account sends in a month, for Premium's monthly limit (see "The AI features and your permission").
Dish pictures. The pictures of the catalogue's dishes are not inside the app. The app downloads the pictures of the dishes it suggests, and any picture it does not have when it shows a dish. The request names only the picture, which is the name of the catalogue dish, and carries no account and nothing else about you or your household. But the dishes it names are the ones the app suggested for your household, so the pictures requested from one address can show that some foods were left out. They don't say which foods, for whom or why. Cloudflare keeps the address and the picture's name for up to seven days, and we use them only for faults and attacks. Because each downloaded file is named after its dish, the pictures stored on your phone show which dishes the app has displayed.
Your account (only if you sign in). You sign in with Google or Apple. We have no password of our own and never see yours. From Google we receive your name, email address, the address of your profile picture, your Google account ID and, for a Google Workspace account, its domain. From Apple we receive your email address (a relay address if you chose "Hide My Email") and your Apple account ID. On iPhone the app asks Apple for your name too, but passes on only Apple's sign-in token, so we neither receive nor store that name. On Android, Apple signs you in through your browser and may share your name; if it does, our sign-in service stores it. Our sign-in service, run by Supabase in Frankfurt, keeps these, the times you signed in, and your sessions — with the IP address and the app's user agent — until you sign out (when your phone can reach the sign-in service), they expire, or you delete your account. Supabase also records each sign-in request, each renewal of your session and each sign-in event — with the IP address, account ID, email address, name and the device's software version — in its own log storage (see "How long we keep things"). Our own account record is an internal number linked to your sign-in; it holds no email address and no name.
On your phone, the sign-in library keeps your session in the app's own storage. On iPhone, Google's own sign-in library also keeps its session for a Google account in the phone's keychain, which can outlast uninstalling the app; the app signs it out when you sign out and disconnects it when you delete your account. Signing out keeps the app's data on the phone. If a different account signs in on the same phone, the app warns you first and, to continue, deletes the previous account's data from the phone, so that two people's data never mix.
Your subscription (only if you subscribe). The store's records of your purchases, held by RevenueCat under your account's ID: the product, price and currency, the store's country, purchase, renewal and expiry dates, and whether you are in a trial or have cancelled; plus the technical details any request carries, such as your IP address, phone model, operating system and the app's version. The app gives RevenueCat no name, email address, allergy, diet or other detail about you. In our database we keep, under your account's ID, a record of the subscription and of the notices we owe you. For each charge we also keep a minimal purchase record (see "Premium, payments and subscription emails").
AI requests, reports and usage statistics are described in their own sections below. Emails you send us: what you write, and the address you write from.
We do not collect precise location from your phone, government IDs, biometric data, payment card details (the store takes payment), your contacts or photo library, or advertising identifiers. The dish pictures were made with AI before the app was released; no information about you went to the companies that made them.
Why we use it
- To provide the app. To show dish pictures, run your account, confirm Premium, and — when you ask — write a menu, a cooking plan or a recipe.
- To send the subscription notices the law requires and to answer you when you write to us. We send no marketing and no newsletter, and no email about changes to this notice or the Terms of Use.
- To keep the service working and safe. To find faults and attacks, to stop a script from running up the cost of the AI features or flooding us with reports, and to hold each account to the monthly limit on AI requests in our Terms of Use.
- To understand how the app is used, only if you allow usage statistics, and to see how the subscription is doing: how many trials turn into paid memberships, how many renew and how many are cancelled. We look at those as totals over all members, not at what one person bought.
- To correct recipes, from the reports you choose to send, and to decide which dishes to add, from the count of dish names we had no recipe for.
- To meet legal duties, including keeping a minimal record that you agreed to an automatically renewing subscription, and to answer requests from authorities.
We do not use personal information for advertising, to profile you, or to make decisions about you with a legal or similar effect. We do not use personal information to train or fine-tune any model, large language models included, and Google does not use what we send to its Gemini API to train its models.
Who receives it, and where
These companies process information on our behalf and on our instructions, under each provider's data-processing terms:
- Cloudflare, Inc. (United States) runs our server on its global network, in whichever of its data centres receives your request; stores the dish pictures; and keeps the records of requests described above.
- Supabase Pte. Ltd. (Singapore), with its affiliates and sub-processors, runs our sign-in service and our database, which is in Frankfurt, Germany. The database holds account records, the sign-in service's records, the subscription records and their notice rows, the codes in the links that stop the yearly reminder, the minimal purchase records, the monthly counts of AI requests, the dish-name counts, reports, and the answers about why an account was deleted.
- Google (the Gemini API) processes the AI requests, in any country where it or its sub-processors have facilities.
- RevenueCat, Inc. (United States) checks Premium subscriptions and processes the data in the United States.
- Resend, Inc. (United States) sends the subscription emails on our behalf. It receives your account's email address and the text of each notice.
- PostHog, Inc. (United States) processes the usage statistics, if you allow them, in its EU cloud in Frankfurt, Germany.
Outside the app. support@pinjula.com is a mailbox hosted by Porkbun, where our domain is registered; email you send to it is kept there. The website that publishes this notice, pinjula.com, is hosted on GitHub Pages; GitHub receives the IP address of every visitor.
Apple and Google as app stores and sign-in act under their own privacy policies, not as our service providers. This includes Apple when our server asks it to revoke the app's sign-in tokens after you delete your account. On iPhone the app also contains Google's sign-in library; what it collects goes to Google under Google's own policy, not to us.
We do not sell your information, we do not share it for targeted advertising, and we have no affiliates to give it to. We may disclose information to authorities where the law requires it, and to a successor if the service is transferred to one, which would be bound by this notice.
Where your information is processed. Your account and our database are in Frankfurt, Germany. Our service providers process information in the United States, Germany, Singapore and wherever Google or its sub-processors operate, and we reach the database from Türkiye. Your information may therefore be stored and processed outside your state, province and country, and the courts, law-enforcement and national-security authorities of those countries may be able to access it under their laws. No law of the United States or Canada that applies to us requires your information to stay in your country. Before we use a service provider outside Canada, we assess the risks.
The AI features and your permission
Premium has three features that use AI: a menu that mixes cuisines ("Mix them into one menu"), a plan for cooking a whole menu ("How to prepare this menu") and a recipe for a dish you typed ("Write me a recipe"). Each starts only when you use it, never in the background. Each sends a request to our server, which passes it to Google's Gemini API and returns the answer. Each needs an account and Premium.
What each one sends.
- Mix them into one menu: the dishes your phone has already picked as candidates — their catalogue code, cuisine, name, role, courses and hands-on time — with the app's language, the cuisines you chose, how many menus you want, the courses you asked for and your time limit.
- How to prepare this menu: each dish in the menu — its name, role, the names of its ingredients and its steps — and the app's language. For a dish you typed onto your calendar, that is the name you typed and the recipe the app wrote for it.
- Write me a recipe: the name you typed, the app's language and how many people you are cooking for. Before offering this, the app checks on your phone that the name looks like a dish name; if it doesn't, nothing is sent.
Your allergies, diets and pantry, and who is in your household, are never sent (only how many people you are cooking for, with a typed dish). But the dishes sent to plan how to cook a menu were chosen from suggestions your phone made with your household's filters, so they can show that your household leaves some foods out. They don't say which foods, for whom or why. Because they go to Google's Gemini, the app asks you first. The dishes sent to mix cuisines are chosen differently: your phone picks them from what your kitchen can make — your equipment, the season, the dishes you have not cooked in the last seven days and, if you asked for what you have, your pantry — without anybody's allergies, diets, lactose or disliked ingredients, and checks the menus that come back against those on your phone. A menu with a dish someone in your household does not eat is left out whole; when none is left, the menus keep to one cuisine each and the app says so.
Your permission comes first, on its own screen. The first time you reach for one of the three features, the app asks one question, "Allow AI features?", on a screen of its own. It comes before the Premium offer screen and before any sign-in, so the permission is never part of a purchase. It says what each feature sends, that it goes through our server to Google's Gemini, that the dishes sent to plan how to cook a menu can show that your household leaves some foods out — not which, for whom or why — and that the dishes sent to mix cuisines are chosen without your household's allergies, diets or dislikes. You choose "Allow" or "Not now".
- "Not now" sends nothing and opens neither the Premium offer screen nor a sign-in. The rest of the app keeps working: menus stay within one cuisine, each dish keeps its own recipe, and a dish you typed stays on your calendar under its name.
- One permission covers all three features. The app keeps your answer on your phone, with its date and the version of the question's words. If the words change in what they say, the app asks again the next time you reach for a feature.
- You can withdraw it at any time in Settings → Privacy & security → AI features. The three features then stop until you allow them again.
- A Premium offer screen you reach any other way asks nothing about AI; it says that some Premium features use Google's Gemini and ask your permission before you first use them.
The permission is never asked when the app starts or while you set it up. Before anything is sent, the app checks that you have Premium, and our server checks it too, with a short-lived ticket that names no account and expires within an hour. The ticket also carries, sealed so that only our server can read it, a code our server works out from your account and the month; our server counts your requests under that code (below).
What we keep: a dish name, and a monthly count. Our server keeps nothing of the requests or the answers, with two exceptions. When you ask for a recipe for a dish our catalogue doesn't have, we count the name, so that if many people ask for the same dish we know to add it properly. We store the name in a simplified form, how it was most recently spelled, a running count, the languages it was asked in, and the date and time it was first and last asked for. Nothing else: no account, no device, no address. For a name only one person has ever asked for, those times are when that person asked. These counts are kept with no end date. The recipe written for you stays on your phone for a week, so it doesn't change while you are cooking it, and reaches our server only if you report a problem with it.
How many AI requests your account sent this month. Premium includes up to 150 AI requests a calendar month, counted in Coordinated Universal Time (UTC), the three features together; our Terms of Use say what counts as a request. To hold to it, our server keeps, for each account that used the features, one number a month: how many requests went to Google's Gemini, less those given back because Gemini gave no answer or returned an error. The number is stored under the code in the ticket — not with your account ID, your email address or anything you sent, and with no times, features or dish names — and the code changes every month. Whoever holds our server's secret key can work out which account a code belongs to, which is how we delete the count with your account, so we treat the count as information about your account, not as anonymous. We keep each month's count until the end of the following month. When the month's requests are used, our server turns the AI requests down until they renew, without counting them, and the app says so, with the date.
What Google does with these requests. We use Gemini as a paid service. Under Google's terms for it, Google doesn't use what we send or what it returns to improve its products or to train its models, and it processes them on our behalf under its data processing terms. Google keeps requests and answers for up to 55 days solely to detect and prevent abuse of its service, and during that time authorized Google staff may review them for that purpose. We cannot match those records to you, so we cannot find or delete them on request; they expire on their own.
A failure never costs you a recipe: the app falls back to a menu built on the phone, to each dish's own recipe, or to the dish on your calendar under the name you typed. We make no decision about you with a legal or similar effect by automated means.
Premium, payments and subscription emails
What it is. Premium is an optional subscription: an Individual plan, billed monthly or yearly through the App Store or Google Play, which take the payment. In Canada only the monthly plan is sold. It may start with a one-week free trial, after which the first payment is taken unless you cancel, and it renews automatically until you cancel it. It adds the three AI features, nutrition values and goals, the keto and high-protein filters, home-screen widgets, and planning beyond today and the next two days. The store takes the payment; we never see your card or payment details. Our Terms of Use describe the subscription itself.
RevenueCat checks it for us. RevenueCat, Inc. is our service provider for subscriptions. Its library does not run until you have signed in, and does not start while your store's age signal says you are under 18. Once you are signed in it asks RevenueCat which plan you are on, whether or not you have ever bought anything, under your account's ID and no other ID; so RevenueCat holds a record for every signed-in account. The app has switched off the library's collection of advertising and attribution identifiers. On iPhone the library still sends Apple's identifier for this app on this phone with each request. Nothing from these records is sent to an advertising network. Restoring purchases needs you to be signed in. When you press the buy button on the Premium screen, the app also gives RevenueCat one label for that purchase: the version of the offer screen you are buying from, its language, the day and the plan (monthly or yearly), so that our purchase record can show what you agreed to. The app takes the label off again if you close the store's window without buying or the purchase fails.
The subscription emails we send. The law in some places requires the seller of an automatically renewing subscription to remind you or to give you notices, and the stores' own emails may not carry our name or our terms. So when RevenueCat tells our server that a subscription has started or restarted, our server sends an email from notices@pinjula.com to your account's email address, through Resend. The emails are:
- A purchase confirmation, after you start or restart a subscription, with the plan, the price, how to cancel, a link to our Terms of Use and our seller details. In Canada it is the copy of the contract that the law asks for within 15 days.
- A renewal notice for a yearly plan, about 40 days before each renewal.
- A yearly reminder for every other subscription, once a year on the anniversary of the first purchase.
- A notice before a free trial ends, for subscribers in Canada, about four days before the trial ends, giving the date it ends, the price that will then apply and how to cancel.
Emails to subscribers in Canada are in French first, then English. They are factual and carry no offer. In Canada, the yearly reminder and the notice before a free trial ends carry a link to stop the yearly reminder: open it and confirm, and the yearly reminders still to come for your account stop. The notices the law asks us to send are still sent — the notice before a free trial ends, a renewal notice and every purchase confirmation — and the emails to subscribers in the United States carry no such link, because each is a notice the law requires or a message about your subscription. A cancellation sends no email; it cancels the notices still waiting.
What we store to send them. No email address is stored for this. When an email is due, our server reads your address from the sign-in service for that one send and passes it to Resend. We keep, linked to your account's ID, a record of the subscription (the store, product, plan period, trial status, country and currency, price, key dates and whether it renews) and a row for each notice (its kind, when it is due, whether it was sent); and, once a reminder email has been prepared for a subscriber in Canada, the random code its link to stop the yearly reminder carries and, if you used the link, the day you did (never the time). Deleting your account deletes all of these at once. Resend keeps the emails it sends for us under its own terms and does not use them for any other purpose.
A minimal purchase record. For each charge a store reports for Premium, our database keeps one row: the store and its transaction number, the product, the day of the charge (not the time), the price and currency, and — when you bought from Pinjula's Premium screen — that screen's version and language and the day you pressed its buy button. The row holds no name, no email address, no account ID and no sign-in, and we do not join it to anything. We keep it for three years from each charge, even after you delete your account, so that we can show you agreed to the subscription. Test purchases are not recorded. A purchase made in the store's own settings or with an offer code, a change of plan made there, and charges after you delete your account or move the subscription to another account are recorded without the Premium screen, or not at all; for those, the stores' own records show what was bought.
Premium never changes how your safety settings work. Allergen filtering, lactose avoidance and the vegetarian, vegan, pescatarian, halal and kosher filters work without Premium and without an account, and nothing about them is sent to RevenueCat.
Cancelling, and deleting your account. Deleting your Pinjula account does not cancel the subscription: the store bills it until you cancel it in your App Store or Google Play account ("Manage subscription" in Settings opens it). When you delete your account, our server also asks RevenueCat to delete the record it holds under your account's ID.
Usage statistics
The app can count how it is used so that we know how many people use it each month and can decide what to improve. A library from PostHog, Inc. does the counting in the app and sends the counts to PostHog's EU cloud in Frankfurt, Germany.
Off until you say yes — everywhere. Nothing is counted and nothing is sent, and the library is not started, until you choose "Allow". The app asks once, after you finish setting up, with the choices "Allow" and "No thanks". Saying no costs you nothing: no feature, and not Premium, depends on your answer. You can change your mind at any time in Settings → Privacy & security → Usage statistics.
What is counted, and what never is. Each count is an event with a name and a few values chosen from fixed lists in the app, such as: the app was opened; a screen was viewed; suggestions were requested (the kind of request, how many came back, the cuisine asked for); a menu was opened; a dish was marked as cooked; the calendar, shopping list or pantry was used; a home-screen widget was added; something was shared; a report was sent; an AI feature was used and whether it answered; the Premium screen was shown; one of the occasional Premium suggestions was shown or closed; and a purchase was started, completed or cancelled. Every event also carries the app's version, the platform, the app's language and region, your residence country (only United States or Canada) and whether you have Premium. Never: anything about your health or diet — your allergies, intolerances, diets or disliked ingredients, or any filter built from them (the cuisine you asked for and the kind of request are counted); the people you cook for; a dish name or any other text you typed; which recipe, pantry item or shopping item; notes and ratings; your account ID or email address. The app never tells PostHog who you are, and no person profile is created.
An ID for the phone, not for you. PostHog's library creates a random ID on your phone and a device ID derived from it. Neither is linked to your account. A random ID is not anonymous: it lets the counts from one phone be recognised as coming from the same phone, and this notice does not call the statistics anonymous. The library also adds technical details about the phone to each event, such as its model, operating system and time zone. PostHog receives your phone's IP address with each request, as every server does, but our project is set to discard it, and each event also asks PostHog not to work out a location from it.
Turning them off deletes everything the library kept on your phone, including its IDs; if you switch them on again, it starts with new IDs, so what was sent before cannot be joined to what is sent after. Nothing in the statistics is used for advertising, sold or given to anybody else.
Reports about a recipe
Only when you send one. At the foot of every recipe — ours, and the ones the app writes for a dish you typed — "Report a problem with this recipe" lets you tell us what is wrong. You pick a reason and can add a note of up to 500 characters. Nothing is sent until you tap "Send report", and a report that could not be sent is not saved or sent later on its own. Reporting does not need Premium, an account or the permission for the AI features.
What is sent and kept. For a recipe from our catalogue: its catalogue code, the reason, your note and the app's language — not the recipe, which we already have. For a recipe the app wrote for a dish you typed, its title, ingredients and steps go with the report, because that recipe exists only on your phone; the report screen says so before you send. Never your account, your household, your allergies or your profile. We keep the report, with the day it was sent (not the time of day), for 12 months, then delete it. Nothing about who sent it is stored with it: no account, no device ID, no IP address, and nothing is sent back to your phone that could find it again. To stop abuse, our server refuses more than ten reports a day from one internet address or home network; it counts them under a keyed code that changes every day, which we do not turn back into the address and never store with a report, and deletes each day's counts shortly after the day ends.
Please keep personal details out of the note. We cannot reply to a report, and a name or an email address written into the note would be kept for the 12 months like the rest. If you want an answer, write to support@pinjula.com. To have a report you sent deleted sooner, write to us with enough to find it — the recipe, the day and the words of your note — and we will delete it. We read reports to correct the catalogue and the way the app writes recipes; a report is not a promise that anything will change.
Why you deleted your account (if you tell us)
Only when you send it. Once your account has been deleted, the app asks — optionally — why you left. You can pick any of eight reasons and add a note of up to 500 characters. Nothing is sent unless you tap "Send", and an answer that could not be sent is not saved or sent later on its own. "OK" closes the page and sends nothing.
What is sent and kept. The reasons you picked, your note, the app's language and whether the phone is an iPhone or an Android phone — never your account (it no longer exists), your household, your allergies or your profile. We keep it, with the day it arrived (not the time of day), for 12 months, then delete it. Nothing about who sent it is stored with it: no account, no device ID, no IP address, and nothing is sent back to your phone that could find it again. As with reports about a recipe, our server refuses more than three answers a day from one internet address or home network, counted under a keyed code that changes every day and is deleted shortly after the day ends. Cloudflare's record of each request, kept for up to seven days ("How long we keep things"), shows this request and your deletion request coming from the same address a few moments apart; we do not use it to connect them.
Please keep personal details out of the note. We cannot reply, and a name or an email address written into it would be kept for the 12 months like the rest. We read the answers to improve the app; an answer is not a promise that anything will change.
How long we keep things
- On your phone: until you delete it, delete your account, or uninstall the app. A recipe the app wrote for a dish you typed: seven days. Downloaded dish pictures: up to about 80 MB, the least recently used deleted first. The text and pictures for reminders and widgets: replaced whenever your data changes. The record that keeps the Premium suggestions rare: until you uninstall the app (deleting your account trims it but keeps it).
- Your account record and sign-in: until you delete your account. Your sessions are kept until you sign out (when your phone can reach the sign-in service), they expire, or you delete your account.
- The subscription record, the notice rows and the code in the link that stops the yearly reminder: while the subscription is active and 12 months after it ends, and at once when you delete your account.
- The minimal purchase record: three years from each charge, even after you delete your account.
- Premium records at RevenueCat: while your account exists; when you delete it, we ask RevenueCat to delete them.
- Dish names counted for "Write me a recipe": no end date, never linked to an account or a device.
- The monthly count of your AI requests: until the end of the month after the one it counts, then deleted; when you delete your account, as the deletion finishes, and at the latest at the end of the following month.
- Reports about a recipe: 12 months from the day they were sent, then deleted.
- Why you deleted your account, if you told us: 12 months from the day it was sent, then deleted.
- Usage statistics: on your phone, until you turn statistics off. At PostHog: one year from the event, then deleted.
- Logs: Cloudflare's record of each request and our server's own log lines, at most seven days each; Google's records of the AI requests, up to 55 days; and Supabase, which runs our sign-in service, records each sign-in request, each renewal of your session and each sign-in event — with the IP address, account ID, email address, name and the device's software version — in its own log storage, under its own retention, which we do not set: when we checked on 29 October 2026, its records for our project went back to the day the project was created, 51 days earlier, so we have not yet seen it delete any. On 7 December 2026, when the oldest of them are 90 days old, and on the first day of every month after that, we check again and ask Supabase to delete any that are older than 90 days. We keep no separate log of sign-in events in our database.
- Backups of our database: Supabase currently makes a backup of our database every day and keeps up to seven of them, so something deleted from the database remains in a backup for up to seven days. On our current plan we cannot open or restore these backups ourselves, and Supabase may stop making them. If our project were ever paused for inactivity, Supabase would keep a copy of the database as it stood at that moment so that it could be restored; Supabase does not say how long it keeps that copy.
- Emails you send us: 12 months after the last message in the conversation, then deleted.
- Records of requests under your rights, and our answers: three years, so that we can show we answered.
- The store's age signal: held in the phone's memory only while the app checks it, and never stored.
- A register of confidentiality incidents: five years (Québec); a record of every breach of security safeguards, 24 months (federal Canada).
Your choices and rights
Wherever you live, you can ask us for a copy of your information, ask us to correct or delete it, and withdraw any consent at any time. The supplements for the United States and Canada say more for each place, including whom you can complain to.
Two ways to ask.
- In the app. Settings → Account has "Export my data" and "Delete account"; "Delete account" is also the last row of Settings → Privacy & security. The permissions for the AI features and for usage statistics are each withdrawn in Settings → Privacy & security, and reminders and widgets under "Reminders and widgets" in Settings. Because the people you cook for and their declarations are on your phone only, you change or delete them on your phone.
- By email. Write to support@pinjula.com, from the email address you sign in with if you have an account. We verify a request by replying to that address; without an account, tell us enough to find what you ask about. Someone you authorise in writing may make a request for you. Requests are free, and we do not treat you differently for making one.
How long we take. We answer within 45 days in the United States, which we may extend once by 45 days, telling you why, and within 30 days in Canada.
Your copy of your data. "Export my data" builds a file on your phone and hands it to your phone's share sheet; we don't build it on our server or keep a copy. It contains your account's email address, if you are signed in; your profile; the date you allowed the AI features; the people you cook for with what was declared for them and their goals; your equipment and staples; your cooking history; the recipes you saved to your Cookbook; your pantry; your shopping list; your calendar and week plans; the dishes you marked as cooked; your badges; your reminder settings; and your ratings. It does not contain a recipe the app wrote for a dish you typed, your sign-in session or your answer about usage statistics. Because the people you cook for can include children, the file contains what was entered for them; treat it with care. For what we hold on our server — your account's email address and provider ID; the name, the address of your profile picture and the work domain, if your provider sent them; your sessions, with the IP address and the app's user agent they were made from; your subscription record and its notice rows; and, in Canada, the code in the link that stops the yearly reminder — write to support@pinjula.com and we will send it to you in a structured, commonly used format.
Usage statistics and Premium records. Usage statistics are not linked to a name or an email address, so we cannot find them by either; switching them off stops them and deletes their IDs from your phone. Premium records at RevenueCat are held under your account's ID; write to support@pinjula.com to ask about them.
Deleting your account
If you never signed in, we hold no account for you; uninstalling the app deletes everything it stores on your phone.
In the app. Settings → Account → Delete account, or Settings → Privacy & security → Delete account. The app tells you that billing for a Premium subscription continues through the store until you cancel it there and that our subscription emails stop, and links to where you can cancel; it then shows what will be deleted and asks you to confirm twice, the second time by typing a word. The page pinjula.com/delete-account/ describes the same steps, and the same request can be made by email to support@pinjula.com.
What is deleted.
- At once, on your phone: the app's data — everyone's declarations, your ratings, your widgets and reminders, the usage-statistics IDs, the downloaded dish pictures and the copies the photo picker left in the app's cache. You are signed out, and the app tries to disconnect from Google's sign-in library. Another phone where you used the app keeps its data until the app is uninstalled there.
- At once, on our servers: your account record, your subscription record and its notice rows. Your sign-in, with your email address, name, provider ID and sessions, the record RevenueCat holds under your account's ID, and the count of your AI requests for this month and the last are normally deleted within minutes; we ask RevenueCat to delete its record again at intervals for up to seven days, in case a phone still running the app re-created it. If a step fails we keep retrying, except for the count of your AI requests: we try once to delete it, as the deletion finishes, and if that fails it is deleted at the end of the following month.
Sign in with Apple. On iPhone, if your account uses Sign in with Apple, the app asks Apple to confirm once more after you have confirmed the deletion, and our server uses the one-time code Apple gives to ask Apple to revoke the app's Sign in with Apple tokens, which removes Pinjula from the apps connected to your Apple Account. Your account is deleted all the same when the revocation does not go through — for example if you cancel Apple's prompt. It is not possible on Android or by email, where Apple gives the app no such code. In those cases Pinjula stays connected to your Apple Account until you remove it yourself under Sign in with Apple in your Apple Account settings.
What stays: the minimal purchase record of each charge, for three years from the charge, with no name, email address or account ID; the count of your AI requests, until the end of the following month, if deleting it with your account failed or another of your phones added to it in the hour after the deletion with a ticket it already held; dish names and reports, which were never linked to you; usage statistics, which are not linked to your account; Cloudflare's record of each request and our server's own log lines, for at most seven days; Supabase's own logs of sign-in requests and events, with your email address, until Supabase deletes them (see "How long we keep things" for what we do about them); Google's records of AI requests, for up to 55 days, which we cannot match to you; our database's backups (see "How long we keep things"); the stores' own records of your purchases, which Apple and Google keep under their policies; and your device's backup, in your own Google or Apple account, which we cannot reach; and, on your phone, the items listed under "What stays on your phone" (the Premium-suggestions record, the membership library's cache, and on iPhone Google's keychain session).
What deleting your account does not do. It doesn't cancel a Premium subscription: cancel it in your App Store or Google Play account, or the store keeps renewing it. After you delete your account we can no longer email you the renewal reminders and notices described above, because we no longer hold your email address; your store sends its own notices. On iPhone the disconnect from Google's sign-in library removes Pinjula from your Google Account's third-party connections. On Android, and when you delete by email, Pinjula may stay in those connections until you remove it there by hand.
If you can't use the app, email support@pinjula.com from, or naming, the email address of the account you signed in with — for "Hide My Email", the relay address. We confirm with that address, then delete the account, within 30 days at the latest.
Children and age
You must be 18 or older to use Pinjula, and the app is not directed at children. The app reads the age signal your phone's store provides (Apple's Declared Age Range, Google Play's Age Signals) and, if it says you are under 18, shows a message that Pinjula is for adults and lets you no further: no account, no purchase, and no use of the app. If you already had an account, that message links to our deletion page and to support@pinjula.com so that you can have it deleted. If your phone gives the app no age signal, nothing is blocked. We use the signal only for this, keep it in memory only while the app checks it, and never store it. We do not otherwise ask your age, and we do not knowingly let anyone under 18 have an account. If you think someone under 18 has an account, tell us at support@pinjula.com and we will delete it.
An adult can add a child to the list of people they cook for — that is what the age bands and portion sizes are for. That entry, with anything recorded for the child, stays on the adult's phone and is never sent to us. We hold nothing about children, and we do not knowingly collect personal information from anyone under 18.
Ingredients you avoid, and sensitive information
For each person you cook for, you can record what they avoid: allergies (with how serious), intolerances such as lactose, diets (halal and kosher among them) and ingredients they dislike. We don't ask why. Some entries may reflect an allergy, a health condition or a belief, so we treat the whole list as sensitive: it stays on your phone and we never receive it. It is never sent to Google, to RevenueCat or with the usage statistics, and reminders and widgets never show it.
Dishes that leave your phone. Dish pictures and the dishes sent to plan how to cook a menu are named from suggestions your phone made with your household's filters, so they can show that some foods were left out. They never say which foods, for whom or why. The menu plan goes to Google's Gemini, so the app asks you first. The dishes sent to mix cuisines in one menu are not chosen with your household's allergies, diets, lactose or dislikes, so they do not reflect them; your phone checks the menus that come back against those. The AI-features question says so in plain words before you agree, and you can withdraw that consent at any time (see "The AI features and your permission"). We never use sensitive information for advertising, to profile you, or to train any model, and we do not sell it.
While you set it up. The diets step and the allergies step of setting up each tell you that what you choose stays on your phone and is never sent to us, and that your phone's own backup to your Google or Apple account may include it.
Not medical or nutritional advice
Where the app shows nutrition figures, they are estimates calculated from published food-composition databases (USDA FoodData Central and, for some ingredients, the Australian Food Composition Database by Food Standards Australia New Zealand) applied to a recipe's ingredients — not an analysis of the food you cook, and never medical or dietary advice. Allergen filtering is a best-effort aid, not a guarantee: recipes containing your listed allergens are filtered out, which does not make any recipe safe or free from an allergen. Always check the full ingredient list and the label of every product yourself before cooking, especially if anyone at the table has a food allergy. A recipe the app wrote for a dish you typed carries no allergen, diet or nutrition information at all. The app is not a medical device and does not diagnose, treat, cure or prevent any medical condition; for medical advice, consult a healthcare professional. In an emergency, call 911 or your local emergency number.
Changes to this notice
When we change this notice, we update the effective date at the top. We make a material change only for a reason that applies to the service: a change in the law, in the features we offer, in the services we rely on, or in how the App Store or Google Play sell subscriptions. We publish the new text on pinjula.com, and the app shows a card the first time you open it after an update that carries a newer effective date ("Our privacy policy has changed", with a "Read it" button); the card appears once for each new date. We do not send an email about a change to this notice. The notice shown in the app (under "About this app") is a copy that comes with each release of the app, so a new version of it reaches your phone when you update the app. Before a significant change to this notice or to the Terms of Use, we also tell Apple and Google, as their rules and Texas law require.
Languages
This notice is published in English, French, Spanish, German, Italian and Turkish, every language the app is offered in. The English text is the original; where a translation differs from it, the English text prevails. For residents of Québec, however, the French version is the version you accept unless, after receiving it, you expressly choose the English version.
Contact
Questions about this notice or your information: support@pinjula.com.