How your data is handled

Your selections live in your browser while you work through the list. None of them are sent anywhere until you press Submit. If you get halfway, change your mind and close the tab, not one of the things you touched was ever saved — there is nothing to delete, because nothing was written.

Joining is the one thing that happens earlier: when you enter your name, you are added to the participant list and we count a join. That records that someone joined and how many people are now in the session — never anything you went on to pick.

Only the interests everyone marked as a yes. On those, the other participants see your display name and the role you chose.

Anything you marked that someone else didn’t is never shown to anyone. Not as a result, not as a hint, not as a count, not as a “close match”. It simply is not in the data anyone else can request.

People in the session can see that you joined and whether you have submitted yet — your name appears in the participant list either way. They cannot see anything you picked until the conditions above are met.

The honest part. Your selections sit in a database on a server we control until the session expires. They are not end-to-end encrypted, so we could technically read them. We don’t, and there is no feature, export or admin screen that does — but you are trusting us on that, and you should know that’s what you’re trusting.

If that isn’t a trade you want to make, that is an entirely reasonable conclusion.

Whoever creates a session picks 1 day, 1 week, or 1 month. When that passes, the session and everything in it — names, selections, matches — is permanently erased, and the app stops serving it immediately on expiry rather than waiting for the cleanup to run. There is no archive and no backup you can be restored from. Your results page shows a live countdown.

There is no sign-up, no email, no password and no cookie. When you join a session your browser keeps a single value in localStorage so the app knows you’re you when you come back to the results.

Two consequences worth knowing. On a shared device, whoever opens that link next is treated as you. And the session link contains a code, so it will appear in your browser history — if that matters where you are, open it in a private window.

We count visits with Fathom, which is cookieless, collects no personal data and honours Do Not Track. Automatic tracking is switched off, because it would report the page URL and a session URL contains the access code. Pageviews are sent manually with the code stripped out, so/session/ABC123/resultsis reported as/session/results, and query strings are dropped entirely.

We record which features get used — a session being created, a link being copied, selections being submitted — as fixed labels with no detail attached. No display name, no interest and no answer is ever included.

One event carries a number: when someone joins a session, we report how many people are in it. It tells us whether this is mostly used by pairs or by larger groups, which is the difference between two quite different products. It says nothing about who those people are, what they picked or which session it was.

A free community tool. No company, no ads, no investors and no revenue — there is nothing here that would ever make your answers worth selling.

It lists explicit adult activities by name and is intended only for adults.