Privacy notice

Controller and contact

The controller is Simlabs (a Finnish sole proprietorship, business ID 3664032-5), PO Box 13, FI-00561 Helsinki, Finland.

Contact for privacy matters: Privacy officer, Simlabs, privacy@getbivio.com. The same address is our point of contact for users and authorities under the EU Digital Services Act.

We have not appointed a data protection officer or an EU representative.

What we process

• A random identifier, created the first time you answer, make a question, send a link, share your result or file a report. We do not ask for your name, email or phone number, and there are no accounts. Our sign-in provider keeps an anonymous user record linked to the identifier. We record when the identifier was first and last used.
• A session cookie that keeps the identifier the same in this browser.
• Your answers: the probability, which question and which link you answered through, the version of the question's terms, and the time from our server's clock.
• The questions you make: the question, its resolution rule, source link, language, topic, and close and resolution times. If you made it from another question's page, we record which question and link you came from. Every version of a question is kept.
• Links you send or share: which question, which link it was forwarded from, and which key version signs it.
• Results you propose or dispute: the outcome, the source and any note you write.
• A name, if you type one when you make a question, send a link or share your result (up to 40 characters). You have one name: the latest one you typed.
• Reports: the reason, which question it is about and where it was made, and an optional message and an optional email address.
• Country and region (for example a province or a state), which our provider derives from your IP address; never the city or anything finer. The latest is stored with your identifier and copied into each answer, report and result action.
• A salted hash of your IP address, to limit abuse. We do not store the IP address itself in our own tables. Server memory holds it briefly to rate-limit events, it is sent to Cloudflare for the human check, and it may be passed to our sign-in provider, which can keep it in its own sign-in and security logs.
• Device type (iPhone, Android, desktop or other) and, if the link opened inside an app's browser, that app's name from a fixed list. We do not store the full browser identification string.
• How you answered: on which page, language, whether you had seen the others' estimates before answering, whether you moved the slider, where it started, how long answering took, whether you opened the question's source link, how you reached the link (the link's source tag) and the service's build version.
• Usage events, such as a link was opened, an answer given, the others' estimates seen, a link forwarded, a result shared or a question made, and the start, submission and failure of an answer. Our server sends them to PostHog with the random identifier, with no free text, names or location. Before your first answer, the identifier is a random one drawn for each page view and not stored on your device.
• The age band you choose when you write (under 13, 13–15, 16–17, or 18 or older). We record it the first time and whenever it changes, with the time, the age question's version, the service's build version, your country and region, and the version of this notice, if you have accepted it. Your browser does not send an under-13 answer, and we store nothing about it.
• Two entries on your device (localStorage) after you answer: that this browser has answered the question, and through which link. With them, the page shows the others' estimates instead of the slider. If you said you are 18 or older and the write succeeded, a third entry remembers it, so this device is not asked your age again.
• If you answer the age question with an age under 18, a cookie called age_block is stored on your device for 24 hours. It stops all writing from this browser except reports if you answered 13–17, and everything if you answered under 13. Its value says only which of the two applies.

We use no cookies other than the session cookie and age_block: no advertising, tracking or analytics cookies and no session recording, and we show no ads.

What we use it for, and on what legal basis

• Providing the service: showing questions, saving answers, showing others' estimates after you answer, settling results, and the results you share. Basis: providing the service you ask for by using it.
• Security and abuse prevention: the human check, rate limits, the check of new questions, handling reports and moderation, and revoking leaked link keys. Basis: our legitimate interest in keeping the service usable and free of spam, bots and harassment, and in protecting people that questions are about.
• The age limit: the age question, its record, and stopping people under 18 from writing. Basis: our legitimate interest in protecting minors.
• Measuring the service with usage events. Basis: our legitimate interest in knowing whether the service works, without advertising or profiling.
• An unchangeable record: who estimated what and when, and salted fingerprints of question texts, so that a later change can be proven. Basis: our legitimate interest in a record nobody, including us, can quietly rewrite.
• Country and region: whether the service is available in your region, and flagging some regions for review. Basis: legitimate interest.
• Legal duties: recording reports and moderation decisions, answering privacy requests, and recording which version of this notice you were shown. Basis: a legal obligation where one applies to us, and otherwise legitimate interest.

Where we rely on legitimate interest, the balance rests on the data being pseudonymous, minimal and never used for advertising.

No processing relies on consent today. If any does later, you can withdraw consent at any time, as easily as you gave it, without affecting processing before the withdrawal.

Research, AI development and comparing AI models with human judgment: we may later use pseudonymised, aggregated answers for these purposes. This has not started. Before it starts, a lawyer reviews it, we publish a new version of this notice, and you can object. We do not sell, license or give data, individual or aggregate, to anyone for these purposes.

Do you have to give us data

No law requires you to give any data. Reading a question needs nothing. Answering, making a question, sharing a link and reporting through the form need a session, an answer to the age question and the content itself, and cannot be done without them. A name is optional; without one, only how others see you changes. A report's message and email address are optional.

The automated check of new questions

Every new question is checked before it is published, with word lists and an AI model from Anthropic. The check looks for forbidden topics about a named person (death or harm, health beyond professional availability, sexuality, sex life or gender identity, pregnancy, their children, and accusations of crimes not already in court).

The check can block a question, in which case it is not created and its text is not stored, or hold it, in which case it stays hidden until a person reviews it. Questions about politics or elections are always reviewed by a person. If the model is off or answers unclearly, the question is held. You see the category of the reason and can contest the decision by email.

The check leaves a record linked to your identifier, also for blocked attempts: a salted fingerprint of the text, the language, the lengths of the fields, the word categories that matched, each stage's result, whether the question seemed to be about a private person, the decision, the model and prompt version and the model's token usage; not the text. The salt is deleted when the question is created, or otherwise within half an hour at the latest. There is no other automated decision-making with legal or similarly significant effects on you.

The AI makes no estimates of its own on questions in the service, and no AI estimate is shown anywhere.

Who sees what

• A question and its details are visible to anyone with the link.
• You see others' answers only after you answer, and then only as an aggregate (how many answered and the distribution). The only individual estimate you see is that of the person whose link you answered through, as it was when you answered.
• The person who sent you the link sees your answer only as part of the aggregate. If you forward the link, people who answer through it see your estimate.
• You can share your own result with a link. It shows only your own estimate, never anyone else's. Your name appears on it only if you typed one when sharing.
• If you type a name, it is shown on the pages and preview images of every link you have sent, to people who answer through your links, and with results you propose, including earlier links, because you have one name. On a result you share, it appears only if you typed it when sharing. Messaging apps keep their own copies of previews, which we cannot delete.
• A result shows its source and note, and whether the question's creator proposed it (with their name, if they typed one) or a moderator confirmed it.
• Staff see reports, including their messages and email addresses.

Reports and moderation

Anyone with a link can report a question or a shared result. A report hides nothing by itself. Staff review it and may hide a question or remove a comment's text. Every action is recorded with its reason.

If your question or comment has been restricted, the question's status page tells you what was restricted, the category of the reason, whether the automated check or a person decided, and when. You can contest the decision by email.

If you are named in a question, you can ask for its removal with a report (reason “I'm named in this”) or by email, even if you do not use the service. On a credible request, the question is hidden at once.

Staff sign in with an email code and an authenticator app. Their identities are kept apart from the record.

Age

Answering, making questions, sharing links and proposing results are for people aged 18 or older only. Anyone may read a question. We ask your age the first time you write, and do not ask for proof. If you answer with an age under 18, what you wrote is not stored, and nothing but reports can be written from this browser for 24 hours. An age band of 13–17 is recorded so that writing stays stopped for your identifier. If you later give a younger age band, writing is stopped.

Someone aged 13–17 can report content through the form, because reporting is a safety measure. We then store the report, the age band and a record of the notice shown. From someone under 13 we store nothing, not even a report. They can contact us at privacy@getbivio.com.

If we learn that someone under 18 has written, we stop their writing, remove their name and the text of their comments, and hide the questions they made. Their answers stay in the pseudonymous record and in the questions' totals, and result links they shared still show their estimate, without a name. They are not used for anything else.

Providers and transfers

• Supabase: database and sign-in, all the data listed above, and your IP address at sign-in. The database is in the EU (Frankfurt).
• Vercel: servers, a worldwide content delivery network and server logs. It handles every request, including your IP address and browser data, and derives your country and region.
• PostHog: usage events and the service's feature switches, on servers in the EU.
• Cloudflare (Turnstile): the human check. It processes browser data and may store data in its own frame, and our server sends it your IP address.
• Anthropic: the check of new questions. It receives the question's text, rule, source and language; not your identifier or your name.
• Proton Mail (Proton AG, Switzerland): the mailbox for privacy@getbivio.com. It holds the messages you send us and our replies. Switzerland has an EU adequacy decision.

Some providers are US companies, and data may be transferred outside the EEA. Ask us which safeguards apply to each transfer.

We do not sell personal data, share it for advertising, or give it to anyone else unless the law requires it.

How long we keep data

• Answers, links, results and their notes, the basic record of reports, moderation decisions, check records and records of the notice you were shown: as long as the service exists, as a pseudonymous record that is never edited. Only moderation can remove the text of a result's note. An unchangeable record of who estimated what and when is the core of the service. On an erasure request we remove what identifies you, and the record stays pseudonymous.
• Question texts: as long as the service exists. A hidden question is shown to no one, but its text stays in our database.
• A name: until you ask us to erase it.
• A report's message and email address: 180 days, then deleted automatically, or earlier on request.
• A check's salt: until the question is created, at most half an hour.
• Rate-limit counters: about a day.
• Usage events at PostHog: for our PostHog project's retention period.
• The age band record: as long as the service exists, as a pseudonymous record. The session cookie: until it expires or you delete it. age_block: 24 hours. The entries on your device: until you clear the site's data.
• Backups may contain erased data for the backup retention period. Server logs are kept for the provider's retention period.

Your rights

You have the right to access your data, have it corrected or erased, restrict its processing, object to processing based on legitimate interest, and receive it to move it to another service.

Send your request to privacy@getbivio.com. As there are no accounts, tell us the question's link, the name you used, and ideally the device and browser you answered with, so we can find your data. If we cannot identify data as yours, we tell you. We answer within one month, which can be extended for complex requests.

A changed mind is a new answer, not an edit of the old one. You can change your name by typing a new one next time. There is no way to edit a question's text in the service.

If you object to usage events or other processing based on legitimate interest, contact us. We cannot stop security processing while you keep using the service.

You can complain to the Office of the Data Protection Ombudsman in Finland (tietosuoja.fi) or to the supervisory authority in your own country.

US state privacy laws

The categories of personal information we collect are identifiers (the random identifier, the session cookie, the IP hash, a name if you give one, and an email address if you give one in a report), internet activity (usage events and answering data), approximate geolocation (country and region) and age band. An answer to a sensitive question can reveal your views; we use it only to provide the service. Purposes and retention are above.

We do not sell personal information or share it for targeted advertising, so there is nothing to opt out of. A Global Privacy Control signal changes nothing.

Changes and errors

When we change what data we process, why or for how long, we publish a new version with a new date and version identifier. We record which version you were shown when you write. Data collected under an earlier version is used only for what both that version and the new one allow.

If you find an error in this notice, tell us at privacy@getbivio.com. We fix it as a new version the same day.