Content Snare is ISO 27001 certified and encrypts your data both in transit and at rest. You also control who can open each request, which answers stay hidden, and how your team signs in.
ISO 27001 certification
Content Snare is certified against ISO/IEC 27001:2022, the global standard for keeping information secure. An accredited, independent auditor checks our systems, policies and processes against it, with a surveillance audit every year and full recertification every three. Our certificate is public, so your compliance team can view it on IAF CertSearch. Audit evidence and our other ISO 27001 documentation are available through our Trust Center on the Pro plan or above, under a non-disclosure agreement, and our Security and Compliance page sets out our wider practices.
How your data is encrypted
Your data is encrypted both while it travels and while it is stored. In transit, the connection between your client's browser and Content Snare is protected with TLS. At rest, it stays encrypted where we store it, and stored answers are encrypted again with a key unique to your company, held in a secure vault separate from the application itself. For where your data is physically held, see where client information is stored.
Controlling who can open a request
By default, a client reaches their request through a link that is long, random and effectively impossible to guess. While the request is open, that link works on its own with no login, so treat it like a key. Only send it to the person it's meant for, and don't post it anywhere others could see it.
For anything sensitive, you can add more protection:
- Require a PIN. The client enters a short code as well as opening the link. A PIN is a light lock on top of the link rather than a password, so use it as an extra step, not as your only protection.
- Turn off Allow access without logging in. The client then signs in with an account instead of opening the link directly.
- Mark a question Confidential. Your client can answer it but cannot see the answer again after submitting, and someone reviewing the request re-enters their password to read it. This suits a single sensitive answer, like a tax file number, rather than the whole request.
The client access and security settings guide covers when to use each, and confidential fields has the full detail on that setting.
Secure your own account
Two-factor authentication adds a second step to your login, so a stolen password on its own is not enough to get in. You can set it up using a code from your authenticator app. Any team member can turn it on for their own account, and an Administrator can require it for everyone on the team. Your clients sign in to their own accounts and are not affected by it.
Getting your data deleted
You can ask us to remove your data at any point, and we will. Our team handles each deletion as a logged request. Our Privacy Policy and Data Processing Agreement explain how we handle your data and how long we hold it.