Your recipes and photos are yours. Nobody at declippr reads them, and nothing is sold or tracked. You can take everything with you, or delete it all, at any time.
declippr photographs recipe cards and turns them into recipes you can read, search and cook from. This page says what it keeps to do that, who else sees it, and how to take it all back.
Last updated September 28, 2026.
What declippr stores
- Your account. A username, an email address, and the date you signed up. Your password is never stored — what is kept is a hash of it, which cannot be turned back into the password, and which is all declippr itself ever sees.
- Your recipes. Titles, ingredients, steps, servings, any cuisine or region, where a recipe came from, and the notes written in the margins.
- Your photographs. The pictures you take of cards, kept so a recipe can be checked against the card it came from.
- Your shopping list and which cookbooks you are in.
- Anything you report as broken, along with which app or browser you sent it from.
- A record of each reading. Which model read it, how many photographs, how much it cost to run. This is how the app knows what it is spending. It holds no part of the recipe itself.
What you type into “What can I make?” is not stored. It is used to answer the question and then it is gone. A photo of your fridge or a shelf that you give it is sent to Claude to be read and is not stored either.
Who else sees it
declippr is a small app built on other people’s infrastructure. These are all of them:
- Anthropic. Your photographs, and any recipe text you paste, are sent to Claude to be read. This is the one step that cannot be avoided: reading handwriting is the whole product. Anthropic’s terms for the API declippr uses say they do not train models on what is sent through it — their privacy policy is the authority on that, not this page.
- Cloudflare. Photographs are stored in Cloudflare R2.
- Railway. The app and its database run there, so everything above sits on their machines.
- Resend. Sends the email declippr has to send — confirming an address, resetting a password. They receive the address it is going to.
- Apple, Stripe and RevenueCat. Only if you buy declippr unclipped or extra reads. On the iPhone, Apple takes the payment; on the website, Stripe does. RevenueCat keeps track of who has paid, whichever way they paid, and tells declippr. It knows your account by a number, not your name. Your card details go to Apple or Stripe and never reach declippr. If you buy on the website, Stripe also gets the email address you give for the receipt. declippr itself keeps only what it needs: whether you subscribe, until when, and how many extra reads you have left.
- GitHub. When you report something broken, a copy of what you wrote is filed in declippr’s own issue tracker so it can actually be fixed.
People you share a cookbook with see the recipes you put in it, and your name beside them. That is the point of a cookbook, and it is the only way another person sees anything of yours.
What declippr does not do
- No advertising, and no advertising trackers.
- No analytics. There is no Google Analytics, no pixel, no third-party measurement kit in the app or on the website.
- Nothing here is sold, rented, or handed to a data broker. Ever.
- Your recipes are not read by anyone at declippr except when you ask for help with a specific problem.
Taking it with you, or deleting it
Save & restore hands you every recipe you have as one file, at any time, without asking anybody. It is yours to keep somewhere else, and it works whether or not declippr still exists.
To delete your account and everything in it, go to Save & restore on the website, or Account in the app, and choose Delete my account. It asks for your password, then everything goes at once: the recipes, the photographs, your shopping list, any cookbook you made, and the account itself. Take a backup first if you want to keep anything — deleting is not reversible.
Deleting your account doesn’t cancel a subscription, so cancel it first: on the iPhone in Settings → your name → Subscriptions, or on the website from the declippr unclipped page.
Two things are kept. Anything you reported as broken stays as you sent it, so it can still be fixed. The record of what each reading cost stays too, no longer tied to you; it never held any part of a recipe.
Keeping it safe
- Everything travels encrypted, on the website and in the app.
- Passwords are hashed, so a copy of the database does not hand anyone your password.
- Resetting your password ends every session that was signed in with the old one.
- On iPhone you can require Face ID to open the app, which also puts your stored sign-in behind it.
No small app can promise it will never be broken into. What it can promise is that there is nothing here worth stealing but recipes, and that your password is not among them.
Children
declippr is not aimed at children and does not knowingly keep accounts for anyone under 13. If one has been made, email the address below and it will be removed.
If this changes
The date at the top moves when the substance of this page does. If what is stored or who it is sent to ever changes materially, that change and this page land together.
Questions about any of it: tyhelton@gmail.com.