Your palate is yours.

Palate is a personal project in beta, operated by an individual (Weston Walker), not a company. There's no support team behind it — questions and requests come straight to me through the in-app Feedback button (bottom-right on any screen), which reaches me directly.

Only what the app needs to build your palate and run the loop:

• Your email and sign-in. Sign-in is handled by Clerk, our authentication provider. We store your email address to sign you in, recognize you when you come back, and reach you about the beta. That's the only contact detail we ask for — no name, address, or phone number.
• Your palate. Your taste-test answers and the flavor-preference vectors we derive from them.
• Your cooking activity. Cook logs (what you cooked, when, your verdict, and any note you add), your dish rankings and the head-to-head comparisons that produce them, and bookmarks (recipes you save to cook later).
• Your Weekly Five. The recipe picks we freeze for you each week so they stay stable across devices.
• What we showed you. A record of which recommended recipes were displayed to you (and whether you opened them), so we can tell a good recommendation from a bad one and improve the picks.
• Feedback you send. Any beta feedback you submit, along with which screen you were on when you sent it.
• Meal photos (optional). If you attach a photo to a cook log, that image is uploaded and stored on our server. Photos are optional — skip them and none are collected.

We do not collect payment information — the beta is free and never asks for a card.

When you paste a recipe to X-ray it, the text of that recipe is sent to OpenAI to analyze its flavor structure. We send the recipe text only — never your email, your name, or any identifier. The analysis is about the food, not about you.

Your data is stored in the United States and processed by a small set of service providers. Each one only handles the slice it needs to do its job:

• Neon — the Postgres database (hosted in the US) that stores your account and activity.
• Railway — hosts the application and stores uploaded meal photos.
• Clerk — handles sign-in and keeps your session secure.
• OpenAI — analyzes the recipe text you paste (never your identity).
• PostHog (product analytics) and Sentry (error reporting) — when enabled, these help us understand how the app is used and catch crashes. They're configured to avoid capturing sensitive content; if session replay is ever turned on, text you type is masked.

These providers process your data on our behalf to run Palate. We don't sell your data, we don't show ads, and we don't share it with anyone beyond the providers above.

Clerk sets a session cookie so you stay signed in — that's essential to using the app. When analytics are enabled, PostHog may set identifiers to measure how features are used. There are no advertising or cross-site tracking cookies.

We keep your data for as long as your beta account is active. Because this is an early beta, it may occasionally be reset, which can clear stored data. You can ask for deletion at any time — see below.

You can have your account and everything tied to it deleted, at any time, for any reason:

• Send a deletion request through the in-app Feedback button (bottom-right on any screen) — just say "Delete my Palate data" and I'll take it from there.
• Your account and all associated data — palate, cook logs, rankings, comparisons, bookmarks, weekly picks, recommendation records, feedback, and any uploaded photos — will be deleted within 30 days.
• You can also use that same channel to ask what data we hold about you.

Palate isn't intended for anyone under 13, and we don't knowingly collect data from children.

As the beta evolves, this policy may change. If a change materially affects how your data is handled, we'll let testers know rather than change it quietly.

Questions, concerns, or a deletion request — reach me through the in-app Feedback button (bottom-right on any screen). See also our Terms.