Data processing statement
2026-09
This statement describes what data Ciliclaw Digital Workforce processes, where it is held, who can reach it, and what each side is responsible for.
1. Where data is held
Under self-hosted deployment, company documents, code, knowledge, conversation records, task data, and execution logs all reside in the company’s own environment. We hold no copy of them.
Under hybrid deployment, the same data still resides in the company environment; only model inference requests reach the model service the company has approved. The company should satisfy itself as to that service’s own data terms.
2. Categories of data
Identity and organisation: employee identifier, department, role, and grants, used for permission decisions.
Task data: the request you made, the plan, each tool call and its result, and the output produced.
Knowledge: the policies and documents a company uploads, with their versions, owners, and validity windows.
Execution records: local file, command, script, and application actions, kept for replay and diagnosis.
3. Access boundaries
The company is the first boundary. Every piece of data, page, and statistic is scoped to one company; nothing is shared or joined across two.
The same person in two companies is two identities; their departments, roles, permissions, and tasks are unrelated.
What an employee can reach is decided by their role and grants. Content they lack permission for is not shown, rather than shown and then refused.
4. Limits on our own access
Our people cannot reach company business content by default.
Entering a company’s scope to assist with an investigation requires the company’s grant, carrying a stated reason, scope, and time window, and expiring on its own.
Every access during such a grant is recorded and visible to the company at any time.
5. Retention and deletion
Retention periods are set by the company. Under self-hosted deployment, backup and destruction follow the company’s own procedures.
Departure follows an ordered path: disposition of work in flight, data export, confirmation of the retention or deletion policy, revocation of credentials and unbinding of runtimes, and archival of records.
6. What this website collects
This website uses no advertising or analytics cookies from third parties.
The name, company, role, and contact details you submit through the form on this site are used only to contact you and arrange a demo. They are not used for anything else and are not shared with third parties.