Security
How Chronicle handles and stores information.
How is my data used and stored?
To deliver alerts and management capabilities for admins and workspaces, Chronicle records a few things about each workspace:
- Events that have been triggered (these are the ones sent to #chronicles)
- Channel metadata (names, IDs, and whether it's been ignored)
- User metadata (guest status, username, user ID, etc.)
- File metadata (IDs, filename, public sharing metadata, etc.)
Note: The content of channels, files, or messages is never stored. Instead, the metadata listed above is saved to track changes to these resources. This allows Chronicle to send admins more detailed alerts when something happens — for example, telling you which file was deleted rather than just that a file with a specific ID was deleted. The same applies when a user changes their username or shares a private company file outside of Slack. No personally identifying information is stored, aside from a user's username, which is used to enable "username changed" events.
For connected admins, Chronicle stores some basic information to function:
- Email address
- Connected workspaces
- Billing information
Additionally, no billing information is stored aside from a Stripe billing token, meaning a user's credit card information never touches our servers.
Data sharing: Chronicle does not share any information with third parties, with one exception: if you reach out through the chat widget on our website and provide an email address, that email is used only to reach you if the conversation gets disconnected. The only way stored data can be accessed is through Chronicle's admin dashboard, by a connected administrator from your Slack workspace.
Data deletion: If you'd like all data related to your user or workspace deleted, please contact us — we can accommodate deletion requests. If you have any questions about how this data is stored or used, please contact us. We’d be happy to answer any questions you may have.