Carillon docsData residency
Where Carillon stores data and what is sent to APNs and FCM.
Carillon is operated by Exostack SARL and hosted on Scaleway in Europe.
Data flow
| Data | Where it goes |
|---|---|
| Device registrations, attributes, and delivery records | Carillon infrastructure in France |
| Provider credentials | Encrypted storage using Scaleway Key Manager |
| Device token and notification payload | APNs for iOS or FCM for Android |
APNs and FCM are external delivery providers operated by Apple and Google. Carillon hosting in France does not guarantee that these providers process the token or payload only in the EU.
To minimize payload data, send an identifier and let your app fetch the content after opening. The token is still sent to the delivery provider.
Device data
Carillon treats push tokens as personal data. Tokens are truncated in list views and available in
the device detail view. external_id and tags are stored as provided by your application.
See registration fields for the SDK's collected data.
Provider credentials
Credentials are encrypted before storage and are not returned after upload. Credential endpoints return metadata such as the Key ID, fingerprint, and validation status. Credential values are redacted in application logs.
Legal documents
The Data Processing Agreement sets out how Exostack processes device data on your behalf. The sub-processor list names the services that process it and explains the role of APNs and FCM. The Privacy Policy covers dashboard accounts.