Privacy Policy

1 Your account

A Platter account is required to use the app — it's what saves your recipes and keeps them in sync. You can create an account in one of three ways, and what we collect depends on which you choose:

• Email & password. We collect your email address and a password. Your password is stored only as a secure one-way hash (Argon2) — never in plain text — and is used solely to sign you in.
• Sign in with Apple. Apple sends us a signed identity token. From it we receive a stable Apple user identifier and, depending on what you allow, your email address (which may be an Apple private-relay address) and your name. Apple shares your name only once, at first sign-up.
• Sign in with Google. Google sends us a signed identity token, from which we receive a stable Google user identifier, your email address, and your name if it's available.

For every account we store: an internal account id, your email address, whether it's verified, your name if provided, the provider identifier that links your Apple or Google login to your account, and the dates your account was created and updated. The identity token itself is used only to verify who you are at sign-in and is not retained afterward.

2 Your recipes and lists (cross-device sync)

So your data follows you across devices, we store the content you create and save on our backend, tied to your account. This includes your:

• Recipe library
• Meal plan
• Grocery list (checked-off items and any items you add by hand)
• Cookbooks and their contents

This data is held in a PostgreSQL database hosted on Railway, our backend infrastructure provider. It is associated with your account and used to deliver and sync the app's features — not for advertising or profiling.

3 Turning shared links into recipes

When you share an Instagram Reel, a TikTok, or a recipe blog link with Platter, we send that URL to our backend and process the linked content to pull out a structured recipe — its title, ingredients, and steps.

In practice that means resolving the link, retrieving publicly available information about it (such as a video's caption and metadata, or a blog page's text), and analyzing that text to build the recipe. To structure the result, the retrieved text is processed by a third-party AI provider (see the next section). We keep a cached copy of the extracted recipe so the same link doesn't have to be reprocessed later.

4 AI-generated recipes

Sometimes a shared post doesn't contain enough detail to reconstruct a full recipe. In those cases, Platter may generate a standard recipe for the identified dish using a third-party AI model (OpenAI), drawing on general culinary knowledge rather than extracting it from your submitted content.

To do this, the relevant text — a caption, page content, or a dish name — is sent to OpenAI to produce the structured recipe. This is used only to create recipe content; we don't use it to build advertising profiles or track you.

5 Images

Platter does not accept or store photos you upload — there is no user photo upload. The food imagery you see is stock imagery:

• Recipe photos: when a shared video has no usable thumbnail, we fetch a relevant photo from the Pexels stock photo library, searched by the recipe's title.
• Grocery-list ingredient icons: these come from the same Pexels stock photo library and ship bundled inside the app.

6 Feedback you send

If you send feedback from within the app, we store what you submit — a rating, your message, and an optional contact email — in our database so we can read it and act on it.

Feedback is not shared with third parties and not emailed anywhere externally. It's viewable only through a password-protected internal admin page.

7 Deleting your account

You can delete your account and its data from within the app at any time. When you do, we permanently remove:

• Your account record and profile details
• The Apple/Google identities linked to your account
• Your saved sign-in sessions
• Your synced library, meal plan, grocery list, and cookbooks

One thing is kept: the shared recipe cache. When a link is turned into a recipe, the resulting recipe content is stored under an identifier for the source (for example, the video), not under your account. Because this cache isn't linked to your account or identity, and because other users who saved the same source rely on it, it is retained after you delete your account.

8 What Platter does not do

Based on how the app and backend are currently built:

• We don't show ads or do cross-app advertising tracking.
• We don't sell your personal data.
• We don't embed third-party analytics or tracking SDKs in the app or the backend.

Platter does rely on a small set of service providers to function — Apple and Google for sign-in, OpenAI for recipe processing, Pexels for stock imagery, and Railway for hosting and the database. These providers process data on our behalf to run the service; they are not advertising networks.