PLATEFOLIO RECIPES PlatefolioEvery recipe, served your way
Recipes Head Chef Roadmap Sign in
Sign in

Privacy policy

Platefolio is a place to keep your recipes. It runs no ads and does not sell or share your information.

What Platefolio collects

  • Your email address. That is the whole account. There is no password to store, because signing in works by emailed link or through Google.
  • What you put in. Recipes, ingredients, steps, photos, categories, and cookbooks. You wrote it or imported it, and it stays yours.
  • How you use your own recipes. Which ingredients and steps you have checked off, and when you marked a recipe as cooked. This is what lets the app show you a cook count and pick up where you left off.
  • The original of anything you import. The pasted text, the fetched page, or the photo is kept alongside the parsed result, so a bad import can be corrected later without making you go find the source again.
  • When an import fails, the site's domain and the reason. Only the domain, never the full address. It shows which sites need work on our end. It is not a record of what you browse.
  • Anything you report. If you flag a public recipe, we keep the report, including any note you write, so a moderator can review it.

What Platefolio does not do

  • No advertising, and no ad networks anywhere on the site or in the app.
  • No advertising or social media scripts, and nothing that follows you from Platefolio to other sites. The traffic measurement described under "Counting visits" below stays inside this app; it isn't shared with an ad network or used to target you elsewhere.
  • No selling, renting, or trading your information.
  • Your recipes are not used to train machine learning models, and are not handed to anyone else for that purpose.

Counting visits

Platefolio measures traffic with Cloudflare Web Analytics, which is cookieless. It records that a page was viewed, roughly where the visit came from, and how quickly the page loaded. It sets no identifier, cannot follow you between sites, and cannot pick you out of the crowd.

Platefolio also uses Google Analytics for a closer look at how the app is used, such as which pages people visit and in what order. Outside the EU, EEA, and UK, it is on by default from your first visit. If you're visiting from the EU, EEA, or UK, you'll see a banner asking first, and it stays off until you accept. Either way, declining costs you nothing: every feature works the same regardless of what you choose.

Photo import happens on your device

When you import a recipe from a photo or a screenshot, text recognition runs in your browser. If the result is low quality, the image may also be sent to Google Cloud Vision to improve accuracy. The image is not stored by Google beyond that recognition step. It is uploaded to Platefolio only if you go on to save the recipe, and then it is stored privately and served through a temporary signed link. Screenshots tend to catch notifications and open tabs along the edges, so this one is deliberately not a public file.

Making a recipe or cookbook public

By default everything you keep in Platefolio is private to you and your household. A recipe or a cookbook only becomes visible to other people when you deliberately switch it to public. When you do, it gets a shareable link, and anyone with that link can read it without signing in.

Public pages are meant to be shared, so they are built to travel: search engines can index them, and pasting the link into a message or a social post can produce a preview showing the recipe's title and photo. That is the point of making something public, but it also means you cannot count a public recipe as private-by-obscurity. Switch it back to private at any time and the public link stops working, though a preview already cached elsewhere may linger for a while beyond our reach.

Reactions like favorites and ratings stay private to your household and are never shown on a public page.

About recipe photos

A photo on a recipe you have made public is public too: it appears on the shared page and in link previews. A photo on a private recipe is different. It is stored at a long, randomly generated web address that is not listed or linked anywhere, but that address is reachable without signing in. Treat that the way you would an unlisted video link: fine for a photo of dinner, not the place for a picture of anything private.

Importing from a link

When you import a recipe by pasting a link, our server fetches the page, not your browser. The site you are importing from sees a request from Platefolio, honestly identified as such. It does not see you, your IP address, or your account.

Who else handles your data

Platefolio is a small app built on other people's infrastructure. This is all of it:

  • Supabase stores the database, the accounts, and the uploaded files.
  • Cloudflare serves the site and the app, so it handles the requests your browser makes, and provides the visit counts described above.
  • Sentry receives an error report when something breaks. It is configured not to send personal information, request contents, or cookies.
  • Resend sends the sign-in emails and holds the contact list described below.
  • Google, if you choose to sign in with a Google account; for the Google Analytics traffic measurement described above; and for Google Cloud Vision, when on-device text recognition produces a low-confidence result on a photo import.

Email

Signing up adds your address to a list used for occasional news about the app. Sign-in links are separate and will always be sent, since that is how you get in. To come off the news list, use the unsubscribe link in any of those emails, or just ask.

Cookies and local storage

Platefolio keeps a few things in your browser: the token that keeps you signed in, whether you prefer the light or dark theme, and your choice about Google Analytics if you were asked. It also notes which site or link first brought you here (a site name like "reddit.com", never a page address or anything about you), and if you sign up, that one word is saved with your account so we can tell which places are worth telling people about. Cloudflare may also set a short-lived cookie that tells real browsers apart from bots, which is a security measure and carries nothing personal about you. Google Analytics, when it's on, sets its own cookies to distinguish one visit from another; see Google's cookie policy for what those are.

Deleting your data

Deleting a recipe or a cookbook takes it out of your collection right away. Behind the scenes it is marked as deleted rather than erased on the spot, which is what makes an accidental deletion recoverable.

To delete your account and everything in it, email contact@platefolio.app from the address you signed up with. There is no self-service button for this yet. It is done by hand, and it is permanent.

Children

Platefolio is not intended for children under 13, and accounts are not knowingly created for them.

Questions and changes

Anything you want to ask about this goes to contact@platefolio.app.

This policy will change as the app does. Material changes will show up here.

Last updated September 14, 2026.

Platefolio RecipesRoadmapHelpContactAcceptable useTerms