Security
Finance data, with a record of every change.
Furrow is built so a reviewer can answer who changed what, when, and why, months later. These are the controls behind that promise.
The controls we run today.
Each control is described as it works now. Anything still being built is listed on the next section, not here.
- Encryption
- Data is encrypted in transit with TLS 1.2 or higher and at rest on the storage it lives on. Keys are rotated on a fixed schedule.
- Access by role
- Viewer, bookkeeper, controller and admin roles limit who can match, approve or lock a month. Access is removed when a person leaves the workspace.
- Audit trail
- Every match, approval, edit and export is written to an append-only log with the user, the time and the previous value. Entries cannot be edited, only added to.
- Locked months
- A signed-off month is locked. Changes after lock are made as adjusting entries, and the original stays visible in the log.
- Backups
- Workspaces are backed up each day and copies are kept in a second location. Restores are tested each quarter and the result is recorded.
- Incident response
- Customers are told within 72 hours of a confirmed personal data incident, with what happened, what data was involved and what we changed.
Where your data lives.
The region is chosen when a workspace is created and stays fixed. Support staff see data only when a customer grants access for a support request, and each access is logged.
Retention for the audit trail is seven years from the date of each change. Deleted workspaces are removed from live systems within 30 days and from backups on the normal rotation.
Certifications: we are preparing for an independent security audit. We will publish the report when it is complete, and not before.
Questions from your security team?
Send the questionnaire you already use. We answer in writing and share the current policy documents under an NDA.