Storing Sensitive Data

Due to the sensitive nature of storing data such as credit cards or SSNs, here are some general notes for best practices when adding such data to your Knack database.

It is generally not recommended to store data such as credit cards or SSNs due to their sensitive nature. However, some customers may choose to store SSNs based on the level of encryption that we currently provide.

It is important to note that you are responsible for securely storing any sensitive data added to your database.

​In terms of recommended practices and additional security measures, customers often opt for using anonymous data, such as unique ID numbers, instead of SSNs. Additionally, some customers may choose to employ jQuery/Javascript to mask their SSNs, providing an added 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.