Data export and switching providers
Status: 12 October 2026. The German version is authoritative.
This page describes how users take their data out of Meteor-AI, the format in which it is delivered and how switching to another provider works (Art. 23 to 31 of the Data Act, Art. 20 GDPR). The contractual rules are in clause 7 of the terms; this page supplements them.
1. Starting an export
Under Einstellungen → Daten & Konto → Daten exportieren (settings → data & account → export data), Meteor-AI downloads all data of the account as one ZIP file. The export is available at any time, as often as wanted and free of charge. It runs in the browser; depending on the number of images and documents it takes seconds to a few minutes.
2. Structure of the archive
| Path | Content |
|---|---|
LIESMICH.txt | description of the archive (German), rows per table, files that could not be retrieved |
manifest.json | format identifier meteor-ai-export, format version, time, account ID and email address, rows per table, missing files |
daten/<table>.json | one JSON array per table with all rows of the account, columns and values as in the database |
dateien/<bucket>/<path> | the account's files, stored under exactly the path given in the corresponding row |
lesbar/ | the same content for reading: chats and image conversations, skills, system prompts, user prompts and knowledge as Markdown, HTML apps as HTML files |
The JSON files are authoritative. The readable version leaves out settings such as model, temperature and links.
3. Tables
File in daten/ | Content |
|---|---|
profiles | display name of the account |
user_settings | settings: theme, language, defaults for model, answer length, images |
chat_folders | folders for saved conversations |
chats | chats with title, model, times, assignment to assistant, flow and folder |
messages | messages of the chats (chat_id), order in seq, role, text, reasoning, web search sources, usage |
attachments | attachments of messages (message_id): text attachments with content, image attachments with storage_path |
image_chats | image conversations |
image_messages | requests and generated images (chat_id), with prompt, model, size, storage_path and reference images in ref_paths |
assistants | assistants: name, description, model, system prompt, temperature, tools, conversation starters, tags |
assistant_skills, assistant_knowledge | which skills and which knowledge an assistant uses, in which order |
flows, flow_steps | flows and their steps with model, system prompt, input and output target |
flow_step_skills, flow_step_knowledge | which skills and which knowledge a step uses |
skills | skills with instructions |
knowledge_items, knowledge_files | knowledge items with text and their documents with extracted text and storage_path |
user_prompts, system_prompts | saved prompts |
html_apps | HTML apps with their complete HTML |
support_requests | support requests with reply |
usage_events | usage per request: time, model, tokens, cost — without content |
credit_ledger | credit bookings: starter credit, monthly allowance, top-ups, usage, refunds |
4. Formats
- Archive: ZIP without compression, file names in UTF-8. Any common program can extract it.
- Data: JSON (RFC 8259) in UTF-8. IDs are UUIDs, times ISO 8601 in UTC, amounts decimal numbers in euros (
…_eur) or US dollars (…_usd). References between tables use the IDs, e.g.messages.chat_id→chats.id. - Files: in the format in which they were uploaded or generated (e.g. PNG or PDF). Bucket
attachments: image attachments of chats;images: generated images and reference images;knowledge: documents in knowledge. - Readable version: Markdown (CommonMark) and HTML.
- Format version: 1. If the structure changes, the version in
manifest.jsonincreases and this page describes the change.
5. Not included in the export
- the password; Meteor-AI does not store it in plain text,
- payment methods and invoices; they are held by Stripe and available in the customer portal under Abo & Zahlung,
- data that serves operations only: subscription status at the payment provider, reports to billing, error logs and declarations of cancellation or withdrawal. The provider gives information about them on request under Art. 15 GDPR.
Requests and answers on their way to the model are not stored (zero data retention); the export contains what is stored in the chats.
6. Switching to another provider
- Notice: Anyone who wants to switch says so by email to info@meteor-ai.com. No notice period applies; the export is available immediately.
- Transition: For up to 30 days after the notice, the service continues unchanged. The provider answers questions about the format and supports the transfer. Users may extend the transition once.
- Retrieval period: After the transition, the data remains retrievable for at least 30 further days. A cancelled subscription ends at the end of the billing period; the account then continues on the Free plan, with all data.
- Erasure: After that, the provider deletes the account with all exportable data and confirms this by email; excepted is what it must retain for legal reasons. The contract ends with the deletion. Anyone who deletes the account themselves before then thereby requests immediate erasure.
- Charges: Export and switching are free of charge.
7. Location of the infrastructure and access by public authorities
Information under Art. 28 of the Data Act. Details on the service providers are in the privacy policy and the DPA.
| Part | Location | Jurisdiction of the service provider |
|---|---|---|
| Database, files, sign-in, server functions | Frankfurt am Main | Supabase Pte. Ltd., Singapore |
| Intermediary to the models | EU | Eden AI SAS, France |
| Processing in the model | EU infrastructure of the model provider | depends on the model provider |
| Emails | Germany, sent from Stockholm | Plunk, Belgium |
| Delivery of the app files (no accounts or content) | Frankfurt am Main and nearest location | Vercel Inc., USA |
| Payments | EU | Stripe Payments Europe, Ireland; group in the USA |
| Provider | Germany | zuber-management, Germany |
Protection against unlawful access. Accounts, content and files are stored exclusively in the EU, encrypted in transit and at rest; each account reaches only its own data. Data processing agreements are in place with the service providers, and with Supabase, Vercel and Stripe additionally the European Commission's standard contractual clauses. The provider discloses data to authorities or courts outside the EU only where an international agreement or Union law permits it (Art. 32 of the Data Act), discloses only as much as the request strictly requires, and informs those concerned beforehand unless this is prohibited.