One reason is our [Double-Hashing anonymization method](https://telemetrydeck.com/docs/articles/anonymization-how-it-works/). It requires two distinct parties to use their own private keys to make sure neither can retrieve any personally identifiable information. When an event arrives on the server, we add our own salt to the user identifier and hash it again. This ensures that neither TelemetryDeck nor you can reconstruct the original identifier, protecting the user’s privacy.
0 commit comments