Data formats and switching
Last updated: 13th October 2026. This page should be read with your agreement with causaLens; if anything on it conflicts with that agreement, the agreement prevails.
This page describes the categories of data available for export from causaLens-hosted services. For Customer-Hosted Deployments, customers control their own hosting; any separately agreed causaLens-hosted services remain subject to the applicable export arrangements. Exportable data includes Digital Worker definitions and customer data, including inputs to and outputs of Digital Workers. Files and formats are agreed for each Digital Worker according to the workflow and the customer's requirements. There is no single file type or version used across all Digital Workers. Only data retained for the relevant Digital Worker is included.
How to export your data or switch
To request an export, contact your causaLens account contact or [email protected]. We deliver the data as files through an encrypted transfer method agreed with you, such as a secure storage bucket or SFTP.
- Digital Worker definitions (rules, roles, skills, prompts, workflows, business logic, knowledge files and configuration): available on request at any time during the subscription and for 60 days after it ends.
- Post-termination copy: request exportable data in writing within 60 days after the subscription ends. We use commercially reasonable endeavours to deliver a copy within 30 days of the request, provided all outstanding fees have been paid. Data is deleted within 90 days after the later of the end of that 60-day period and delivery of any requested copy, subject to routine backup cycles, our 1-year log retention and any retention required by law. For hosting covered by the EU Data Act, you may also retrieve your exportable data for 30 calendar days after the hosting arrangement ends.
Live hosting exit: for hosting covered by the EU Data Act, give two months' written notice to request deletion of your exportable data or transfer as part of a switch to your own environment, including infrastructure you procure from another cloud provider. We provide relevant information and reasonable assistance so you can complete the deletion or switch within 30 calendar days after the notice period. You may request a one-time extension of the transition period. If completing the switch within 30 calendar days is technically unfeasible, we will notify you within 14 working days of your switching request, explain the technical reasons and specify an alternative transition period of no more than seven months. During the transition we act with due care to maintain continuity, security and service provision. Ending hosting does not affect other subscribed services or their fees; any extension of the subscription term during the transition is charged on a prorated basis. We may charge agreed professional services rates for work beyond the information and assistance required to complete the deletion or switch, subject to applicable switching-charge restrictions. Before 12 January 2027, any reduced charges for covered switching must not exceed directly incurred switching costs. From 12 January 2027, no switching charges apply to covered switching. For hosting not covered by these switching provisions, 30 days' written notice applies, with reasonable transition assistance at the agreed professional services rates.
You can retain and use Digital Worker definitions to re-create or re-implement your Digital Workers elsewhere. The causaLens software and its runtime, reliability and orchestration technology remain ours and require a current subscription. Prompts and configuration may need changes to work on another platform. Reasonable transition assistance is available at the agreed professional services rates, subject to any applicable EU Data Act switching rights.
Register of exportable data
Each Digital Worker is designed for a particular workflow. The workflow determines which inputs it uses, which outputs it creates and the file types it needs. Formats are flexible and selected to suit the workflow and the customer's requirements. For example, a workflow may use Python files, Markdown or Word documents, JSON, CSV or other file types. These examples are not an exhaustive list. Data can be exported in its existing format or another format agreed with the customer, subject to any technical limits.
| Data | What it covers | Export format |
|---|---|---|
| Customer-supplied files and datasets | Documents, source files and datasets supplied for the workflow and retained in the service; connected-source data only where held | The original supplied file type, or another export format agreed with the customer |
| Digital Worker rules, roles and configuration | Customer-specific workflow logic, rules, roles, skills, prompts, knowledge files and configuration | Open, machine-readable files suited to the workflow definitions, such as Python, Markdown, JSON or other text formats, as agreed with the customer |
| Digital Worker inputs | Retained task instructions, uploaded files and other data used by the workflow | The format used or retained by the workflow, such as a document, spreadsheet, code file or structured dataset; another export format may be agreed |
| Digital Worker outputs | Workflow results, such as code, reports, documents, datasets or other files, where retained | Workflow-specific formats, for example .py, .md, .docx, .json or .csv. These are examples; the format is agreed around the workflow and customer requirements |
| Run records (metadata) | Timestamps, steps taken, tool calls and outcomes for each run | A format agreed for the retained run history, such as JSON, Markdown or trace-log output, where available for the workflow |
Where these formats are used, they follow open standards: JSON (RFC 8259), CSV (RFC 4180), Markdown (CommonMark), Word and Excel files (ISO/IEC 29500) and PDF (ISO 32000). Code is exported as plain UTF-8 text.
Exports exclude the causaLens software and its underlying runtime, reliability and orchestration technology, and protected provider or third-party materials. Security-sensitive service data is excluded where exporting it would expose the service to cybersecurity vulnerabilities. These exclusions do not remove your Digital Worker definitions or other exportable customer data.