Security and data · updated 2026-09-07
Where your files go, who can see them, and how you leave.
Specific practices rather than reassurance. This page is updated whenever the practice changes, and the date of the last change is printed on it.
01
Access
A workspace belongs to one organisation. Only invited internal users can sign in; counterparties are labels on a record and never receive access or messages.
- Role-based access within the workspace; owners can be reassigned by an administrator
- Every confirmation, edit, reassignment and export is recorded with who did it and when
- Removing a member reassigns their agreements and stops pending reminders to them
02
Files and processing
Uploaded originals are stored immutably and encrypted in transit and at rest. Extraction runs on the document you uploaded; the excerpt shown beside each term is the actual text from that file.
- You must be authorised to upload a document; the product asks you to confirm this
- AI processing uses documented providers and retention terms listed in the privacy policy
- No contract text, filenames or counterparty names are sent to marketing analytics
03
Retention and deletion
Records and files are kept for the service term and the published retention window. You can delete an agreement at any time, and the deletion is recorded.
- Deleted files are removed from primary storage promptly and from backups on a stated schedule
- Read-only export access after service end follows the published retention policy
- Customer material is not used to train a model
04
Export and portability
Leaving is a button. Export original files, the register as CSV and every confirmation as JSON, with source references intact.
- Exports are available throughout the service term, not only at cancellation
- The CSV keeps the same column meanings as our published spreadsheet template
- No call, no retention offer, no waiting period
05
Reliability of reminders
Confirmed reminders run on deterministic application logic, independent of the AI allowance. Delivery is retried and reconciled; a failure is shown in the action queue and can be reassigned.
- A reminder that could not be delivered is never marked sent
- Reminders for a superseded rule are cancelled; sent ones remain in history
- Reminders continue until the exact service-end timestamp you can see in settings
06
Connectors and e-signature
Document connectors and e-signature use explicit authorisation, narrow scopes and visible revoke or reconciliation states.
- External files are selected for import review; a whole drive or tenant is not ingested
- Provider completion returns an artefact but does not confirm legal validity or contract terms
- HubSpot receives summary fields and links by default, not contract text
Honesty
What we do not claim
- We do not claim certifications unless the report exists and is available under the stated process.
- We do not describe the product as a system of legal record. It is agreement administration.
- We do not claim validity, enforceability, legal sufficiency or guaranteed delivery of notices.
Common questions.
Read the policy, then judge the product.
The privacy policy and terms are short and specific. The sample agreement shows exactly what a record holds and what leaves the workspace.