Build Sovereign is a blog about data sovereignty — data ownership, GDPR, privacy, and European tech. It is published under the Build Sovereign brand of RightThing Studio, a registered European company.
The author’s pseudonymity
Build Sovereign is written by a single author who publishes under a pseudonym. The byline on every article is “Build Sovereign” — the brand — not a personal name.
This choice is deliberate. This blog argues for data sovereignty, including the author’s own right to control their personal data, including identity. Pseudonymity is a sovereignty practice, not an evasion: the author’s identity is controlled by the author, not exposed as a byline artifact on every page.
RightThing Studio (a registered European company) is the legal entity readers and B2B counterparties contract with. The pseudonymity is public, not commercial — the about page states it plainly, and the legal page names the entity behind the brand.
The sovereignty thesis
A blog about data sovereignty must itself embody the sovereignty it argues for. The blog’s own infrastructure is the first argument it makes, before a single word of content is read:
- Source hosted on GitHub (canonical); a future migration to a EU non-profit forge is reserved but not pursued now.
- Built on the same EU VPS that serves it, via the author’s existing deployment pattern (Ansible + make + compose).
- Served from a self-hosted EU VPS with nginx + Let’s Encrypt.
- A strict Content-Security-Policy header is set via nginx.
- Fonts from Bunny Fonts, EU-hosted, zero-logging.
- Analytics via self-hosted, cookieless Umami on a separate EU VPS — no third-party SaaS.
- No third-party runtime dependencies on reader data.
The colophon documents these choices in full.
Contact
- Email: build-sovereign@proton.me (ProtonMail, EU-jurisdiction encrypted email)
- X: @buildsovereign
No contact form is provided — the blog is a static site served from a self-hosted EU VPS and does not run server-side processing for form handling.