Privacy policy

Platefolio is a place to keep your recipes. It runs no ads, sets no tracking cookies, 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.

What Platefolio does not do

• No advertising, and no ad networks anywhere on the site or in the app.
• No tracking pixels, no advertising or social media scripts, and nothing that follows you from Platefolio to other sites.
• 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. Visitors from the EU are left out of it entirely. What it produces is a count of visits, not a profile of visitors.

Photo import happens on your device

When you import a recipe from a photo or a screenshot, the text is read in your browser. The image is not sent anywhere to be read. It is uploaded 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.

About recipe photos

A photo you attach to a recipe is stored at a long, randomly generated web address. It is not listed or linked anywhere, and nothing points anyone to it, but that address is reachable without signing in. Treat it 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, only if you choose to sign in with a Google account.

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 two things in your browser: the token that keeps you signed in, and whether you prefer the light or dark theme. Both are there because the app would not work without them. 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. Nothing is stored for tracking, and the visit counting above is cookieless, so there is nothing here for you to accept or decline. That is why you were not handed a cookie banner on the way in.

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, particularly once recipe sharing arrives. Material changes will show up here.

Last updated August 24, 2026.