This page explains your rights and BRYTER’s processes for data switching (migration or deletion) under the EU Data Act (Regulation 2023/2854).
These rights apply to customers of BRYTER’s cloud services seeking to migrate their data to another data processing service provider or to on-premises ICT infrastructure, or to delete such data after service termination. It explains how to initiate switching, how BRYTER technically enable migration and deletion via APIs, applicable limitations, and who is involved in these processes.
This page complements the contractual provisions in BRYTER’s Master Service Agreement (MSA) and the applicable Documentation.
1. Customer’s rights to request migration or deletion
1.1 Right to migrate
You may request automated migration of your data to another provider or to your own on-premises ICT infrastructure. Data is made available in commonly used, structured, and machine‑readable formats (such as JSON, XML, or CSV) to support interoperability and functional equivalence.
1.2 Right to deletion
You may request complete and irreversible deletion of your data from BRYTER systems after service termination, subject to legal retention obligations.
1.3 Contractual Consequences
Migration or deletion of your data typically results in termination of the applicable order. BRYTER will notify you once migration or deletion has been successfully completed and the corresponding termination has taken effect. Commercial consequences (including fees) are governed by your MSA and applicable Order.
2. Switching Process Overview
2.1 Notice and timing
You must provide two (2) months’ prior written notice of your intention to initiate migration or deletion. Following expiry of this notice period, BRYTER will complete the requested migration or deletion without undue delay and in accordance with applicable law.
2.2 How to Initiate a Switching Request
Authorized users may open a switching request via BRYTER Support at support@bryter.io, referencing “EU Data Act Migration/Deletion”. BRYTER will confirm receipt and provide next‑step instructions, including links to the relevant API documentation.
2.3 Prerequisites
Before initiating switching, please ensure that:
- your receiving environment is capable of processing the supported export formats and data volumes;
- authorized personnel and scope of data are clearly defined; and
- any required internal approvals are in place.
3. Process Steps
3.1 Migration Process
- Submit a switching request via Support at support@bryter.io and confirm scope and target environment.
- Receive API credentials and endpoint documentation.
- Execute data export using the documented APIs and supported formats.
- Validate data integrity and completeness in the target environment.
Confirm completion. BRYTER will notify you that migration is complete and that termination has taken effect.
3.2 Deletion Process
- Submit a deletion request via Support at support@bryter.io, specifying datasets and scope.
- Optionally perform a final export prior to deletion.
- BRYTER performs complete and irreversible deletion of Exportable Customer Data, including backups, subject to legal retention requirements.
- BRYTER confirms completion and notifies you that termination has taken effect.
4. Technical Enablement
4.1 APIs and Automation
BRYTER enables automated migration and deletion of Exportable Customer Data via documented APIs. Relevant technical documentation is provided in a timely manner.
4.2 Data Formats
Exports are provided in commonly used, structured, machine‑readable formats (including JSON, XML, and CSV), depending on data type and endpoint.
4.3 Authentication and Security
API access is authenticated and logged. Secure credentials must be used in accordance with the API documentation and BRYTER’s security guidance.
4.4 Performance and Scheduling
Large‑volume exports may be batched or scheduled to ensure platform stability. Any material scheduling constraints will be communicated in advance.
5. Statutory and Technical Limitations
5.1 Legal Retention Obligations
Applicable laws may require retention of specific data for defined periods. Such obligations override deletion requests to the extent strictly necessary.
5.2 Technical Limitations
The scope of Exportable Customer Data and functional equivalence at the receiving environment may be limited due to:
- third‑party system constraints or proprietary formats;
- historical backups or immutable storage policies; and
- volume, rate limits, or performance safeguards.
Material limitations are described in the applicable API documentation and communicated in advance where relevant.
6. Third Parties Involved
6.1 Sub‑processors and Other Providers
BRYTER identifies sub‑processors and other third parties involved in migration or deletion activities, such as infrastructure providers or support partners, and provides advance notice of material changes.
6.2 Roles and Responsibilities
BRYTER remains responsible for providing APIs, documentation, and coordination of the switching process within the scope of its statutory obligations. Third parties may provide infrastructure or tooling as disclosed.
7. Commercial Information and Charges
7.1 Standard Fees
Standard subscription or service fees continue to apply until the effective termination date. These fees are not switching charges.
7.2 Switching‑Specific Charges
Switching‑specific charges (for example, data egress fees or additional support services) may apply where permitted by law and agreed in advance. Any such charges will be disclosed transparently before you commit to them.
Refunds, early termination consequences, and prepaid fees are governed by your MSA and applicable Order.
8. Notifications and Updates
BRYTER will notify you upon completion of migration or deletion. This page and linked documentation are kept accessible and up to date, and material changes affecting switching rights or processes will be communicated to your designated contact.
9. Support and Escalation
For questions regarding migration or deletion, please open a support ticket with support@bryter.io and reference “EU Data Act Switching”. Include your desired timeline, data scope, and receiving environment details. For urgent or large‑scale requests, escalation may be requested via Support.