Privacy
What this site stores about you, why, and how to get rid of it. Last updated 7 August 2026.
Who is responsible
This site is run by Mikkel Hansen as a personal professional site. For anything on this page — including a request to see or delete your data — write to acid9381@gmail.com.
What is stored, and when
You can read every page here without signing in, and nothing is stored about you if you don't.
No access logs are kept. The server does not retain a record of which pages were visited, or from where.
Signing in with Google creates a record. It happens automatically the first time, for any Google account — there is no separate registration step. The record holds:
- your email address
- your name, as Google supplies it
- a display name — initially your name, and changeable on your profile
- the identifier Google uses for you (an opaque subject id)
- when the record was created and last changed
That is the whole of it. There is no profiling, no automated decision-making, and nothing is sold or shared for advertising.
Why, and on what basis
The record exists so the site can recognise you between visits and show the name you chose. The lawful basis relied on is legitimate interests: running a sign-in at all requires knowing who signed in, and the data is the minimum that needs. If you would rather it did not exist, delete it — see below — or simply do not sign in.
How long it is kept
Until you delete it. There is no automatic expiry. Signed in, you can remove the record yourself from your profile; it is deleted immediately and you are signed out.
Deleting is not opting out. If you sign in again afterwards, a new record is created in the same way as the first — because signing in is what creates it. Deleting removes what is held now; it does not prevent a future sign-in from storing it again.
Who else is involved
- netcup (part of the Anexia group) hosts the server, in the EU. They hold the data on our behalf under a data processing agreement.
- Cloudflare provides DNS for the domains — it answers the lookup that turns the name into an address. Traffic then goes directly to the server rather than through Cloudflare.
- Google handles the sign-in itself. That part is between you and Google, under their own privacy policy — this site receives your email, name and subject id as a result of it.
Cookies
No analytics, no advertising, no third-party scripts — the site loads one stylesheet and one script, both its own. The only cookies are the ones sign-in needs:
.DoktorHansen.Site— your signed-in session.DoktorHansen.Site.SignedOut— a short-lived marker so signing out does not bounce you back in- an antiforgery cookie, which protects form submissions
Your theme choice is kept in your browser's local storage. It stays on your device and is never sent to the server.
Your rights
You can ask to see the data held about you, to have it corrected, or to have it erased; you can object to it being processed, and ask for a copy in a portable form. Erasure is the one you can do yourself, immediately, from your profile. For anything else, write to acid9381@gmail.com.
If you think the data is being handled wrongly, you can complain to your national data protection authority.
Changes
This page describes how the site works today. If that changes — a new provider, a different arrangement for traffic, anything else recorded here — this page changes with it, and the date at the top changes too. There is no mailing list to notify, because no address is kept for that purpose.