Trust
Security and data
How your documents are protected, who can reach them and how we handle your data.
Rowland is built for documents that matter: leases, title, ownership and revenue. Here is how they are protected.
Independently audited
Rowland is SOC 2 Type 2 audited. Request the report at trust.rowland.ai (opens in a new tab).
Your data
- Encrypted in transit and at rest.
- Never used to train AI models.
- Isolated by organization. Every API key belongs to one organization, and every request is limited to that organization's data. Asking for something outside it returns
404, so a key cannot even learn that it exists. - Deleted when you delete it. Deleting a document removes its file, pages and extractions.
API keys
- Rowland stores only a fingerprint of each key, never the key itself.
- Keys can expire on a date you choose.
- Keys are issued by the Rowland team, and admins can revoke them in the app at any time.
- Rowland may disable a key that has been published.
Webhooks
Every webhook is signed and timestamped, so your server can reject calls that did not come from Rowland, or that are replayed.
In the app
- Access controls on every project and document.
- Review flags, so a person checks what needs checking.
- WORK's Row Bots ask before they act and keep an audit trail.
Operations
- Continuous vulnerability monitoring, alongside regular security audits.
- Live service status at status.rowland.ai (opens in a new tab).
Questions from your security team? Email support@rowland.ai.
