Data Act
The “ Data Act ” (Regulation (EU) 2023/2854) has been in effect since September 12, 2025. You can export your data at any time and switch providers. Here you’ll find the process, a list of all exportable data—including formats and interfaces—and the location of the infrastructure.
As of October 28, 2026 · EULA V2.5 · Platform Cumulocity, Release 2026
Applies to switching to another provider, migrating to your own infrastructure, or deleting your data. Governed by Section 17 and Appendix 4 of the EULA V2.5.
You let us know where the data is going or whether we should delete it.
We will support you and your new provider, make the data available, and continue to operate MACHINES.cloud .
Exports and interfaces will remain available. After that, we will delete your data and confirm this with you.
Switching fees: Until January 11, 2027, no more than our direct costs; as of January 12, 2027, none (Section 17.2). If you switch before the end of the minimum term, a limited compensation fee will apply (Section 17.3). If the switch cannot be completed technically within 30 days, we will notify you within 14 business days and specify a timeframe of no more than seven months.
Pursuant to Article 26 of Data Act. Annex 4 of the EULA V2.5 specifies which data can be exported. For information about the platform, please refer to the public documentation at Cumulocity; our additional notes are provided at the end.
| Data | Structure | Format | Interface | Description |
|---|---|---|---|---|
| Measurement Values: Numerical values from gateways and sensors, including timestamps, units, and sources | Measurement using fragments and series (value, unit) | JSON · CSV · XLSX | /measurement/measurements | Domain Model ↗OpenAPI: Measurements ↗Export Function ↗ |
| Location Data: Timestamped locations derived from the tracking of vehicles and machinery | Event with fragment c8y_Position (lat, lng, alt); last position on the device | JSON · CSV · XLSX | /event/events | Fragment Library ↗OpenAPI: Events ↗ |
| Events: Events such as power-on, status changes, or BLE beacons | Event with type, time, text, and fragments | JSON · CSV · XLSX | /event/events | Domain Model ↗OpenAPI: Events ↗ |
| Alerts: Alerts with Severity, Status, and Frequency | Alarm (severity, status, count) | JSON · CSV · XLSX | /alarm/alarms | Domain Model ↗OpenAPI: Alarms ↗ |
| CalculatedValues: Values calculated and stored in the tenant based on this data | Measurement, Event, or Managed Object, such as the source data | JSON · CSV | wie die Ausgangsdaten | Domain Model ↗ |
| Devices andGroups: Master Data for Devices, Groups, and Assets, Including Their Structure | Managed object with fragments such as c8y_Hardware, c8y_Firmware | JSON · CSV · XLSX | /inventory/managedObjects | OpenAPI: Inventory ↗Fragment Library ↗ |
| Users, roles, and groups in the tenant, without passwords or other access credentials | User, Group, Role | JSON | /user/{tenant}/users | OpenAPI ↗ |
| Dashboards: Dashboards and views created by the customer | Managed Object with fragment c8y_Dashboard | JSON | /inventory/managedObjects | OpenAPI: Inventory ↗ |
| Rules: Rules and reports created by the customer | Analytics Rules and EPL Apps | JSON · Source Code | Streaming Analytics | EPL Apps ↗ |
| Retention Policies: Retention Periods by Data Type | Retention Rule | JSON | /retention/retentions | OpenAPI ↗ |
| AuditLog: Security-Related Events in the Tenant | Audit Record | JSON | /audit/auditRecords | OpenAPI: Audits ↗ |
| Operations: Commands, configurations, and OTA updates sent to devices, along with their status | Surgery Involving Fragments | JSON | /devicecontrol/operations | OpenAPI: Device Control ↗ |
| Files andFirmware: Files, binary data, and firmware uploaded by the customer | Binary with Managed Object | Original format | /inventory/binaries | OpenAPI ↗ |
| CustomApplications: Applications Provided by the Customer | Application with Archive | Original format (ZIP) | /application/applications | OpenAPI ↗ |
| Fieldsin Our Components: Additional fragments that our decoders and microservices create in your tenant | Fragments in Managed Objects, Events, and Measurements | JSON | wie oben | follows |
| Raw Data fromReception Services: Unprocessed data packets from the devices you purchase through us | by device type | [open] | [offen] | follows |
The web application's export function supports CSV or XLSX formats, with a maximum of one million records per export. Larger volumes and all other data are available via the REST interfaces in JSON format. Upon request, we can provide the data as a file during the transition.
Internal operational and monitoring data, internal security data such as keys and certificates, and internal billing and capacity data. These exceptions do not delay the transition.
Pursuant to Article 28 Data Act.
Storage
Your data is stored in Amazon Web Services data centers in Frankfurt am Main, Germany. The backups are stored in the same region. Our own services run in data centers in Germany, as do the reception services for devices you purchase through us.
Operations and Support
The platform's operations team also works from countries outside the EU. We grant access to your data for support purposes only on a case-by-case basis and for a limited time; such access is logged.
Protection Against Government Access
Encryption during transmission and storage, as well as standard contractual clauses or an adequacy decision for each transfer to a country outside the EU.
If we supply you with devices, you will receive a data sheet for each device type prior to the conclusion of the contract, in accordance with Article 3 of Data Act: what data the device generates, how you can access it, and who uses it.
The data sheets for Teltonika and Digital Matter devices will be provided with the quote.
