Security
The controls we use today.
A short summary of how Lawbooks protects client matters and drafts. If you find a problem, please tell us.
Encryption
- HTTPS for every page and API call
- Database and file storage encrypted at rest by our provider
- Third-party integration tokens encrypted again by Lawbooks before they are stored
Access
- Sign in with email and password or Google
- Row-level security on every table, so accounts can't read each other's data
- Webhooks from Stripe, Slack, Microsoft and WhatsApp are signature-checked before anything is saved
Reporting a problem
- Email security@lawbooks.io with what you found and how to reproduce it
- Please give us a chance to fix it before you share it publicly
Ready to see Lawbooks in action?
Talk to our team or explore pricing and the Lawbooks PC.
