Vibee

Data Portability and Infrastructure

Last updated: 21 September 2026

This page supplements Section 10 of the Terms of Service and fulfils the information duties of Regulation (EU) 2023/2854 (the Data Act) regarding data export, formats, switching to another provider, and the location of the infrastructure. It is linked from the Terms of Service.

1. What can be exported

  • Database table definitions and schema (column names, types, relationships between tables).
  • All rows stored in the tables.
  • Uploaded files, in their original format.
  • App configuration – page, form, dashboard and chart definitions.
  • Definitions of custom endpoints/APIs created in the app.
  • The app's user list (e-mail addresses and assigned roles, without passwords).

2. What is not exported

  • Hashed passwords and security tokens – for security reasons these are never exported or shown in readable form; they must be re-created after switching instead.
  • Internal operational logs and infrastructure metadata (e.g. access IP addresses) that are not the Customer's content.

3. Formats and technical limits

Table data is exported as CSV (RFC 4180, UTF-8 encoding); app configuration and table schema as JSON (UTF-8). Uploaded files are downloaded individually or in bulk as a ZIP archive in their original format. There is no fixed upper size limit on an export; larger volumes of data (typically above 1 GB) may be split into several files for download. Every export includes a schema.json file describing the structure and types of the exported data (the Data Act's registry of data structures and formats).

4. How export and switching work

  1. The Customer requests an export via the dashboard, an MCP tool, or by e-mail to info@vibee.one.
  2. The Operator starts preparing the export no later than 5 business days after the request.
  3. From notice of intent to switch to another provider, a 30-day transition period runs during which the Service remains fully functional and data can be exported repeatedly.
  4. After the transition period ends, the Customer has a further 30 days to download the prepared export before it is removed.
  5. The transition period may be extended once, by a further 30 days, at the Customer's request.

The exported data and formats (CSV/JSON, described by schema.json) contain nothing proprietary; importing it into another provider is a matter for the Customer and that provider, and the Operator will explain the export's structure on request.

5. Location of the infrastructure

The database, file storage and running apps are operated exclusively on servers of Hetzner Online GmbH in Germany, within the European Union. The Operator does not move the Customer's content outside the EU/EEA.

6. Protection against third-country government access

Because the infrastructure is located in the EU, non-personal data stored in the Service is not subject to the jurisdiction of third-country public authorities. The Operator will not give a non-EU public authority access to the Customer's non-personal data unless required by an international agreement (e.g. on mutual legal assistance) recognised under EU or Member State law, and will inform the Customer of any such request unless expressly prohibited by law from doing so.