Switching and data export

1. Request. Close your organisation in the dashboard, or email [PLACEHOLDER: support email — DSA Art. 12 point of contact]. Say whether you switch to another provider, move to your own infrastructure, or want your data erased — and whether you need a transitional period.
2. Notice period. Your plan keeps running until the end of the billing period you have paid for — at most a month, never more than the two months the Data Act allows. Renewal stops with the request.
3. Transitional period (optional). On request we keep the service running unchanged for up to 30 more days at the standard monthly fee, pro rata, and help you and anyone you authorise. If that is technically unfeasible we tell you within 14 working days, with reasons and an alternative of at most 7 months. You may extend the transitional period once.
4. Service end. Your workers are destroyed, and we confirm the end of the contract by email.
5. Retrieval period. For at least 30 days you can still sign in and download the export.
6. Erasure. Then we erase your exportable data. Kept only because the law requires or allows it: invoice and booking records (statutory retention), DSA decision records, and the connection log until its own retention ends (see the privacy policy). An open abuse case or an AUP / sanctions suspension postpones the erasure until it is decided. Backups expire within 15 days. On request we confirm the erasure in writing.

You can withdraw a close request until the service ends; the renewal then stays off until you turn it back on in the billing portal.

In the dashboard, as an owner or admin, download the export; or, while signed in, call GET /api/dashboard/export. You get one JSON document (flatbrowser.export, format version 1) containing every category listed in the register below. Large histories are streamed in full, not truncated.

Known restrictions and technical limitations

• Browser state does not persist: cookies, local storage, cache and downloads live in a temporary profile that is deleted when each session ends. There is nothing browser-side to port — keep login state on your side (for example Playwright storageState).
• Screenshots, PDFs and HTML from the REST API are returned in the response and never stored, so they are not in the export.
• API-key secrets are never stored, so they cannot be exported. Create new keys at your new provider.
• Invoices are read from Stripe when you export (up to 1,000); they are also available in the billing portal.
• Exempt for security and trade-secret reasons (Terms §12a): key hashes, worker access tokens, host and network configuration, our hostname blocklist, capacity data, our internal audit log, and the identity of people who sent notices about you.

The export is UTF-8 JSON (RFC 8259); timestamps are ISO 8601 in UTC; amounts are integers in the smallest currency unit. A JSON Schema (draft 2020-12) of the current version is published at /switching/export-schema.json. The browser interfaces themselves follow open specifications: the Chrome DevTools Protocol, WebSocket (RFC 6455) and JSON over HTTPS.

Changelog

• Version 1 (2026-10-04): First published version.

• Puppeteer, Playwright and any other CDP client: replace our WebSocket URL with your new provider’s, or go back to launching Chromium locally. No library of ours is involved.
• REST calls: our /v1 endpoints are documented in the REST reference, and the Browserless-style aliases accept Browserless request bodies, so moving between compatible providers is a base-URL change.
• Proxies you configured are yours; take them with you.
• Nothing runs on your infrastructure, so there is nothing to uninstall.

Who and where

• The provider of the service is [PLACEHOLDER: registered legal name incl. legal form (GmbH / UG (haftungsbeschränkt))], established in Germany and subject to German and EU law.
• The ICT infrastructure — every server that runs the service and stores your data — is operated by Hetzner Online GmbH, a German company, in its data centres in Falkenstein and Nuremberg (Germany), Helsinki (Finland). It is subject to German and EU law (Finnish law as well for the Helsinki site).
• Encrypted database backups are stored with [PLACEHOLDER: offsite backup storage provider — name, seat and location (a separate account from Hetzner)] in the EU.
• Billing data is held by Stripe Payments Europe Ltd. (Ireland), part of a US group, under our controllership — it is not part of the service data described here.

Measures against unlawful third-country government access to non-personal data (Arts. 28(1)(b) and 32)

• EU-only infrastructure, enforced in software: the provisioning system refuses to order servers outside the EU locations above.
• No subprocessor established or controlled outside the EU holds service data.
• Encryption in transit for all external traffic; backups are encrypted before they leave the server, with a key the storage provider does not hold.
• Every request from a third-country authority is reviewed for legality: we comply only where an international agreement such as a mutual legal assistance treaty, or the conditions of Art. 32(2) and (3), allow it, and we disclose only the minimum the request requires.
• Before complying we inform you of the request, unless it serves law enforcement and informing you would endanger that purpose, for as long as that is the case (Art. 32(5)).

The standard fees are the monthly plan prices published on the pricing section and in the billing terms. There are no switching charges, no data-export or egress charges and no early-termination penalties — not now, and not after 12 January 2027 when the Data Act forbids them. During an optional transitional period only the standard monthly fee applies, pro rata.