Privacy Policy

Draft placeholder. Not legal advice. Must be reviewed before public launch.

Account holders

We store your email, username, when you accepted our terms, and that you confirmed you're 18+ (with the date you did). We check your date of birth at sign-up but don't store it.

Your photo and link stats

If you add a profile photo, it's shown publicly on your link page and story cards. Your phone shrinks it and removes hidden photo data (like GPS location) before upload. To count how many people opened your link today, we store a one-way hash of each visitor's device ID and IP address, once per visitor per day, and delete these records after 30 days. You only ever see the total number.

Answers you post

If you post an answer, the question text, your answer and when you posted it are public on your profile. Posts never include who sent the question, hints, reveals, or any sender data. Hiding a post removes it from your profile; deleting a question removes it from your inbox and profile (we keep a copy only for safety reviews).

If you send a question, its text may appear on the recipient's profile if they answer it. Nothing that could identify you is shown. When someone reports a post, we store the report and a one-way hash of their device ID or IP address to limit abuse.

Story photos

Background photos you add to story images never leave your phone: the image is put together in your browser and we never receive the photo.

Signing in with Facebook or TikTok

If you sign in with Facebook, we receive your Facebook account ID, name, email address and profile picture link. If you sign in with TikTok, we receive your TikTok account ID for Psst and your display name; TikTok doesn't share your email. We use these only to sign you in. After a social sign-in we ask for your date of birth to check you're 18+, and don't store it. To delete your data, see Delete your data.

People sending questions

For each question we record:

What the recipient can see

The recipient can unlock hints, one at a time: the time sent, your device type, whether you were signed in or a guest, whether you've sent them questions before (same account or device), and your approximate location. "Approximate location" is estimated from your IP address: it shows your city only when the lookup is confident (a city of at least 50,000 people that no smaller place shares its name with), otherwise only your country. They can only see the first letter of your username, or who you are (your username, or your Instagram if you verified it), if you were signed in and allowed a reveal for that question. They never see your IP address, the hashes above, or your exact location.

Questions sent before hints existed (before November 2026) never show hints, because their senders were told this information would stay private.

Referrals

When you open someone's profile link without being signed in, we store their username in a cookie (for up to 90 days). If you then create an account, we record that they referred you. We use this to give you the referral prices and to give them a free hint. They see only how many people joined through their link, never who.

Instagram and purchases

If you add your Instagram username we store it, marked unverified until you verify it. If you buy Pro or a reveal, we keep a record of what you bought, when, and the price.

Consent records

When you allow a reveal, we keep a record of the question, the time, and the exact text you were shown. We also record when you withdraw consent. We keep these records to show what you agreed to.

Other uses

We use this data to run hints and reveals, rate-limit, enforce blocks, investigate abuse reports, and where required by law.

Cookies

We use a login session cookie, a random device ID cookie for rate limiting and blocking, and a referral cookie (the first profile link you opened before signing up).

Your rights

You can ask us to access or delete your data. Contact details to be added.

Credits

City population and region data from GeoNames, licensed under CC BY 4.0.