Data Portability

We publish this page pursuant to Section 11(16) of our Terms & Conditions and Article 25 of Regulation (EU) 2023/2854 (the "Data Act"). It sets out the categories of data and digital assets that can be ported out of Turbofy® during a switching process, the categories that are excluded from them, and the register of the data structures, data formats and interoperability specifications in which the exportable data are made available.

1. Categories of data and digital assets that can be ported

The following list is exhaustive. All of it can be exported by the customer at any time through the API provided by us, without assistance from us, and all of it is covered by the switching process under Section 11 of our Terms & Conditions.

1. Data in tables — all records stored in the tables of the customer's workspace, including every field value and the relations between records, together with the table definitions (fields, field types and relations) that describe them.

2. Assets in the file explorer — all files stored in the customer's workspace, both public and private, in the file format in which they were uploaded, together with their metadata such as file name, content type, size and folder.

3. Functions — the declaration and source of every function created in the customer's workspace.

4. App users — the end-user accounts created in the customer's apps, including their profile fields, group membership and status. Authentication credentials are not included; see Section 2.

5. Block code for apps — the source code of every building block of the customer's apps, including its entry file and sibling runtime files, together with the app, page and block declarations that place them.

6. Flow declarations — the declaration of every flow in the customer's workspace, including its triggers, steps, parameters and their configuration. The values of secrets referenced by a flow are not included; see Section 2.

2. Categories of data excluded from the exportable data

The following categories are specific to the internal functioning of Turbofy® and are excluded from the exportable data because their disclosure would risk a breach of our trade secrets, or because they cannot be disclosed for security reasons. None of them is required in order to run the customer's data, applications or digital assets on another provider's service, and these exclusions therefore neither impede nor delay the switching process within the meaning of Article 23 of the Data Act.

1. the source code of the Turbofy® platform itself and of the runtime that executes customer apps, other than the customer's own block code under Section 1;

2. internal infrastructure and operational metadata, such as internal service identifiers, deployment, caching and indexing structures and derived search indexes;

3. operational, security and audit telemetry that we keep in order to operate and secure the platform;

4. internal usage-metering and billing records, beyond the usage figures and invoices made available to the customer;

5. authentication credentials and secret values, namely password hashes, API keys, tokens and the values of stored secrets. Password hashes are irreversible by design and cannot be exported; the values of secrets are set by the customer and can be re-created at the receiving provider.

3. Register of data structures, data formats and interoperability specifications

The exportable data are made available in the structures and formats set out below. The authoritative and always current register of the data structures themselves is the schema of the customer's own workspace API: it is generated from the customer's tables, functions and flows, and it can be retrieved through that API at any time. The API documentation is provided free of charge.

1. Structured data — records, table definitions, functions, app users, flow declarations and app, page and block declarations are made available as JSON over the API, via HTTPS.

2. Files — assets are made available for download byte-for-byte in the file format in which they were uploaded; their metadata is made available as JSON.

3. Block code — source files are made available as plain text in their original file format, namely .tsx, .ts, .jsx, .js, .css and .json.

4. Standards and open interoperability specifications — JSON (RFC 8259 / ECMA-404), UTF-8 character encoding (RFC 3629), HTTP over TLS (RFC 9110, RFC 8446) and ISO 8601 for dates and times.

We keep this page up to date. Where a change to Turbofy® adds or removes a category of exportable data, or changes a data format in which it is made available, we update this page accordingly.

4. Exercising the right to export or to switch

1. The customer may export the data and digital assets listed in Section 1 at any time through the API, without a switching process and without assistance from us.

2. A switching request under Article 25 of the Data Act is made by e-mail to support@turbofy.com, subject to the notice period set out in Section 11 of our Terms & Conditions.

3. During the transitional period and the subsequent retrieval period described in Section 11 of our Terms & Conditions, the customer retains access in order to retrieve the data and digital assets listed in Section 1. No separate switching charge is imposed for the switching process.