Privacy Policy
Reelery saves recipes you find on Instagram, TikTok, YouTube and Facebook into your own private collection. This page says exactly what that involves, in the order that it happens.
Last updated 31 August 2026. Effective 31 August 2026.
The short version. Reelery has no analytics, no advertising and no tracking of any kind. It keeps your email address, the recipes you save, and a count of how many you have saved. When you share a post, its public description is sent to two processing services to be turned into a recipe. Neither of them is told who you are. Nothing is ever sold. Deleting your account deletes all of it, immediately.
Who is responsible
Reelery is made and operated by Andersen Keller, an individual developer based in Arizona, United States. For anything on this page, including a request to access or delete your data, write to support@reelery.app.
What Reelery collects
Your account
You need an account, because your recipes have to belong to somebody. Depending on how you sign in, that means:
- Email and password. Your email address is stored. Your password is never stored. The authentication service keeps only a one-way hash of it, which cannot be turned back into a password.
- Sign in with Apple. Apple sends an account identifier and an email address. If you choose Hide My Email, the address Reelery receives is an Apple relay address, and Reelery never learns your real one. Apple also sends your name on the first sign-in only, and only if you allow it; it is used as your display name and nothing else.
What you save
When you share a post into Reelery, it stores:
- the link to the original post, which platform it came from, and that platform's own identifier for it;
- the recipe extracted from the post's public description: title, ingredients, steps and times;
- the original creator's username on that platform and a link back to their post, so every recipe stays attributed;
- the web address of the platform's thumbnail image. The image itself is not copied. Your phone loads it from that platform directly, and no image file is ever stored on Reelery's servers.
Plus whatever you add yourself afterwards: edits to a recipe, the cookbooks you file it under, and items on your grocery list.
What it takes to run the service
- A record of each save. One row per attempt to save a post, with its outcome. This is what enforces the rate limit and counts the free allowance. It is not used to build any profile of you.
- Your subscription status, if you subscribe: the plan and its expiry date.
What stays on your phone
Ingredients you tick off while cooking, and a cache of your own recipes so the app opens instantly, are stored only on your device. They are never uploaded and do not survive reinstalling the app.
What Reelery does not collect
There is no analytics SDK, no advertising SDK, and no third-party tracker in this app. Nothing you do in Reelery is tracked across other apps or websites, which is why iOS never asks you about tracking.
Reelery does not collect your location, your contacts, your photos, your health data, your device advertising identifier, or your browsing history. It never asks for access to any of them.
Reelery does not receive or store your payment details. Subscriptions are billed by Apple, and Apple does not share your card details with developers.
No video is ever downloaded, stored or served. Only the text of a post's description is processed, and there is nowhere in the database capable of holding a video.
Who else processes it
Reelery uses a small number of services to do work on its behalf. Each is bound to use the data only to provide that service. None of them is given your identity except where the table says so, and none is permitted to use anything for their own purposes.
| Service | What it receives | Why |
|---|---|---|
| Supabase | Your account, your recipes, your grocery list, and everything else stored. Hosted on Amazon Web Services in the United States. | The database, sign-in, and the servers that do the work. |
| Apify | The link to the post you shared. Not your identity. | Fetches the post's public description and thumbnail address. |
| OpenRouter | The text of the post's description. Not your identity. | Runs the language model that turns a description into a structured recipe. Requests are sent with data collection refused, so providers that would keep the text for training are excluded from handling it. |
| The platform you shared from | The link to the post you shared. Not your identity. Which company this is depends on the post: Meta for Instagram and Facebook, TikTok, or Google for YouTube. | Reelery checks that the post exists before anything paid is done, and your phone loads recipe thumbnails from that platform's servers directly rather than from ours. Reelery has no account with any of them and sends them nothing about you. |
| RevenueCat | Your Reelery account identifier and Apple's purchase receipt. No payment details. | Validates subscription receipts and tracks renewal. Only used if you subscribe. |
| Apple | Whatever Apple already holds for your Apple Account. | Sign in with Apple, and billing for subscriptions. |
Reelery does not sell your personal information, and does not share it for advertising or cross-context behavioural advertising. There is nobody to sell it to and no advertising in the app.
A note on the shared cache
The same post shared by two different people is the same post. Reelery keeps a cache of the public description and the extracted recipe for each one, so that the second person to share it does not pay to fetch and process it again. That cache is keyed on the platform's public identifiers and carries no user identity at all. There is no column in it that could say who shared what. It is public content from those platforms, not personal data, and it is deliberately built that way.
Why Reelery is allowed to hold this
If you are in the United Kingdom or the European Economic Area, the legal bases are:
- Performance of a contract, covering your account, your saved recipes, your grocery list, and your subscription. The app cannot do what you asked without them.
- Legitimate interests, covering the record of save attempts, used to stop abuse and to keep the service affordable to run.
- Legal obligation, covering records Apple or tax authorities require to be kept about a purchase.
Reelery does not rely on consent, because it does none of the things that would require it.
How long it is kept
- Your account and everything in it is kept until you delete it. Reelery does not expire inactive accounts.
- When you delete your account, everything goes at once, in one operation. See Delete your account for exactly what goes.
- Encrypted database backups: deleted data may persist in routine backups for up to 30 days before those backups age out. Backups are not used to restore deleted accounts.
- The shared post cache is kept indefinitely, because it contains public content from those platforms and no personal data.
Security
- Everything travels over HTTPS. There is no unencrypted path.
- Every table enforces row-level security in the database itself, so one account cannot read another's rows even if the app asked it to.
- The share sheet uses its own credential rather than your sign-in session, and only a hash of that credential is stored.
- Passwords are stored as one-way hashes and are not recoverable by anyone, including Reelery.
No system is perfectly secure, and Reelery is a small independent app rather than a large company with a security team. It is built carefully, but that is worth saying plainly.
Your rights
Wherever you live, you can ask for a copy of your data, ask for it to be corrected, or delete it. Deletion is built into the app and takes effect at once. See Delete your account. For anything else, write to support@reelery.app and you will get a reply within 30 days.
If you are in the EEA or UK you also have the right to object to processing, to restrict it, to data portability, and to complain to your national data protection authority. If you are in California, you have the right to know, delete, correct and opt out of sale or sharing, and as stated above, Reelery does neither. You will never be treated differently for exercising any of these.
Children
Reelery is not directed to children under 13, and accounts are not knowingly created for them. If you believe a child has an account, write to support@reelery.app and it will be deleted.
Where your data is
Reelery's database and servers are in the United States. If you use the app from outside the United States, your data is transferred there, and United States law may give it less protection than the law where you live. Where a transfer mechanism is required, Reelery relies on the data processing terms offered by each of the services named above, which incorporate the European Commission's Standard Contractual Clauses.
Changes to this policy
If this policy changes in a way that matters, the date at the top changes and you will be told in the app before the change takes effect. Continuing to use Reelery after that means the new version applies.
Contact
Andersen Keller
Arizona, United States
support@reelery.app