Privacy
What we know about you, and what we don’t.
This notice covers this website, its temporary browser demo, the beta list you can choose to join, and the private Twin Training page for internal testers. Website hosting processes request information, and you may also email us directly. TasteTwins is a native mobile app. The iPhone build is in private testing; an Android build is in active development. Part two describes how the app handles data.
Part one — this website
This website serves public pages, a beta-list form, and a private Twin Training page for internal testers. The interactive demo uses temporary state in the current browser tab. Reloading the page discards that demo state.
There are no cookies. There is no analytics package, no tag manager, no advertising pixel, no heat-mapping, no session recording, and no embedded social media widgets. Page resources, including images, styles and scripts, are served from this site. Its browser security policy restricts resource loading and script-initiated connections; ordinary page navigation and email links remain available. You can inspect the requests by opening your browser’s network inspector and reloading the page.
The interactive demo does not leave your browser. Ratings you give, dishes you save and plans you build in the demo are held in your tab’s memory. They are not written to storage, not sent anywhere, and not associated with you. Reloading the page discards all of it. The demo does not create an account, send a message or invitation, or reserve a table — the people and venues in it are fictional.
Hosting request information
The site is hosted by Vercel Inc., which keeps ordinary web server logs the way every host does: the requesting IP address, the time, the page requested, and the browser’s user-agent string. These exist so the site can be delivered and so abuse can be blocked. We do not use them to build a profile of you and do not combine them with anything else. Vercel’s handling of that data is governed by its own privacy policy.
If you join the beta list
If you join the beta list, Love Salone receives your email address, phone type (iPhone, Android or other), general region, how you found us, your selected interest, confirmation that you are 18 or older, and permission to email you about early access. Vercel processes the request for us and stores it in private storage. We send you a confirmation email, and send ourselves a notification of your signup, through our email provider, Resend. We use it only to invite people to the beta in waves; it does not create a marketing subscription or guarantee an invitation. Entries are kept for 12 months and then deleted by a daily retention run. You can ask us to delete your entry sooner at hello@tastetwins.app. The form does not ask for your name, street address, ZIP code, health information or free-text notes.
If you use Twin Training
Twin Training is limited to signed-in internal testers. Supabase stores your account ID, dish answers, selected reasons, and an optional short “Something else…” note you write about what you like or dislike in a dish. That text is private to your account and kept with your answer. We may use AI to read notes like this and improve the choices. Notes are not used directly in matching or shared with other testers. Authorized operators review any suggested new choices before they are added. Please do not enter medical or contact details. You can read your own training answers and undo the latest one through the page; authorized Love Salone operators can review them to improve the reason choices. Training answers remain until you undo them, delete your account, or ask us to remove them at hello@tastetwins.app. Signing in keeps a session in this browser tab.
If you confirm a food rule, we save the excluded food and any exceptions to your account so Twin Training can skip those dishes. You can pause, edit or delete these rules. Rules do not store a medical reason or verify allergens.
Part two — the TasteTwins mobile app
Status
TasteTwins is a native mobile app. The iPhone build is in private testing with a small group of invited people; an Android build is in active development. Android is not in testing or available, and the iPhone build is not on the App Store. This section describes how the app handles data.
About you: age, area and optional details
When you create a TasteTwins profile, we ask for your birth month and year and for you to confirm you're 18 or older. TasteTwins is for adults. We don't ask for your full date of birth.
We also ask for your general area: a city or metro area, or the first three digits of your ZIP code. We don't store your street address or exact location from this question.
You can choose to tell us your gender, the cuisines you grew up eating, and the languages you speak. These are optional. Skipping them doesn't change anything about your account.
How we use them. Your age confirms you can use TasteTwins. Your general area and optional details are stored privately with your account. Today, we don't use them to pick your twins or change your recommendations. In the future, we may use them to make better first guesses about your taste before you've rated many dishes, and to show what's popular in your area. We'll update this policy before we start.
Who can see them. No one else. These details never appear on your profile or twin cards. We don't sell them or share them with advertisers. If we ever share insights built from many people's data, they will be combined and de-identified so they can't be tied back to you, and we'll describe that here first.
Deleting them. When you delete your account, these details are deleted with it.
We don't ask about race or ethnicity.
What it collects
- Your dish reactions. Twin Training uses Love it, Like it, It's fine, Not for me or Never had it. Crave's fast lane uses Yes or No, with a Haven't tried it option.
- Why you reacted. The reason chips you pick, such as "Deep smoke" or "Too salty", and which chips you were shown, so we can make them better. Chips you don't pick are not counted as dislikes.
- Notes you write or say in the app. In the iPhone app, notes you type or speak with Say it are processed on your iPhone. The app keeps the note text on this iPhone; it does not upload it to TasteTwins. Say it does not save an audio recording or send that audio to us. Your dish answer and capture information, including a reference to the note, can be saved to your account. If you confirm a food rule, we save that rule and its exceptions. (Notes written on this website's Twin Training page are covered in Part one.)
- Food rules. Foods you choose to hide, including allergy or religious dietary rules, and any exceptions. Rules hide dishes in training; they are not an allergen check.
- About you. Your age, general area and optional details, as described above.
- What you post and share. Photos and videos you choose to upload, including any sound in a video, reviews, captions, saved dishes and places, plans, venue check-ins you make, and messages you send in Plans and chats.
- People. Who you follow, your friends and plan members, and anyone you block or report.
- App activity. Which dishes and cards you were shown, what you did with them, and when you were last active, to run and improve the app.
- Account basics. Your sign-in email or identifier, username and display name.
- Location while you search. Nearby searches use your phone's current location with Apple's Maps services. TasteTwins does not request background location access. Saved places and check-ins can store the venue and its location with your account.
What it does not collect
- Government identification numbers of any kind.
- Genetic, biological or biometric data. “Taste DNA” is a name for your learned food preferences. It is not a genetic test, it involves no saliva sample, no DNA sequencing and no genetic data of any kind. We chose the name because it is memorable, and we would rather say plainly what it is not.
- Protected health information or medical records. TasteTwins is not a medical device and does not diagnose, treat or give clinical advice.
- Background GPS logs or travel history.
- Card numbers or financial account details. If payments are ever introduced, they will run through a PCI-compliant processor and the card details will not reach us.
- Your phone contacts, calendar or whole photo library. We only receive the photos and videos you choose to upload. Say it uses your microphone during a recording you start; that audio is processed on your iPhone and is not sent to us.
How it is protected
- Row-level security is enabled on every application table, so a query can only ever return rows the requesting account is entitled to.
- The access policies do not permit anonymous row operations. An unauthenticated request cannot read or write application data.
- Your taste vectors are stored separately from your profile content, and an authenticated account can only insert and manage its own.
- Data is encrypted at rest with AES-256 and in transit with TLS 1.3.
- Access follows role-based controls.
A claim we are not making
Your taste vectors are linked to your account. They are stored in their own tables, with their own access policies, apart from your profile — but the link exists, and the protection is access control, not anonymization. Some products describe arrangements like this as cryptographically anonymous. Ours is not, and we would rather tell you what it actually is than borrow a stronger word.
Your control
For help exporting or deleting account data, email hello@tastetwins.app. You can delete your account in the app from Profile → Settings → Delete account. We keep a minimal hashed deletion record so the same request is not processed twice.
Research, and why it is a separate decision
Aggregate patterns in food preference are genuinely useful to public-health and academic researchers, and part of why this company exists is to make that data available to them. That is a completely separate decision from using the app, and it works like this:
- It is opt-in and specific. Nothing about your data goes to a research partner unless you have separately and explicitly agreed to it. Consent to use the app is not consent to be in a dataset.
- Declining costs you nothing. Every feature works identically whether you opt in or not. You will not be nagged, degraded, or shown a worse product for saying no.
- You can withdraw. Turning it off stops your data being included in anything released afterwards.
- Safeguards are being built, and are not finished. Statistical disclosure controls — thresholds ensuring no released record can be traced to a small enough group to identify someone — are a design requirement that must be implemented, tested and documented before any dataset is shared with anyone. They are not in place today. We are saying so rather than describing a planned control as an existing guarantee.
- No brokers, ever. We do not sell, rent or trade individual profiles to data brokers, ad networks or marketers. This is not a business model we intend to leave room for.
Children
TasteTwins is for adults. You must be 18 or older to activate a TasteTwins profile. We ask for your birth month and year and for you to confirm you're 18 or older. The sign-in service may create a login record before this check. In the current iPhone build, you cannot continue into Training or Twins without confirming your age. Existing accounts without a confirmation are asked after updating. The under-18 screen asks you to confirm the entry, so you can correct a typo first. If someone enters an age under 18, the app removes their sign-in automatically. If you believe someone under 18 has given us data another way, write to hello@tastetwins.app and we'll delete it.
Your rights
Depending on where you live, you may have the right to see what we hold about you, correct it, delete it, obtain a portable copy, or object to particular processing. We extend all of these to everyone who asks, regardless of jurisdiction, because maintaining two standards is more trouble than simply having one good one. Email hello@tastetwins.app and we will respond within 30 days.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
Changes
If this policy changes materially, the date at the top changes and app testers are notified in the app. Superseded versions are kept, so a change can always be pointed to rather than quietly made.
Questions, or something here that does not match what you have observed? Tell us — we would rather fix a document than defend one.