I help teams prove what happens to their users' data.
Does your product say "we never see your data"?
Sooner or later a customer or auditor will ask you to prove it. Your privacy policy says what you promise. They want to know what in your system enforces it.
Three technologies can back that up:
- Reproducible builds show that the code you publish is the code you ship.
- Transparency logs keep a public record of every release.
- Remote attestation lets a server prove what it's running right now.
As a freelance engineer, I help teams design, build and maintain systems that use them.
Based in Germany. Happy to work with teams in compatible timezones.
How I can help
-
Verifiability assessment Five days, fixed price
What you claim, what you can prove today and what it would take to close the gap.
-
Make-it-verifiable sprint Up to eight weeks, billed by the day
Attestation and a verification flow for one service.
-
Verification retainer Two days a month
Reviews and threat models while you build.
What I'm building
I'm also building Verbond, a system that shows where your data could end up before the code that processes it runs.
A local runtime works today, and a remote runtime is planned for 2027.
It's in early access, and I'm looking for a few design partners.
Learn moreMake privacy claims you can back up
Join 800+ subscribers.
One email every few weeks.
I share what I learn building privacy-friendly systems. From confidential computing to Verbond and the occasional Go tip or trick. You can unsubscribe at any time.
