royeyal.com

Privacy

This site has no analytics, no tracking pixels, no embeds and no forms. It does not know who you are, and neither do I.

Last updated

What this site collects

Nothing that identifies you, and nothing I ever see. There is no analytics script on any page — no Google Analytics, no Plausible, no self-hosted alternative. There is no dashboard behind this site telling me you visited, which page you read, or how long you stayed.

There is also nothing to fill in. The contact control in the footer copies my email address to your clipboard; it does not submit anywhere. Writing to me is a normal email from your own mail client, and the only thing I learn is whatever you choose to put in it.

No consent banner, on purpose. A cookie banner is for asking permission to do something you would otherwise have to be asked about. Nothing here qualifies, so putting a banner up would be theater — and it would imply tracking that is not happening.

Cookies

This site sets none of its own. The only cookie that can appear comes from Cloudflare, which serves the site:

__cf_bm
Cloudflare's bot-mitigation cookie. It is set on some requests to tell automated traffic apart from human traffic, expires after about 30 minutes, and carries nothing about you or your visit that outlives it. It is a strictly necessary security cookie, which the ePrivacy rules exempt from consent — which is the other reason there is no banner.
cf_clearance
Only if Cloudflare ever challenges your connection, to remember that you passed. Most visits never see it.

At the time of writing, a plain request to this site returns no cookie at all — those two are what Cloudflare's protections can set, not a list of what you will get.

Server logs

Serving a page means receiving a request, and a request carries information whether or not anyone wants it to. Cloudflare handles that on my behalf, as a processor:

What a log line holds
Your IP address, the URL you asked for, the time, your browser's user-agent string, and the response code it got back.
What it is for
Delivering the page and keeping the site up — rate limiting, abuse handling, and diagnosing outages. Not audience measurement.
How long it lives
Cloudflare retains it for a limited period under its own policy and then discards it. I do not export it, keep a copy, or join it to anything else.

Cloudflare's own handling is described in its privacy policy.

Fonts, images and everything else on the page

All of it is served from this domain. The three typefaces are self-hosted rather than pulled from Google Fonts, which matters here for a reason beyond speed: a webfont request hands your IP address to whoever serves the font. Nothing on these pages makes a request to a third party, so there is no such disclosure to make.

Links to other places

The site links out — to LinkedIn, to GitHub, and to sites I have worked on. Following one takes you somewhere I do not control and whose privacy practices are its own. Nothing from those places is embedded here, so none of them can see you until you click.

Your rights, and how to use them

If you are in the EU, the UK, California or anywhere with comparable law, you have rights of access, correction, deletion and objection over personal data held about you. For this site I am the controller, and you can exercise any of them by writing to hello@royeyal.com.

A straight answer about what that gets you: because nothing identifying is stored, an access or deletion request usually has very little to act on. The honest response to "what do you hold on me" is normally "nothing" — and if you ask, that is what I will tell you, rather than sending a form back.

If this changes

It changes when the site does. If I ever add a form, an analytics tag or an embedded third party, this page gets updated in the same change that adds it, and the date at the top moves. There is no version of this site where the code and this page disagree and I find out later.