Table of contents
1. About this information
The Data Act (Regulation (EU) 2023/2854) requires that, before a purchase or contract, you know which data a connected product and a related service generate and what you can do with it. Here the connected product is the ModbusCloud Gateway (Article 3(2)) and the related service is the ModbusCloud portal (Article 3(3)). This page gives that information per topic.
This information belongs to the terms and conditions. If this page differs from the terms, the terms prevail. You can print this page or save it as a PDF with the button at the top.
2. Who holds the data
ModbusCloud is the data holder of the data of the gateway and the portal.
| Item | Details |
|---|---|
| Name | ModbusCloud |
| Legal form | Trade name of a Dutch sole proprietorship |
| Chamber of Commerce number | 97761362 |
| Address | Ceintuurbaan 15, 8022 AW Zwolle, the Netherlands |
| info@modbuscloud.com | |
| Phone | +31 85 333 4015 |
Parties that process data on behalf of ModbusCloud are on the list of sub-processors. Where they store the data is set out on Data location and government access.
3. Which data is generated
| Type | What it is | Format |
|---|---|---|
| Readings from the gateway | The values of the Modbus registers you set up in the portal, with the time, the raw value and the value after the scale factor | Numbers with a timestamp, with the name and unit of the register |
| Status data of the gateway | Online or offline, 4G signal strength, uptime, firmware version, IP address, the daily data usage of the SIM card and the confirmation that the gateway has applied a new configuration | Numbers and text with a timestamp |
| Data of the portal | Settings of gateways, Modbus devices and registers, alert rules and alerts with acknowledgements and notes, automations and their executions, write commands to registers, dashboards, reports and the activity log | Structured data in the database |
4. How often and how much
The gateway reads the registers continuously, at the polling interval you set per Modbus device. The default is every 5 minutes. Live values appear in the portal as soon as the gateway sends them.
| Gateway connection | Shortest polling interval | Live in the portal | Stored in the history |
|---|---|---|---|
| Cable, through ethernet or the local network | 1 second | Every reading | At most 1 value per register per minute |
| 4G, through the SIM card | 60 seconds, default 300 seconds (the SIM interval) | Every reading | At most 1 value per register per minute |
The volume depends on the number of registers and the polling interval. The table gives the volume per register. The size is that of a CSV export of one register with timestamp.
| Polling interval | Stored values per register per year | Size, approximately |
|---|---|---|
| Every 5 minutes (default) | 105,120 | 3 MB |
| Every minute or faster | 525,600 | 15 MB |
Status data arrives with every heartbeat of the gateway and with every change. Data of the portal arises with every action, such as a changed setting, an acknowledged alert or a write command.
5. Where the data is stored and for how long
The gateway does not keep a history. Readings are held only briefly in the working memory of the gateway, until they have been sent. If the connection is down, the gateway holds up to 20,000 readings. After a power interruption they are gone. The gateway does keep the settings the portal sends to it.
All other data is stored with the providers of ModbusCloud, in data centres in the EU. Which provider is located where is set out on Data location and government access.
| Data | Retention period |
|---|---|
| Readings (raw) | 12 months |
| Summaries per 15 minutes, per hour and per day | May be kept longer, but without guarantee |
| Status history of the gateway | 90 days |
| Resolved alerts with their notes | 365 days after resolution |
| Settings, such as gateways, Modbus devices, registers, alert rules, dashboards and reports | Until you delete them |
| All data after the end of the agreement | 90 days to export, then deletion within 30 days and from the backups within 35 days after that (clause 9.2 of the terms) |
The periods for the other data, such as logs and notifications, are listed in Retention periods and exporting your data.
6. Accessing, retrieving and erasing data
You retrieve the data yourself, without charges per request or per export. All routes are included in the licence.
| Route | What you get | Format | Conditions |
|---|---|---|---|
| Portal | Live values, history per register, alerts and all settings | In the browser | With an account in your organisation, every role can view |
| Download readings, per gateway | All registers of one gateway, over 7 days, 30 days, 12 months or everything | CSV or JSON | Up to 500,000 readings per file, every role can download |
| Export of the whole account | All exportable data of your organisation, as in Annex A of the terms | CSV and JSON | Under Settings in the portal |
| REST API | Gateways, Modbus devices, registers with their latest value, history and alerts, with the raw and the converted value | JSON, described in OpenAPI 3.1 | With an API key created by an owner or administrator, 100 requests per minute per key, up to 1,000 readings per request |
| Webhooks | A message on an event, such as an alert going off or a gateway going offline | JSON over HTTP POST, signed according to Standard Webhooks | An owner or administrator sets the address |
The API documentation is at docs.modbuscloud.com. How to download readings per gateway is described in Download readings.
You delete settings, dashboards and alert rules yourself in the portal. When you disconnect a gateway, you choose whether its readings, Modbus devices, registers and variables are deleted as well. To have other data erased, or your whole organisation, email privacy@modbuscloud.com. After the end of the agreement, ModbusCloud erases all data in accordance with clause 9.2 of the terms, except invoice data, which is kept for 7 years (clause 9.3).
7. What ModbusCloud itself does with the data
The customer remains the rights holder of the data (clause 8.1 of the terms). The use by ModbusCloud is set out in clauses 8.2 and 8.3. They read as follows.
8.2 The Customer grants ModbusCloud a limited, worldwide, royalty-free right of use over this data insofar as necessary for providing, securing and improving the Service, as well as for performing legal obligations.
8.3 ModbusCloud may use anonymised, aggregated statistics for product improvement, benchmarking and reporting. Such statistics do not contain data traceable to natural persons or individual Customers.
Sub-processors process the data only on behalf of ModbusCloud, to provide the service. Beyond that, a third party only receives your data through a route you set up yourself, as in section 8, or if the law requires ModbusCloud to provide it. How ModbusCloud handles a request from a government is set out on Data location and government access.
8. Sharing data with a third party, and stopping it
| Route | How you share | How you stop |
|---|---|---|
| API key | Create a key under Settings > API keys with only the permissions the third party needs, and give it to the third party | Revoke the key. It stops working immediately |
| Webhook | Enter the address of the third party in the webhook | Switch the webhook off or delete it |
| Export | Download the readings per gateway or the export of the whole account, and pass on the files | You cannot recall a file you passed on. Make arrangements about it with the third party |
You can also ask ModbusCloud to deliver the data directly to a third party. Email info@modbuscloud.com with the name of the third party and the data concerned. You stop the sharing the same way.
9. Trade secrets
ModbusCloud does not hold trade secrets in the data that your gateway and the portal generate.
10. Lodging a complaint
If you believe ModbusCloud does not comply with the Data Act, you can lodge a complaint with the Netherlands Authority for Consumers and Markets (ACM). The ACM supervises the Data Act in the Netherlands. Where personal data is concerned, the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) is competent. You can also lodge a complaint with the competent authority in the EU country where you are established. You can always contact ModbusCloud first at info@modbuscloud.com.
11. Duration and termination
| Licence | Duration | Termination |
|---|---|---|
| Annual licence | One year, after which the licence renews automatically for one year (clause 11.3) | As of the end of the current year, in writing, for example by email to info@modbuscloud.com (clause 11.4) |
| Lifetime licence | For as long as ModbusCloud offers the service (clause 11.3) | Not needed, because the licence does not renew |
Switching to another provider, or stopping with export and erasure, is governed by clause 25 of the terms. That applies to both licences, free of charge.
12. Changes
| Date | Change |
|---|---|
| 15 October 2026 | Page published |