Data Processing Summary

This page contains details on the underlying ClearBlade IoT Core’s data storage processing configuration:

1. Device state and configuration data:

   1. For each device in a given registry, up to ten of the most recent states are stored. State messages are those received FROM the device.

   2. For each device in a given registry, up to ten of the most recent configuration changes made are stored. Configuration changes are made in the registry (i.e. cloud-side) and may or may not have been sent TO the device.

   3. For a given registry, state and configuration data will be stored for the life of the registry. The data is immediately deleted when the registry is deleted.

2. Backups and Logs:

   1. ClearBlade does perform regular backups on application data. Backups are retained 14 days in storage before being deleted permanently.

   2. Logs are stored for 30 days.

3. Mitigation for Google PubSub outages:

   1. In the event of a PubSub outage the ClearBlade MQTT brokers contained within IoT Core will queue up up to 10,000 messages per registry for delivery upon the recovery of PubSub.

   2. ClearBlade uses Google’s Golang PubSub library. That library retries delivery to PubSub until PubSub recovers.