Analytics Data Privacy

Answers about how TelemetryDeck ensures the privacy of the end-users that generate analytics data by using our customers' apps

Can’t find the answer you’re looking for? Ask a question on Github issues or write an email to info@ this domain!

Questions about Analytics Data Privacy

How can I delete my analytics data?

You can delete your analytics data at any time. For this, you delete your organization in TelemetryDeck. This deletes the namespace of your organization and stops all ingestion into it.

You can also delete single months of your data in Organization Settings. We cannot delete the data of one app, one user or one installation.

Please keep two things in mind:

  • Parts of your analytics data can remain in low-level backups for up to 3 months.
  • Aggregated numbers that went into our public survey currently cannot be separated from that data set.

Does TelemetryDeck use my analytics data for advertising, profiling or other purposes?

We do not use your data for advertising, tracking, cross-app or cross-customer matching, or profiling. We also can not do this: The data is anonymized, so it is simply not suitable for these purposes.

We also do not sell personal data. We have no personally identifiable information of any kind about the users of your apps.

We do use aggregated data for our own analyses. You can see the results in our survey. We reserve the right to do more analyses of aggregated customer data in the future, and to make them available to selected partners. These analyses focus on device information, operating system versions and how common they are. You cannot opt out of this aggregated data set.

What data does TelemetryDeck collect in apps?

When you use one of our SDKs in your app, our servers store this data:

  • An anonymized user ID. It stays the same for one app installation, but nobody can trace it back to a person.
  • The action, for example "App launched" or "Settings opened". You as the app publisher define these actions.
  • A timestamp of the action, rounded to the hour. The server keeps your event time if the event arrives within 24 hours. Older events get the time of arrival minus 24 hours.
  • Device metadata, for example system version, app version, build number, App Store or TestFlight, and device type. You find the full list of default parameters in our docs.
  • Additional metadata that you define, for example "Number of items in the database".

Our servers never store IP addresses. Not in the database, not in log files, and also not anywhere else.

Can I set my own retention period?

Not yet, but you can delete data by month. Since October 27, 2026, you find a screen in Organization Settings for this. It deletes single months of your analytics data. By the end of 2026, we want to allow our customers to set the value for Cold Storage Retention by themselves. This will be a new organization-wide setting that says something along the lines of "delete all analytics data as soon as it is older than x months".

Additionally, we will refine our backup strategy, so that we no longer store raw ingested data forever. Raw ingested data is fantastic for recovery, but it is impossible to remove individual customers from that data set. So we will find a better way to back up our analytics data, namespace by namespace. Then we can also delete data from backups.

Can I delete the data of one app, one user or one installation?

No. Our storage works per month, not per app or per user. You can delete single months of your analytics data in Organization Settings. You can also delete your whole organization, which will delete all its analytics data.

If you need a clean start for one app, create a new app with a new app ID.

The stored events contain no value that links back to a device or an installation. So an end-user cannot ask us to delete their events.

Can I match my own user IDs to TelemetryDeck users?

No. Our server salts your clientUser value with a secret and hashes it, and we expect senders to salt and has the clientUser on their side as well, making sure neither party can restore the original user identifier. Only TelemetryDeck knows the secret. So you cannot compute the stored value, and we do not offer a lookup.

This is the core privacy principle of TelemetryDeck: nobody can match a stored event to a person. If you add identifying information to your events, for example in a parameter, you undermine this principle. In that case, our data privacy guarantees are void.

If you need a property like a license status in your insights, send it as a parameter with your events. Make sure that the value identifies no person.

Does TelemetryDeck look at the IP address for app events?

No. For events from our app SDKs and from the Ingest API, the server does not read the IP address. No country or location value is added.

Only Website Analytics uses the IP address for a moment. It sends its events to the /v2/w/ endpoint. There, the server derives a country and a daily changing hashed identifier. The IP address is then discarded. You cannot turn off the country lookup for Website Analytics.

We don’t store IP addresses in logs or elsewhere of course.

Does TelemetryDeck store IP addresses?

No, TelemetryDeck does not store IP addresses. Not in our database, not in log files, not in backups, and also not at our infrastructure providers.

For apps that use our SDKs or send data directly to the Ingest API, our servers do not look at the IP address at all.

Only for Website Analytics (the Web SDK) is the IP address used for a short moment, and for two things:

  • A hashed user identifier. The IP address, the app ID, the user agent and a salt that changes daily are combined and hashed with SHA-256. The same visitor is recognized within one day on one website, but not across days or across websites.
  • A rough country and continent. The country code, continent and EU membership are derived from the IP address.

After this, the IP address is discarded. It is never written anywhere.

More details you find in our Privacy FAQ and our Privacy Policy.