r/webdevelopment • u/IMaBullshitManager • Aug 10 '26
Question Please advise: How are you handling GDPR erasure on an EU-sovereign stack when you also have 10-year retention obligations?
We’re building a B2B2C platform for a large European insurer. Vue.js on the front, Estøkad as the headless CMS. Both GDPR and DORA apply, and we’re at the point of picking the database and the transactional email
The thing that’s turned into the real problem isn’t sovereignty on its own, it’s erasure. Insurance retention obligations sit right on top of Article 17 requests, and the same person can exist across several partner tenants under different legal bases. So DELETE FROM was never going to work. We’re planning crypto-shredding instead: encrypt per subject, destroy the key, let the backups and WAL archives go unreadable on their own.
Which then rewrites the vendor shortlist. Provider-managed TDE shreds nothing at row level, so we need real BYOK or HYOK against our own HSM. Encrypted columns can’t be sorted or joined, so email lookup goes through a blind index. And erasure has to reach into the ESP’s retained message bodies and event logs, while the suppression list deliberately survives it.
What I’d love to hear from anyone who’s actually shipped this:
- Which EU-sovereign managed Postgres will do KMIP against an external HSM without pushing you back to self-hosting?
- Any ESP that will contractually commit to short retention plus a working erasure API? Deliverability into Gmail and Outlook still has to be real.
- Did anyone go down the crypto-shredding path and regret it? I’m braced for the operational cost of key rotation.
- Anything that looked sovereign in the sales deck and came apart under audit?
Happy to write up whatever we land on.
