Storing sensitive data (credit cards, social security numbers, etc.)

Danielle Kellogg Updated by Danielle Kellogg

​Generally, we don't recommend storing data like credit cards or SSNs due to their sensitive nature. With this said, we do have customers that store SSNs based on the level of encryption that we currently offer. Ultimately, you're responsible for the storage of any sensitive data added to your database.​

​As far as best practices or additional measures, we've seen customers revert to using anonymous data, such as unique ID numbers rather than SSNs, for example. ​Also, some customers will use jQuery/Javascript to mask their SSNs for an additional layer of security.​

​Further, if you are storing sensitive data like social security numbers, we do offer a HIPAA plan which you can read more about here.

How did we do?

Is Knack GDPR compliant?

Will Knack sign an NDA (Non-Disclosure Agreement)?