About
Why fixGDPR exists
A few years ago I was building a SaaS product. I had a cookie banner, a privacy policy I copied from somewhere, and assumed that was enough. It wasn't.
I received a legal threat — a formal letter from a lawyer representing a data protection consultancy, claiming my site was in violation of GDPR and demanding a settlement. I had no idea what I'd done wrong, no idea what to fix, and no tool that could tell me.
I spent days reading through regulation text, DPA enforcement decisions, and Stack Overflow threads to figure out what a compliant website actually looked like. What I found: most violations come down to the same handful of things — missing cookie consent, a privacy policy that doesn't say the right things, tracking scripts that fire before the user agrees to anything.
None of it is complicated once you know what to look for. But nobody had built a tool that just checks your site and tells you exactly what's wrong.
So I built it.
What fixGDPR does
You paste a URL. In about 30 seconds, fixGDPR crawls your site and checks 7 things regulators look at first: SSL, privacy policy, cookie consent banner, form consent, tracking scripts, terms of service, and contact information.
Each check gets a pass/fail with a plain-English explanation of what's wrong and why it matters. Pro users get exact copy-paste fixes tailored to their platform — WordPress, Shopify, Webflow, or custom code.
It's not a law firm. It's not legal advice. It's a fast, honest technical audit — the thing I wished existed when I got that letter.
Who built this
My name is Mor Ofir. I'm an indie developer. fixGDPR is a solo project — one person building, shipping, and supporting it.
I built this because I needed it, and I think a lot of other developers and startup founders are in the same position I was: trying to build something, not a compliance expert, and just wanting to know if their site is going to get them in trouble.
If you find a bug, have a feature request, or just want to say hi — email works.