Privacy

Survex is built for honest answers in a room full of colleagues. That only works if anonymity is real, so this page describes exactly what we store — no more, no less. Last updated 28 August 2026.

Who is responsible

Libaty GmbH, Am Krummen Graben 23, 63150 Heusenstamm, Germany(see the imprint). Privacy questions and requests: privacy@survex.me.

For the content of a survey — the questions asked and the answers collected — the facilitator who runs it decides what is collected and why; they are the controller for that data and we process it on their behalf (GDPR Art. 28). A data processing agreement is available on request.

If you answer a survey

• No account, no name, no email. You join with a short code. We never ask who you are.
• A random token instead of an identity. Your device keeps a random token for the session so a page refresh doesn’t lose your place. We store only a one-way hash of it — it cannot be traced back to you, and it lives only in your browser tab.
• Your answers and when they arrived. Nothing else is attached — no IP address, no browser fingerprint, no location.
• Small groups stay hidden. Results are withheld until enough people have answered (the facilitator sets the threshold, three by default), so a single early answer is never exposed.
• Abuse protection without identity. To rate-limit joins we briefly keep a salted hash of your network address — deliberately unlinkable to your answers — and purge it within 24 hours.
• Answers can expire. Facilitators can set raw answers to auto-delete after the session; only aggregate results remain.
• No analytics, ever. Participant pages load no analytics script and set no cookie. Nothing about you is measured.

Legal basis: our legitimate interest in running the survey the facilitator set up and in keeping the service abuse-free (Art. 6(1)(f)), given that no identifying data is collected.

If you run surveys

• Your email address, and that’s it. You sign in with a link we email you — there is no password to store, so none can leak.
• Your sessions are yours alone. Sessions, questions, and results are visible only to the account that created them. Results stay private to you unless you set a results password to share them — the join link participants use never opens results.
• Product analytics on what you do, not who you are. To learn where facilitators get stuck we record events such as “session created” or “results opened”, sent from our server under your account’s internal id — never your email, never a session title, never an answer. No tracking script runs in your browser and no analytics cookie is set.
• AI assistants only if you connect one. If you create an API token and connect an assistant such as Claude, survex sends that assistant what it asks for — your sessions and their results, including participants’ anonymous answers — and its provider’s terms apply to what it receives. We store only a hash of the token; revoking it in your dashboard cuts access at once.
• Deleting means deleting. Deleted sessions are purged permanently after 30 days, along with all their answers. Deleting your account removes your account and every session in it immediately.

Legal basis: performance of the contract with you (Art. 6(1)(b)) for the account and your sessions; our legitimate interest in improving the product (Art. 6(1)(f)) for the usage events.

Cookies

• Facilitators: sign-in session cookies and a last-activity timestamp that signs you out after 8 hours of inactivity.
• Results viewers: entering a results password sets a signed cookie for that one session, valid 24 hours.
• Participants: no cookies. No analytics or tracking cookies anywhere on the site, which is why there is no cookie banner.

How long we keep things

• Answers: until the facilitator deletes the session or the auto-delete period they set has passed.
• Deleted sessions: 30 days in the recycle bin, then purged.
• Rate-limit hashes: 24 hours.
• Facilitator account: until you delete it.
• Usage events: 12 months.

Who processes data for us

All processing happens in the EU. Our subprocessors:

• Supabase (database, authentication, realtime) — Frankfurt, Germany.
• Vercel (application hosting) — functions run in Frankfurt, Germany.
• Resend (transactional email: sign-in links, results reports you choose to send).
• PostHog (usage events for facilitators, as described above) — EU cloud.

Data is served over HTTPS. Session pages are excluded from search engines. Aggregated results travel to the presenter screen over authenticated channels; individual answers never leave the server unaggregated, except in the facilitator’s own export, where participants appear as anonymous numbers (P1, P2, …).

Your rights

You can ask for access to, correction or deletion of your data, restriction of processing, or a copy in a portable format (GDPR Art. 15–20), and object to processing based on legitimate interest (Art. 21). Facilitators can export everything in their account and delete it themselves from the dashboard; for anything else write to privacy@survex.me. You also have the right to complain to a supervisory authority.

Participants: because we hold nothing that identifies you, we cannot find “your” answers to show or delete them — that is the point.

Questions

Ask the facilitator who invited you, or write to privacy@survex.me — the answer to “do you store X?” should always be on this page.