An Aptabase alternative that never reads the IP address
The short answer
Aptabase and Trackless are close. Both are small, privacy-first analytics for apps, neither SDK sends a device identifier, and with either one you declare nothing under Identifiers on your App Store label. Aptabase is open source end to end, server included, and has SDKs for far more platforms.
Aptabase stores every event individually. Its server derives a user ID for each event from a hash of the client's IP address and user agent, with a salt that is different for each app and thrown away every 24 hours. That daily ID is what lets it count daily users.
Trackless never reads the IP address and stores no individual events, only aggregate counts per day. It has no daily-user count and no session timeline. In exchange there is nothing in it, even for a day, that could single out a person.
If you want a self-hosted server, an SDK for your engine or framework, or a daily user count, Aptabase answers that and Trackless does not. If you want funnels, timing percentiles, and alerts, with no IP processing and nothing per event, Trackless is built for that.
At a glance
| Trackless | Aptabase | |
|---|---|---|
| Identifier stored | None | A user ID per event, hashed from IP and user agent with a daily salt |
| Session ID | None leaves the device | Sent with every event; a new one after an hour idle |
| Individual events stored | No, only daily aggregate counts | Yes |
| IP address | Never read; region comes from the device's settings | Hashed into the daily user ID; country, region, and city stored per event |
| Device model | Not collected; device class only (phone, tablet, desktop) | Collected by the Swift SDK and stored per event |
| App Store privacy label | Product Interaction and diagnostics, no Identifiers | Product Interaction, no Identifiers |
| Daily users | No | Yes |
| Conversion funnels | Aggregate step counts | Not found in its docs or source |
| 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 | In beta, with stack traces |
| Timing | p50 / p90 / p99 and a duration histogram per measurement, with threshold alerts; launch time and main-thread hangs if you turn them on | Not found in its docs or source |
| SDKs | Swift (iOS, macOS), Android, web | Swift, Android, Flutter, React Native, Electron, Tauri, .NET MAUI, web, Unity, Unreal, Godot, and more |
| Free plan | 100,000 events a month, 2 apps | 20,000 events a month, unlimited apps |
| 1,000,000 events a month | $9 (Indie, 5 apps) | $20 |
| How long data is kept | 13 months, every plan | Up to 5 years |
| Hosting | AWS, United States (us-east-1); a US company | EU or US, your choice; a Romanian company |
| Open source | SDKs (MIT) | Server (AGPL-3.0, self-hostable) and SDKs (MIT) |
Choose Aptabase if
- You want to run the server yourself, or read every line of it.
- You build with Flutter, React Native, Electron, Tauri, .NET MAUI, or a game engine. Trackless has no SDK for those.
- You want a daily user count, a live view, or a timeline of each session's events.
- You want error reports with stack traces.
- Your data must stay in the EU. Trackless hosts in the United States.
- You have many small apps. Aptabase allows unlimited apps on every plan.
Choose Trackless if
- You want no IP processing at all. Aptabase hashes the IP address into a daily ID; Trackless's application code never reads it.
- You want counts kept, not events: nothing per event and nothing per day per person.
- You care about what is failing and how slow it is: funnels, 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, 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 daily user ID
Aptabase's SDKs send no device identifier. Instead, its server generates a user ID from the client's IP address and user agent with a salt that differs for each app and is thrown away every 24 hours, so sessions on different days or in different apps cannot be correlated (Aptabase: privacy policy, updated July 24, 2026). The source shows a SipHash of IP and user agent keyed with that daily salt (Aptabase source: DailyUserHasher). Within a day, events that share that ID can be grouped together. The SDK also sends a session ID, replaced after an hour without activity (Aptabase Swift SDK).
Trackless sends no identifier and no session ID, and never reads the IP address. 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.
What is kept, and for how long
Aptabase's events table stores, for each event, the timestamp, event name, user ID, session ID, OS, locale, app version, country, region, city, and your custom properties (Aptabase source: events table), and a later migration adds the device model. Its privacy policy says analytics data is stored for up to 5 years.
Trackless keeps aggregate counts for 13 months, then deletes them automatically. Deleting your account deletes your apps' data after a 7-day grace period.
The App Store label
Aptabase's guide says the only data type to select for it is Product Interaction, with nothing under Identifiers (Aptabase: Apple App Privacy). With Trackless you declare Product Interaction, Other Diagnostic Data, and Performance Data, because it also counts errors and timing (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.
Handing production to your agent
Your agent gets 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). Trackless calls no model. Because storage is aggregate-only, a whole app's production fits in a context window, and there is no personal data in the pack, because there is none anywhere. Once your agent has the pack, those counts sit with whichever service it uses, under its terms.
Pricing
Aptabase is free up to 20,000 events a month, then $10 for 200,000, $20 for 1,000,000, and $75 for 5,000,000, with unlimited apps on every plan. It charges no overage: past your limit, it turns analytics off until the next month (Aptabase: pricing, as archived on October 10, 2026).
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, and Pro is $49 a month for 5,000,000 events and 25 apps. Trackless never upgrades a plan automatically and never charges overage. All plans are on the pricing table.
Moving from Aptabase
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.
| Aptabase (Swift) | Trackless (Swift) |
|---|---|
Aptabase.shared.trackEvent("export") | Trackless.feature("export") |
trackEvent("export", with: ["format": "csv"]) | Trackless.feature("export", detail: "csv") |
trackEvent("screen_view", with: ["name": "Settings"]) | Trackless.view("settings") |
Aptabase.shared.trackError(error) | Trackless.error("import_failed", code: "json_decode") |
Daily users and session timelines have no equivalent, and Trackless keeps no stack traces. 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 Aptabase fact here comes from Aptabase's own pages and its public source code, 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.