Privacy policy
Last updated: 4 November 2026 · Wersja polska
This policy explains how ReciQuick handles personal data when you use the ReciQuick app for iPhone, its Apple Watch app and Share extension (together, “the app”), and the website at quickrecipe.app (“the website”). We wrote it to be read, so it is short where it can be and specific where it matters.
1. Who we are
ReciQuick is run by [legal entity name], [registered address], [company number, if any] (“we”, “us”). We are the controller of the personal data described here.
Contact us about privacy at hello@quickrecipe.app. [If the controller is in the UK and has users in the EU, or the other way round, name the Article 27 representative here.]
2. What we collect
Information you give us
- Account details. The app creates an account for you automatically. If you link one, we also hold your email address or your Sign in with Apple identifier. Apple may give us a private relay address instead of your real email.
- Onboarding answers. Your goals, how much time you have to cook, how you heard about us, your units and appearance settings, and whether you want reminders.
- Diet and allergy choices. For example gluten, milk, nuts, vegetarian, or vegan. See section 4.
- Your recipes and kitchen. Recipes you import, write, or edit; cookbooks; meal plans; grocery lists; fridge and pantry items, including prices from receipts; notes, star ratings, and when you last cooked something.
- Links, photos, and receipts. The links you share to the app, and photos of recipes, fridge shelves, products, or receipts you choose to upload.
- AI Chef conversations. What you type or photograph in AI Chef, and its replies.
- Shared cookbooks. Which cookbooks you share or join, and the recipes and photos added to them.
- Messages to us. Anything you send when you contact support.
Information collected automatically
- Usage counters. How many imports and AI requests your account makes, and when. We need these for free-plan limits and fair use.
- Device and app details. App version, iOS version, device model, language, and a device integrity check from Apple App Attest that tells us requests come from a genuine copy of the app.
- Server logs. Technical records of requests to our servers, such as time, account ID, and error details.
- Advertising identifier. Only if you allow tracking. See section 7.
Information from others
- Apple and RevenueCat tell us whether you have an active ReciQuick Plus subscription, including through Family Sharing. We never see your card details.
- Appstack tells us which ad campaign, if any, led to your install.
- Public posts you import. When you import from TikTok, Instagram, YouTube, Facebook, or a website, we read the public post or page, including the creator’s public name and profile.
- Other ReciQuick users who invite you to a shared cookbook.
3. How we use it and why
The law requires us to give a legal reason (a “lawful basis”) for each use.
| What we do | Lawful basis |
|---|---|
| Run the app: save and sync your recipes, import links and photos, plan meals, build grocery lists, keep your fridge, share cookbooks | Contract: we need it to provide the service you asked for |
| Provide ReciQuick Plus and check your subscription | Contract |
| Flag recipes that may clash with your diet or allergies, and suggest swaps | Your explicit consent (see section 4) |
| Send cooking reminders on your iPhone | Consent, given through the iOS notification prompt |
| Enforce free-plan limits and fair use, prevent fraud and abuse, and keep the service secure | Legitimate interests: protecting the service, our costs, and other users |
| Fix bugs and improve imports, for example by looking at a link that failed to import | Legitimate interests: making the app work better |
| Measure which ads brought you to the app using your advertising identifier and email | Consent, given through the iOS tracking prompt |
| Understand installs and purchases at an aggregate level without your advertising identifier | Legitimate interests: knowing which marketing works [confirm with your adviser; this may need consent] |
| Answer support requests and handle complaints or appeals | Contract and legitimate interests |
| Keep records we must keep and respond to lawful requests | Legal obligation |
We do not sell your personal data, and we do not use your recipes, photos, or chats to train AI models.
4. Diet and allergy choices
Allergies and some diets can reveal information about your health, which the law treats as special category data. We only collect these choices if you pick them, and we use them only to flag recipes that may conflict and to suggest swaps. When you look up swaps, we send your choices and the recipe’s ingredients to OpenAI to generate them.
You can change or clear these choices at any time in Settings. Clearing them withdraws your consent; it does not affect anything we did before.
These warnings are a reminder, not a medical check. They cannot see brands, labels, or cross-contamination.
5. AI features
ReciQuick uses AI models from OpenAI for: reading recipes from links, captions, and photos; listening to the audio of recipe videos when the ingredients are only spoken; AI Chef; estimating nutrition; suggesting diet swaps; reading receipts and fridge photos; matching products; and translating recipes into your app language.
For these features we send OpenAI only what the request needs, such as the recipe text, the photo you took, the video’s audio, or your AI Chef message. OpenAI processes it for us under a data processing agreement, may keep it for up to 30 days to detect abuse, and does not use it to train its models.
AI output can be wrong. Check ingredients, quantities, cooking times, and allergens yourself. AI never makes decisions about you that have legal or similarly significant effects; in particular, a person reviews any decision to suspend or close an account (see section 6).
6. Fair use and misuse checks
Imports, AI Chef, and photo scans cost us money each time they run, so we watch for use that does not look like a person cooking at home. To do that we look at usage counters, timing patterns, the number of accounts linked to one device or subscription, failed or repeated requests, and reports from other users.
Our systems can automatically slow down or pause requests that cross fair-use thresholds. That is temporary and lifts by itself. A suspension or closure of your account is always reviewed by a person first, and you can ask us to look again. The terms of use explain when and how this happens.
If we take action, we keep a record of what happened and why for up to 12 months, or longer if we need it for a legal claim.
7. Ads and tracking
We use Appstack to learn which ads lead to installs and subscriptions. If you tap Allow on the iOS tracking prompt, the app shares your device’s advertising identifier and your email address with Appstack, which passes them to Meta, Google, and TikTok so they can match ads to installs. Those companies use the data under their own privacy policies.
If you tap Ask App Not to Track, we do not access your advertising identifier or share your email for this purpose. You can change your choice at any time in iOS Settings › Privacy & Security › Tracking.
8. Who we share data with
We use these service providers. They may only use your data to provide their service to us.
| Provider | What for | Where |
|---|---|---|
| Google (Firebase and Google Cloud) | Sign-in, database, file storage, servers, app configuration, App Check | United States [confirm region] |
| OpenAI | The AI features in section 5 | United States |
| RevenueCat | Managing subscriptions | United States |
| Appstack | Install and ad attribution | [confirm] |
| A proxy network provider | Downloading the public video or page behind a link you import. It receives the public link, not your account details | [confirm] |
| Cloudflare | Hosting this website | Global |
We also share data:
- With Apple, which sells subscriptions and is responsible for payments as an independent controller.
- With Meta, Google, and TikTok, as independent controllers, only if you allow tracking.
- With people you share a cookbook with. They can see its name, cover, recipes, and photos, and anyone you send an invite link or QR code to can join while the invite is on.
- With authorities or advisers when the law requires it, to protect people from harm, or to establish or defend legal claims.
- With a buyer or successor if ReciQuick is sold or reorganized, under the same protections.
When you import a public post, we keep one shared copy of the original recipe and the creator’s public profile so everyone who imports the same link gets the same recipe. Your own edits, notes, and ratings stay on your copy. Star ratings are combined into an average shown to other users without your name.
9. International transfers
Some of our providers store or process data outside the UK and the European Economic Area, mainly in the United States. When they do, we rely on adequacy decisions (such as the UK Extension to the EU–US Data Privacy Framework, for providers certified under it) or on standard contractual clauses with the UK International Data Transfer Addendum. You can ask us for a copy of the relevant safeguards.
10. How long we keep data
| Data | How long |
|---|---|
| Your account, recipes, cookbooks, plans, lists, fridge, photos, and AI Chef chats | Until you delete them or your account |
| Recipes you added to someone else’s shared cookbook | They stay in that cookbook after you leave or delete your account, until its owner removes them |
| Server logs | Up to 30 days |
| Data sent to OpenAI | Up to 30 days at OpenAI |
| Records of fair-use action, suspensions, and appeals | Up to 12 months after the matter ends |
| Support emails | Up to 2 years after the conversation ends |
| Subscription records held by Apple and RevenueCat | Under their own policies |
When you delete your account in Settings, we delete your account and its data from our live systems straight away. [If backups are enabled, add: “Copies in backups are overwritten within N days.”] Deleting the app without deleting your account does not delete your data.
If you never link an email or Apple account, your account lives only on your device. If you lose or reset the device, we cannot tell which account was yours, so we cannot restore it.
11. Your rights
Under UK and EU data protection law you can ask us to:
- give you a copy of your personal data, including in a machine-readable format;
- correct data that is wrong;
- delete your data (you can also delete your account yourself in Settings);
- restrict how we use it;
- stop using it where we rely on legitimate interests, unless we have compelling reasons; and
- withdraw any consent you gave, at any time.
Email hello@quickrecipe.app from the address linked to your account, or include your account ID from Settings. We reply within one month. We may need to check it is really you first.
If you are unhappy with how we handle your data, please tell us first. You can also complain to a regulator: in the UK, the Information Commissioner’s Office (ico.org.uk); in Poland, the President of the Personal Data Protection Office (uodo.gov.pl); or the data protection authority where you live or work.
12. The website
This website has no analytics, no ads, and no tracking. It remembers your language choice in your browser’s local storage. Our host, Cloudflare, processes your IP address and request details to deliver the pages and protect them from attacks, and may set a strictly necessary security cookie when it suspects automated traffic.
13. If you are a recipe creator
When a user imports one of your public posts, we store the recipe, the post link, a thumbnail, and your public name or handle so we can credit you with “Recipe by” and link to your other recipes. We do this on the basis of our legitimate interest in crediting creators accurately. If you want your profile or recipes removed, email hello@quickrecipe.app with links to the posts.
14. Children
ReciQuick is not for children under 16, and we do not knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.
15. Security
Data is encrypted in transit and at rest by our providers. Database rules keep each account’s data private to that account, server requests are checked with Apple App Attest, and access to production systems is limited to the people who need it. No system is perfectly secure; if a breach puts you at high risk, we will tell you without undue delay.
16. Changes and contact
If we change this policy, we will update the date at the top. If a change matters, for example a new use of your data, we will tell you in the app before it takes effect and ask for consent where the law requires it.
Questions: hello@quickrecipe.app, [postal address].
This policy is available in English and Polish. Both versions have the same meaning.