A Mixpanel alternative that never identifies anyone

Trackless Telemetry and Mixpanel, compared

Checked against Mixpanel's own documentation on October 26, 2026

The short answer

Mixpanel is deep product analytics built around people: funnels, flows, retention, saved user groups, session replay, heatmaps, experiments, and feature flags, with a generous free plan. If you need to understand how individual users move through your product, Mixpanel is built for exactly that, and Trackless is not.

Mixpanel generates a device ID in its SDK and attaches it to every event. When someone signs in and you call identify, Mixpanel joins that device's earlier events to the user, retroactively, across sessions and devices.

Trackless stores no identifier of any kind and no individual events, only aggregate counts per day. It has nothing to join, so it offers no user profiles, no per-user funnels, and no retention curves. What you get instead is analytics with nothing in it that could single out a person.

If you need to know what each user did, Mixpanel 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 person, Trackless is built for that.

At a glance

TracklessMixpanel
Identifier storedNoneA device ID on every client event, joined to your user ID after sign-in
Individual events storedNo, only daily aggregate countsYes
User profilesNoYes
IP addressNever read; region comes from the device's settingsUsed for country, region, and city by default, then discarded
Device detailsDevice class only (phone, tablet, desktop)Model, manufacturer, carrier, and screen size by default
Funnels, flows, and retentionAggregate funnel step counts onlyYes, per user
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 Not among its listed products
Session replay, heatmaps, experiments, feature flagsNoYes
Your AI agent A read-only context pack of aggregate counts, with reading instructions: copied, downloaded or fetched over MCP Mixpanel AI, and a hosted MCP server your agent queries directly
SDKsSwift (iOS, macOS), Android, webJavaScript, iOS, Android, React Native, Flutter, Unity
Free plan100,000 events a month, 2 apps1,000,000 events a month
How long data is kept13 months, every planEvents 2 years (5 years for projects created before September 1, 2025)
HostingAWS, United States (us-east-1)US on Google Cloud by default; EU residency chosen when a project is created

Choose Mixpanel if

  • You need to follow users: who converted, who came back, what path they took, and how one group of users compares with another.
  • Your product has sign-in and you want behavior joined across devices.
  • You want session replay, heatmaps, experiments, and feature flags in the same tool.
  • You need more than 100,000 free events a month. Mixpanel's free plan is ten times larger.
  • Your data must stay in the EU. Trackless hosts in the United States.
  • You ship with React Native, Flutter, or Unity. Trackless has no SDK for those.

Choose Trackless if

  • You want analytics that hold nothing per person, so there is nothing to protect, disclose, or delete about any individual, and no profile to export when someone asks.
  • You want an App Store label with nothing under Identifiers.
  • 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 a flat monthly price: 1,000,000 events 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

Mixpanel's client SDKs generate a $device_id, persist it, and attach it to all of a user's events. When you call identify with your own user ID, Mixpanel retroactively sets that user ID on earlier events with the same device ID, so the two event streams are joined, including from other devices once the person signs in there (Mixpanel: identifying users). On iOS the device ID is a random UUID unless you opt in to the vendor identifier (Mixpanel: Swift SDK).

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.

Location and device details

By default, Mixpanel looks up each request's IP address to set country, region, and city on your events and profiles, then discards the IP before ingestion (Mixpanel: geolocation). Its mobile SDKs add the device model, manufacturer, carrier, and screen size as default properties (Mixpanel: default properties).

Trackless's application code never reads the IP address. Region comes from the device's own region setting, which the person controls, and device context stops at the class: phone, tablet, or desktop.

What is kept, and for how long

Mixpanel deletes events after 2 years; projects created before September 1, 2025 keep 5 years until their plan changes. User profiles are kept for as long as the subscription is active (Mixpanel: GDPR compliance).

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

Mixpanel runs a hosted MCP server that gives AI assistants direct access to your Mixpanel data: events, funnels, flows, retention, session replays, and more (Mixpanel: MCP server). That gives an agent live access to everything Mixpanel 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 events stored per device and user. 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

Mixpanel's free plan includes up to 1,000,000 events and 10,000 session replays a month, with funnels and retention analysis. Growth starts at $0 and is billed by usage above that (Mixpanel: pricing, as archived on October 17, 2026). The free plan limits saved reports to 5 per user (Mixpanel: plan differences).

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 Mixpanel

The calls map closely. Trackless takes one optional detail value per event rather than a dictionary of properties, because each value becomes its own aggregate count.

Mixpanel (Swift)Trackless (Swift)
Mixpanel.mainInstance().track(event: "Export")Trackless.feature("export")
track(event: "Export", properties: ["format": "csv"])Trackless.feature("export", detail: "csv")

identify, people properties, groups, and anything else that depends on telling users apart have 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 Mixpanel fact here comes from Mixpanel's own pages, linked above, read on October 26, 2026. Where a page is linked through the Internet Archive, the date is the date of that copy. Products change; if something on this page is out of date, tell us at feedback@tracklesstelemetry.com and we will correct it.