Understanding Data Privacy and Validity of a Sensor in Cumulocity IoT


Data privacy and the validity of a sensor in Cumulocity IoT are important concerns for businesses that use the platform. Here, we answer some of the most common questions regarding this topic.

Is there an upper limit on the storage of historical sensor data on the Cumulocity IoT platform?

The answer to this question is that it depends on the retention rules defined for the tenant. For more details on retention rules, you can refer to the relevant documentation:


What happens to sensor data when a sensor device is removed from the Cumulocity IoT platform?

If a device is deleted, corresponding data will immediately be deleted, and any unlinked data will be removed by cleanup activity, which is an internal activity triggered by the device delete action. To prevent the loss of data, an alternative to deleting a device is to arrange all retired devices in one group, which ensures that all reports remain correct. For more information on grouping devices, you can refer to Assign inventory roles to device groups using the API) . To prevent alarms from being raised for retired devices, disable connection monitoring.

Note: Deleting a device does not delete the data of its child devices.

Will unregistering a smartphone from the Cumulocity IoT tenant or logging out of the platform affect the device registration status?

Unregistering a smartphone from the Cumulocity IoT tenant will stop it from sending sensor values, but historical values will still be stored. User logout will not have any effect on device registration status.

Relevant articles:

1 Like

This addresses the device life-cylce from provisioning (onboarding), installation on site, production, maintenance and offboarding. There are of course different states from customer to customer. However, I which the Cumulocity IoT would provide such a device life-cycle state machine which is configurable, instead of addressing this in a such very technical way.

1 Like