it’s 2026. build like you’re already going to get hacked, because sooner or later you probably will
collect less. only keep the customer data you actually need. anything you never store can’t leak
encrypt everything you keep. not just passwords and card numbers: names, emails,…
Commit
52b1750
the encrypt everything needs some better clarification here. Doing it at the application layer adds massive architecture and performance overhead. Industry best practice is at the storage or engine level. Keep the application layer to PII, secrets and anything else truly sensitive.
The biggest issue I typically see is even when data is correctly encrypted, the decryption key is left on the same box in a .env file instead of being physically separated in a KMS
commit 52b1750