Hi HN!<p>I've built Vaulty (<a href="https://vaulty.co" rel="nofollow">https://vaulty.co</a>) - open source (Go) forward/rewerse proxy that encrypt/pseudonymize/tokenize/mask/hash data between two systems talking HTTP(S):<p>- browser -> backend API
- backend -> API of 3rd party service
- backend <-> backend<p>It transforms specific attributes/fields of JSON/XML/Form transparently for sender and receiver (no code changes needed) based on transformation rules. Using Vaulty you can:<p>- prevent developers from accessing sensitive customer data
- protect sensitive data before it reaches your backend
- reduce compliance scope (e.g., PCI DSS)
- contain personal information within a country's borders
- and just make your systems more secure :D<p>Here are two cookbooks (demos) to show how Vaulty may be used:<p>- <a href="https://docs.vaulty.co/cookbooks/safe-sensitive-data-import" rel="nofollow">https://docs.vaulty.co/cookbooks/safe-sensitive-data-import</a><p>- <a href="https://docs.vaulty.co/cookbooks/email-list-with-protected-emails" rel="nofollow">https://docs.vaulty.co/cookbooks/email-list-with-protected-e...</a><p>I would appreciate your feedback! If you see how you may use Vaulty, let me know! I'll help you with Vaulty adoption.