Export and Switching

Personal account export provides application records in JSON, including saved content and related records available to that account. Authorised organisation export provides structured organisation records in JSON. Original uploaded files are downloaded separately in their original format where available. Supported report functions provide readable exports such as Markdown or Word documents; a report export alone is not a complete workspace migration.

Exportable data include Customer inputs and outputs and the related metadata necessary for their use, to the extent held and lawfully releasable. Exclusions are the Provider’s proprietary source code, model weights, trade secrets unrelated to the Customer’s data, security information whose disclosure would create a material risk, and another customer’s data. An exclusion cannot be used to obstruct transfer of the Customer’s own exportable data or mandatory rights.

The standard JSON export and original-file downloads are separate operations; we do not describe them as a tested one-click migration to every destination. For an institutional exit, identify the workspace, all data classes, formats, file inventory and integrity checks in the exit schedule. Any additional format or destination integration must be agreed and verified.

Use the available export controls while the account is active. For a coordinated switch or data retrieval after termination, send a request to contact@veritasask.com identifying the Customer, authorised representative, workspace and intended destination or return method; do not attach the complete confidential dataset. We verify authority and agree a secure delivery route. A destination provider may participate when authorised by the Customer.

Where Chapter VI of Regulation (EU) 2023/2854 applies, the Customer can switch to another provider of the same service type, move exportable data and digital assets to its own infrastructure, or erase exportable data as permitted by that Regulation. Any contractual notice period for initiating the switch shall not exceed two months. The standard transitional period shall not exceed 30 calendar days after that notice period, subject only to the Regulation’s permitted extensions and the Customer’s applicable extension rights.

If a 30-day transition is technically unfeasible, we must notify the Customer within 14 working days of the switching request, explain and substantiate why, and identify an alternative transition period which shall not exceed seven months. We shall provide reasonable assistance, relevant information, security and continuity during the applicable transition and cooperate in good faith with the Customer and authorised destination provider. The parties remain responsible for their respective migration tasks. A different platform need not reproduce every proprietary AI function identically.

The post-transition data-retrieval period is at least 30 calendar days where the Data Act applies. We shall not erase exportable Customer Data before that period ends unless the Customer requests earlier erasure or law requires it. Completion and termination follow the applicable switching process; after retrieval, deletion follows the Customer’s instructions and the DPA retention schedule, subject to lawful retention.

Standard self-service exports carry no separate export fee. Before 12 January 2027, any separately agreed switching charge may not exceed the directly incurred costs permitted by the Data Act and must be disclosed in advance. From 12 January 2027, no switching charge is imposed where that prohibition applies. Ordinary service fees and any lawful, transparently agreed early-termination charge are distinct; they must not be used to evade mandatory switching rights. Bespoke work outside the mandatory switching obligations requires a separate accepted scope and price.

An account deletion request is distinct from cancellation of subscription renewal or a switching request. Export needed records first. A legal duty to retain a particular record does not authorise indefinite retention of the entire workspace. Authentication identities, backups and supplier copies have their own completion steps described in the Privacy Policy and DPA Schedule D.