Last updated: 2026-10-26
Security Practices
Clerato uses a controlled workflow for handling project data and documents. Specific security, data-handling and retention requirements are agreed before live client documents are accepted.
Clerato is an early-stage service. It does not currently hold SOC 1, SOC 2, ISO 27001 or similar certifications, and this page does not claim any.
Who has access to documents
Access to project data is limited to named, authorised users. Accounts support multi-factor authentication (TOTP) and role-based permissions.
Client data is separated by organisation within the application, and each client's work is kept in its own workspace. No subcontractor has access without prior disclosure and client approval. Clerato does not access client production systems by default.
Storage and deletion
Uploaded documents are stored in private (non-public) storage and transferred over encrypted connections. The document transfer method, retention period and access conditions are agreed for each engagement before live client data is processed.
After the agreed retention and correction window, documents are deleted or returned. Deletion is a documented manual procedure with an audit trail; there is no automatic scheduled deletion. Provider-side copies and backups follow their own retention and are listed in the engagement's data-processing terms.
AI data processing
AI may support first-pass extraction, but it does not independently create the delivered record. AI suggestions are staged for review, and approved values are only written after a human action. Every delivered record is subject to human review before release.
Where AI processing is used, document content is sent to a third-party AI provider. That processing is not restricted to the EU, so Clerato does not claim EU-only processing, and does not make blanket no-training or no-retention claims. Provider, location and retention terms are disclosed and agreed for each engagement.
Technical controls in place
The following controls are implemented in the application:
- Organisation-scoped data separation and role-based permissions.
- Multi-factor authentication for user accounts.
- Signed, size- and type-checked uploads into private storage.
- Audit logging of uploads, downloads and key record changes.
- A file that has not been cleared cannot be downloaded or sent to OCR or AI processing.
- Source references, field history and versioned delivery packages for each record.
Current status and limits
Clerato does not currently accept real client documents. Controls that must be in place first include active malware scanning of uploaded files, tested backup and recovery, tested deletion, and agreed AI-provider and data-processing terms. Until then Clerato works with synthetic demonstration data only.
Clerato does not claim EU-only processing, tamper-proof audit logs or any security certification, and does not provide legal advice.
Client review
More detailed information about Clerato's application controls, data flow, processing providers and operating practices can be provided during client security or procurement review.
Questions: office@clerato.com