A TelemetryDeck alternative that stores no identifiers
The short answer
Both are privacy-focused analytics for iOS, macOS, Android, and web apps. Neither uses cookies or advertising identifiers, and neither asks for an App Tracking Transparency prompt. The difference is what gets stored.
TelemetryDeck stores every signal your app sends, each with a salted, double-hashed identifier that stays constant for an app installation. That identifier is what lets it count daily and monthly users, chart retention, and follow funnels install by install.
Trackless stores no identifier of any kind and no individual events, only aggregate counts per day. It cannot count people, so it offers no user counts and no retention curves. What you get instead is a store with nothing in it that could single out a person: nothing to declare as an identifier on your App Store label, and nothing personal in what you hand to your coding agent.
If you need to know how many people used your app this week, TelemetryDeck answers that and Trackless does not. If you need to know which features are used, what is failing, and how slow it is, without holding anything per install, Trackless is built for that.
At a glance
| Trackless | TelemetryDeck | |
|---|---|---|
| Identifier stored | None | A salted, double-hashed ID, constant per app installation |
| Individual events stored | No, only daily aggregate counts | Yes, each signal with a timestamp rounded to the hour |
| App Store privacy label | Product Interaction and diagnostics, no Identifiers | Device ID and Product Interaction (User ID instead, with a custom identifier) |
| Device model | Not collected; device class only (phone, tablet, desktop) | Collected by default (for example, iPhone 12) |
| User counts, DAU / MAU | No | Yes |
| Retention curves | No | Yes |
| Conversion funnels | Aggregate step counts | Yes, per installation |
| Errors | By name and code, with errors per session and spike alerts, plus an opt-in count of uncaught exceptions by class or name, with no stack traces | Yes, an Errors preset with categories |
| Timing | p50 / p90 / p99 and a duration histogram per measurement, with threshold alerts; launch time and main-thread hangs if you turn them on | Duration events, charted as a histogram you configure |
| Revenue | No | Purchases preset and RevenueCat integration |
| Your AI agent | A read-only context pack of aggregate counts, with reading instructions: copied, downloaded or fetched over MCP | An MCP server your agent queries directly |
| SDKs | Swift (iOS, macOS), Android, web | Swift (iOS, macOS, visionOS), Android, Flutter, React Native, web |
| Free plan | 100,000 events a month, 2 apps | 50,000 events a month for accounts opened since July 1, 2026 |
| Entry paid plan | $9 a month: 1,000,000 events, 5 apps | €9 a month: 750,000 events, unlimited apps |
| How long data is kept | 13 months, every plan | 24 months on the entry paid plan |
| Hosting | AWS, United States (us-east-1); a US company | EU (Germany and the Netherlands); a German company |
| Open source | SDKs (MIT) | SDKs |
Choose TelemetryDeck if
- You need to count people: daily and monthly active users, new installs, or how many come back a week later.
- You want to follow installations through a sequence, or slice any query by any parameter in a query language and notebooks.
- You track purchases and want RevenueCat data next to your usage data.
- You ship with Flutter or React Native. Trackless has no SDK for either yet.
- Your data must stay in the EU with an EU company. TelemetryDeck hosts in Germany and the Netherlands; Trackless hosts in the United States.
- You want more than 13 months of history.
Choose Trackless if
- You want analytics that hold nothing per person or per install, so there is nothing to protect, disclose, or delete about any individual.
- You want the App Store label to show no Identifiers. TelemetryDeck's own guide has you declare a Device ID.
- You care about what is failing and how slow it is: errors per session, p50 / p90 / p99 timing, and email alerts when error rates climb, a measurement crosses a threshold you set, or an app goes silent.
- You work with a coding agent and want to hand it your app's production numbers as a bounded, readable pack with no personal data in it.
- You want 100,000 free events a month on a new account, or 1,000,000 for $9.
What is different under the hood
For the general case, A hashed ID is still an ID explains what a stored identifier, hashed or not, lets someone link together, and where Trackless's own protection runs out.
The identifier
TelemetryDeck's SDKs accept a custom user identifier, such as an email address. If you don't supply one, they generate a random one, and on some platforms ask the operating system for one, such as iOS's identifierForVendor. The SDK salts and hashes it on the device, and the server salts and hashes it again, so neither you nor TelemetryDeck can recover the original. The result stays constant for each installation, and with the same salt and the same original identifier you can recognize the same person across platforms (TelemetryDeck: anonymization).
That is a careful design, and it is what makes user counts and retention possible. It is also still an identifier: two events from the same installation can be told apart from two events from different ones.
Trackless sends no identifier at all. A session lives in memory on the device and ends when the app goes to the background; the next launch is a new, unrelated session. Ingest adds each event to a daily count for its name and coarse context (platform, OS version, device class, app version, region, language), and nothing is written per event. Two sessions on the same phone are indistinguishable from two sessions on two phones, so there is nothing to link.
The App Store label
TelemetryDeck's guide tells you to declare Device ID under Identifiers in its default mode, "what identifies individual users to TelemetryDeck", not linked to identity and not used for tracking. If you supply your own identifier, you declare User ID instead (TelemetryDeck: Apple's app privacy details).
With Trackless you declare Product Interaction, Other Diagnostic Data, and Performance Data (and Crash Data, if you turn on uncaught-exception counts), none linked to the user, none used for tracking, and nothing under Identifiers. The privacy guide walks through every screen, and the Google Play Data safety answers too.
What is kept, and for how long
Each TelemetryDeck signal is stored with the anonymized ID, the action, a timestamp rounded to the hour, and device metadata such as the model. TelemetryDeck has no schedule for deleting events in cold storage and expects to delete them after 7 to 10 years, without guaranteeing it. Analytics data is kept when an account closes (TelemetryDeck: privacy FAQ).
Trackless keeps aggregate counts for 13 months, then deletes them automatically. Deleting your account deletes your apps' data after a 7-day grace period.
Handing production to your agent
TelemetryDeck runs an MCP server, so your AI agent can query your TelemetryDeck data directly, as often as it likes, from your side (TelemetryDeck: MCP). That gives an agent live access to everything TelemetryDeck stores.
Trackless gives your agent something different: one app's Agent pack, the aggregate counts for the window you choose with the instructions that tell an agent how to read them. You can copy or download it from the Agent pack page, or let your agent fetch it itself from Trackless's read-only MCP endpoint with a read token (Connect your agent). Either way it is a pack, not live query access into signals stored per installation. Storage is aggregate-only, so a whole app's production fits in a context window, and there is no personal data in the pack, because there is none anywhere. Trackless calls no model. Once your agent has the pack, those counts sit with whichever service it uses, under its terms.
Pricing
TelemetryDeck changed its pricing on July 1, 2026. Accounts opened since then get 50,000 free events a month; accounts opened before keep 100,000, and existing paid customers keep their plan and price until they change it or are auto-upgraded after two months at their limit (TelemetryDeck: pricing update). Its entry paid plan is €9 a month for 750,000 events, with unlimited apps and 24 months of data (TelemetryDeck: pricing calculator).
Trackless Free is 100,000 events a month for 2 apps, with no credit card. Indie is $9 a month for 1,000,000 events and 5 apps. Trackless never upgrades a plan automatically and never charges overage. All plans are on the pricing table.
Moving from TelemetryDeck
The calls map closely. Trackless takes one optional detail value per event rather than a dictionary of parameters, because each value becomes its own aggregate count.
| TelemetryDeck (Swift) | Trackless (Swift) |
|---|---|
TelemetryDeck.signal("exportTapped") | Trackless.feature("export") |
signal("exportTapped", parameters: ["format": "csv"]) | Trackless.feature("export", detail: "csv") |
startDurationSignal / stopAndSendDurationSignal | Trackless.startTimer("sync") / Trackless.stopTimer("sync") |
TelemetryDeck.errorOccurred(id: "ImportObject.jsonDecode") | Trackless.error("import_failed", code: "json_decode") |
Anything that depends on telling installations apart, such as user counts or retention, has no equivalent. The documentation covers each platform, and every SDK ships a guide written for coding agents, so you can point yours at it and let it do the migration.
Sources
Every TelemetryDeck fact here comes from TelemetryDeck's own pages, linked above, read on October 26, 2026. Products change; if something on this page is out of date, tell us at feedback@tracklesstelemetry.com and we will correct it.