What is a Encryption at Rest?

It pairs with encryption in transit, which protects data while it moves across a network. In transit is what HTTPS gives you on a website. At rest is what protects the copy sitting in a database or a backup afterwards. Both are needed, because they defend against different failures: interception on the wire versus someone getting hold of stored media.

In practice, encryption at rest is a baseline expectation rather than a differentiator. Major cloud platforms provide it by default, and security frameworks including SOC 2 and HIPAA treat it as standard. The more interesting questions are how keys are managed, who can access them, and whether backups are covered too — encryption is only as good as the key handling around it.

For a website chat widget the stored data is conversation transcripts and captured contact details, which is exactly the kind of thing that should never sit in plain text. Clerkzo is SOC 2 Type II examined, GDPR compliant and HIPAA assessed, so this sits alongside the other controls an IT reviewer will look for.