The platform provides a highly configurable and flexible message meta-data and payload retention policy.
Device Message Meta Data
This is the informaton related to the message transfer such as device IP address, device port, device id, etc.
The message meta data can be configured to be retained for example for device dashboard analytics and historical information access/queries.
The message meta retention policy can be configured in the device service profile to specify if device message meta-data should be stored permanently, destroyed immediately or stored temporarily for a configurable period before it is destroyed
Device Message Payload
By default Message Content Data (payload) is destroyed after message delivery regardless whether the message meta data is configured to be retained for the device /service profile.
The payload storage service provides the capability to define the payload storage policies to specify whether the device payload should be stored permanently or stored temporarily for a specified period after which it be automatically destroyed.
Regional Data Storage (Data Residency Policies)
When message payload is configured to be retained permenently or temporarily, the customer can specifiy the country/region where the message payload is to be stored/retained. This enables the customer to control in which jurisdiction their message content data should be held in and or whether the messages may be stored accross multiple regions.
Each regional storage service provides mulitple levels of data replication and high resilience storage services within the region. Customer may choose additinoal storage regions if desired or applicable.
Non Regional (Globally distributed) Data Storage
This service enables the IoT messages to be stored directly in high performant in-memory Data bases. Where the message meta-data are retained. When payload storage is enabled, the customer has the option to use Regional data store as described above for payload storage or the customer can opt to use Non region specific storage which will store the payload in an in-memory DB dispersed accross multiple regions.
This service can also be used concurrently with the regional storage option and should only be used if you have no legal obligation to store your data in a specificly named region/country.
Each device service profile can be configured independently with any combination of the above described storage options.
Message Queueing Services
The platform provides Message Queueing for devices in Deep Sleep / Offline mode or devices that are unreachable at the time of message delivery attempt.
This service can be enabled in the device Service Profile. If enabled a queued message is auto delivered to the device when the platform detects the device is awake and or when the device performs an event. When enabling this service the duration of time to queue a message is specified. During the submission of message, a specific queue duration time can also be specified for each message otherwise the service profile specified queue duration is used. The time specified for each message must be within the queue duration time specified in the service profile.
The Storage service type configured in the service profile (regional and or Non regional) is automatically applied to where messages are queued to ensure customer data is retained within the desired region/country only.
Multiple Level of Data Encryption
The messages are encrypted before being stored. The encrypted messages are stored on encrypted data volumes/drives. When in-transit the messages are transfered over encrypted secure links (encrypted in transit and at rest).
Data Ownership
In the period of time the payload is retained (queued or stored as per payload storage policy) you retain ownership of the payload received from your IoT devices and upstream applications. We do not share it with any third parties.