A PostHog alternative that keeps nothing per person
The short answer
PostHog is an all-in-one product platform: analytics, session replay, feature flags, experiments, surveys, error tracking, a data warehouse, and more, with a large free tier and an open-source core you can host yourself. If you want one tool for all of that, PostHog is a strong choice, and Trackless does not try to replace it.
PostHog gives every event a distinct ID. Before you identify someone, the SDK generates an anonymous one; when you call identify, PostHog creates a person profile and merges the earlier anonymous events into it. On the web it stores that ID in a first-party cookie by default.
Trackless stores no identifier of any kind and no individual events, only aggregate counts per day. It cannot show you a person's path, replay a session, or target a feature flag at a user. What you get instead is analytics with nothing in it that could single out a person.
If you need to know what a particular user did, PostHog 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
| Trackless | PostHog | |
|---|---|---|
| Identifier stored | None | A distinct ID on every event; person profiles once you identify someone |
| Individual events stored | No, only daily aggregate counts | Yes, anonymous events included |
| Web storage | None: no cookies, localStorage, or sessionStorage | localStorage plus a first-party cookie by default; in-memory mode available |
| IP address | Never read; region comes from the device's settings | Captured or discarded per project; off by default for EU organizations |
| User paths and retention | No | Yes |
| Conversion funnels | Aggregate step counts | Yes, per person |
| 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 | Error tracking |
| Session replay, feature flags, experiments, surveys | No | Yes |
| 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 uses directly |
| SDKs | Swift (iOS, macOS), Android, web | iOS, Android, web, React Native, Flutter, and many more |
| Free plan | 100,000 events a month, 2 apps | 1,000,000 analytics events a month, 1 project |
| How long data is kept | 13 months, every plan | 1 year on the free plan, 7 years on paid plans |
| Open source | SDKs (MIT) | Yes; a self-hosted deploy under MIT, officially unsupported |
Choose PostHog if
- You want to see what individual users did: paths, retention, session replays.
- You want feature flags, experiments, surveys, and analytics in one tool, billed together.
- Your product is a web app with signed-in users you want to identify.
- You need more than 100,000 free events a month. PostHog's free tier is ten times larger.
- You want to host it yourself, or query raw events with SQL.
- You ship with React Native or Flutter. Trackless has no SDK for either yet.
Choose Trackless if
- You want analytics that hold nothing per person, so there is nothing to protect, disclose, or delete about any individual.
- Your web app should set no cookies and write nothing to the browser for analytics. Trackless's web SDK uses no device storage at all.
- 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.
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
Every PostHog event has a distinct ID that groups events together. Before identify is called, the SDK generates an anonymous one, and those events are still captured and stored. When you identify someone, PostHog creates a person profile and merges their anonymous events into it (PostHog: people). On iOS the anonymous ID is a random UUID (PostHog: iOS configuration).
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.
Cookies and consent on the web
PostHog's web SDK stores its state in localStorage and a first-party cookie by default, including the distinct ID and session ID; the cookie lasts 365 days. You can switch to in-memory storage, for example until someone consents (PostHog: persistence). PostHog's GDPR guide says to ask for consent when you track users in your product, and to show a cookie banner if you use cookies for logged-out visitors (PostHog: GDPR).
Trackless's web SDK sets no cookies and uses no localStorage, sessionStorage, or IndexedDB, and it reads nothing back from the browser. The privacy guide explains what that means for consent.
The IP address
PostHog lets each organization and project choose whether client IP addresses are captured or discarded; EU organizations default to discarding them (PostHog: privacy controls). Trackless's application code never reads the IP address. Region comes from the device's own region setting, which the person controls.
What is kept, and for how long
PostHog keeps events for 1 year on the free plan and 7 years on paid plans (PostHog: pricing). 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
PostHog runs a free, hosted MCP server, so your agent can query your PostHog data, run SQL, and change things such as feature flags from a prompt (PostHog: MCP). That gives an agent live access to everything PostHog 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 against a distinct ID. 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
PostHog's free plan includes 1,000,000 analytics events, 5,000 session recordings, and 100,000 exceptions a month, for 1 project; usage stops at the free limits. After the first million, anonymous events cost $0.00005 each and identified events $0.000198 each (PostHog: pricing).
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 PostHog
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.
| PostHog (Swift) | Trackless (Swift) |
|---|---|
PostHogSDK.shared.capture("export") | Trackless.feature("export") |
capture("export", properties: ["format": "csv"]) | Trackless.feature("export", detail: "csv") |
PostHogSDK.shared.screen("Settings") | Trackless.view("settings") |
identify, person properties, groups, session replay, and feature flags 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 PostHog fact here comes from PostHog'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.