Privacy

The short version: no name, no email, no stored IP, an account that's a 16-digit code rather than an identity, and a delete button that actually deletes. The rest of this page is the detail behind that.

What we don't collect

No name. No email address. No phone number. No IP address is ever stored — not even a hashed one; an unsalted hash of an ordinary IP address is trivial to reverse, which defeats the point of hashing it in the first place.

No location beyond country, and country is used to route your session, not saved on any row that also holds an opinion. No third-party script, tracker, or connection of any kind loads on a page where you're answering a question — your browser's own network rules enforce that, not just a policy we could quietly drop.

Your account

Signing up gives you a 16-digit code — that's your identity here, not your name or your email. Behind the scenes it's paired with an internal address that isn't a real mailbox and that nothing is ever sent to; ActPol has no email-sending capability at all, for any account, for any reason.

That trade is real and stated plainly at signup: there's no “forgot my code” email, because there's no email. Lose the code and you lose access to that account's history. What you get in return is an account that was never, at any point, tied to who you are.

Keeping your code

At the end of registration you're shown your code once, and offered ways to hold onto it that never leave your browser: let your password manager save it, download a credential card with a QR code, email it to yourself from your own mail client, or print it. Every one of those happens entirely on your device — we don't receive, see, or log an email address at any point, including when you email your own code to yourself.

Exporting and deleting your data

From your results page, you can download everything recorded under your account — every submission, every answer, every score and band — as a file, any time, with one click.

You can also delete your account outright: your account, and every submission and answer tied to it, removed permanently and immediately. There's one thing it doesn't do — if a cycle you took part in has already published its results, those published numbers don't change. They're anonymous aggregate counts by then, not your data, and deleting your account can't retract a number that's already gone out and possibly been cited.

What we publish about you

Never your account, never your code, never anything that points back to it. Written reasoning you submit is reviewed before any of it can appear publicly, and even then only ever as an anonymous excerpt — never attributed to an account. No opinion result is published at all — in total or for any band — from a cycle without enough respondents behind it; a thin cell simply doesn't get a number.

That threshold is already built into the system. What's still ahead of us is running an actual published cycle through it, which hasn't happened yet.

Where your data lives, and for how long

ActPol's database will run in the EU — Hungarian respondents, GDPR, and the fact that this is a political-opinion product all point the same direction. That infrastructure isn't live yet; this page will be updated the moment it is.

Retention: records used to slow down abuse are deleted within hours, on purpose, so that one day's traffic can't be lined up against another's. Aggregated, published results are kept indefinitely — that's the actual output of this product. We haven't yet finalised the retention window for raw written reasoning text, and we'd rather say that plainly than put an invented number on this page.

If we ever add email

If ActPol ever offers an email-based account, it will be a genuinely separate option — opt-in, and applied only going forward. It will not retroactively attach an email, or any other identity, to answers an anonymous account already gave. Turning an anonymous archive into a personal one after the fact is the one mistake in this area we're not willing to make.

Before this holds anyone's real data

A written incident-response plan — who decides, who's notified, and the clock GDPR puts on that — will be in place before this ever handles a real respondent's answers, not drafted after something goes wrong. The same goes for a data processing agreement with every company ActPol's data passes through, including whoever hosts this site and its database.