Privacy

Data controller

Codeetry SRL

Contact

privacy@whatweearn.eu

Address

8 Boucle Jean-François Breuer, 1435 Mont-Saint-Guibert, Belgium

Enterprise number

0880.250.749

There is no account, no login and no identifier of any kind attached to a response. When you submit, the server stores your answers and returns nothing: no id, no token, no receipt. There is deliberately no value you could later present to us that would point at your row.

Because of that, survey responses are not personal data, and the rest of this policy is mostly about the two places where personal data does briefly appear.

To stop the same person submitting fifty times, the server combines your IP address and browser with a secret that is scoped to a single calendar day, hashes the result one way, and stores only that digest. The address itself is never written to disk or to a log.

The digest cannot be reversed into an address, and because the secret changes daily and is discarded, the same visitor hashes to something different tomorrow. It cannot be used to follow anyone over time. Its only purpose is spotting a duplicate before midnight.

There is no free-text field anywhere in the survey. Every question is a list to pick from or a number, which means nothing personal can end up in the dataset by accident. Not a name typed into a comment box, not an employer mentioned in passing.

We never ask who you work for. Company size bracket and industry only.

The notification list is optional, is never part of a survey submission, and is stored in a physically separate database with its own credentials, in a separate provider account. There is no key, no timestamp and no shared value connecting the two, and no code in this project is permitted to open both connections. An automated test fails the build if any module tries.

Both databases record dates rather than timestamps, signups are recorded only to the week, and the subscriber table uses random identifiers rather than sequential ones, so a signup and a response cannot be matched by when they arrived or by the order they were written in.

The consequence is worth stating plainly: we can never email you about your own answers. Not as a policy, but because we genuinely cannot find them. Your address is used for two things: telling you when results publish, and telling you when the survey reopens.

Nothing is stored until you follow the confirmation link. If you never do, the address is deleted within a fortnight. Every email carries a one-click unsubscribe.

Your email address

Unsubscribe from any email, or ask us. We will delete it and confirm.

Your survey response

We cannot delete a particular response, because we cannot tell which one is yours. That is the direct cost of the anonymity above, and we would rather say so than pretend otherwise. Please be sure before you submit.

Any slice of the data with fewer than 5responses is withheld entirely, and a country’s figures are not published until it clears 60. Withheld figures are absent from the published files rather than hidden by the interface, so a display bug cannot leak them.

The downloadable dataset drops cities, bands experience into five-year ranges, rounds pay to the nearest €500 and withholds any combination of characteristics appearing fewer than 5 times.

Cloudflare Turnstile

Confirms a submission came from a browser rather than a script. It sees your IP address as part of that check. We chose it over a proof-of-work alternative because the realistic threat is somebody submitting invented salaries at volume, which proof-of-work does not stop.

Resend

Sends the confirmation and notification emails. Resend stores account data and logs in the United States under Standard Contractual Clauses and its Data Privacy Framework certification. We use it only to send: your address lives in our own EU database, never in Resend's contact storage.

Hosting

The site and both databases run in the EU. No analytics, no advertising, no tracking scripts, and no cookies, which is why there is no cookie banner.

If you think we have handled personal data badly, tell us first at privacy@whatweearn.eu, and we will answer.

You also have the right to complain to a supervisory authority without going through us. Ours is the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données). You may equally complain to the authority in the country where you live.

The mechanisms above are code, not promises. The suppression thresholds, the hashing, the two-database separation and the test that enforces it are all in the public repository. If this page and the code ever disagree, the code is what runs.