[donatj]

I've got a side project I've been working on for over 12 years, on and off. About a year in, a very popular competitor popped up, and it was roughly as good as what I was working on so I gave up - for a year or two.

Then they closed their API and had some PR drama so I started up again. Rewrote the whole thing. I've got it about 90% of the way there, and I was getting ready to open it up for a public beta and suddenly GDPR happened.

I don't even want names if I can avoid it, but the core data of the product could be construed to be PII, which means I want to get some sort of encryption on it before I open it… And I just haven't come up with a way to do that that doesn't involve rewriting the whole thing.

So right now, I've got a project I spent 12 years on that only I am using - and using heavily - and love. I generally put a couple hours a week into it.

If anything it's been a fun testbed for keeping my frontend skills up to snuff, especially as I've moved from full-stack to backend in my professional career over the last 5 years.

[NicoJuicy]

Cloud DB with encrypted columns is not enough?

( Other options exist)

[donatj]

If I'm going to do it, I want it in a way where it's encrypted per-user, using something not stored in the database like a client side hash of their password or something.

I don't want the possibility a miswritten SELECT potentially revealing anything.

I don't want to be able to read their data, at all.

[NicoJuicy]

Normally that would be a salt or a certificate. No?

It protects against rainbow tables. So I'm not sure sure why you wouldn't go down that road.