See why users convert. Never who they are.
Respectlytics finds the paths that lead to a purchase and the steps where people give up, from five fields per event. No user IDs, no device IDs, and nothing stored on the phone.
14-day free trial, no credit card needed.
What you no longer have to deal with
Each one is removed by how the SDKs and the API are built, not by a setting someone can forget.
A tracking prompt from your analytics
The SDKs never read the IDFA or the Android Advertising ID, so they add no ATT prompt and no AD_ID permission.
A long privacy label
Five fields make a short, explainable entry in your App Store privacy label and Google Play Data Safety form.
Identifiers on the phone
The session ID and the event queue live in memory. Nothing is written to the device for analytics.
Personal data in your analytics
No user IDs, device IDs or IP addresses are stored, so there is nothing about one person to look up or protect.
What you see in Respectlytics
All of it comes from the five stored fields. Nothing about who the user is.
Conversion paths
The most common sequences of events in sessions that converted, found for you once you name your conversion events.
Drop-offs
The steps where sessions end, ranked by how many sessions each one loses.
Funnels
Any sequence of events you choose, with the conversion and the time taken at each step.
Conversion drivers
The events that sessions which converted did more often than the rest, with the size of the difference.
Segments
Conversion compared by platform, country, session depth and hour of day.
Open the live demo
Every view above, running on sample data. No signup.
One line per event
Configure the SDK once at launch, then call track() where things happen.
Respectlytics.configure(apiKey: "your-api-key")
Respectlytics.track("signup_completed")
Respectlytics.track("purchase_completed")
Respectlytics.configure(Configuration(apiKey = "your-api-key"))
Respectlytics.track("signup_completed")
Respectlytics.track("purchase_completed")
await Respectlytics.configure(apiKey: 'your-api-key');
await Respectlytics.track('signup_completed');
await Respectlytics.track('purchase_completed');
Respectlytics.configure('your-api-key');
Respectlytics.track('signup_completed');
Respectlytics.track('purchase_completed');
Using an AI coding assistant? The SDK page has a prompt that plans 10 to 20 events and adds the calls; review what it writes. The event plans show what to track in each part of an app.
Check it yourself
Privacy you can read in the code, hosted where you can name the region.
Open source
MIT-licensed SDKs and an AGPL-3.0 server. Read what runs in your app and what the API keeps.
Self-host for free
The Community Edition runs on your own servers with Docker and PostgreSQL.
EU-hosted, built in Sweden
The managed service runs on servers and databases in the EU.
Is it right for your app?
Respectlytics answers questions about sessions and steps, never about people. That suits many apps and not all of them.
A good fit if you want to
- see where users drop off and which paths lead to a purchase
- keep advertising IDs and the ATT prompt out of your analytics
- declare a short list in your App Store and Google Play privacy forms
- read the code that runs in your app, or host the server yourself
Not a fit if you need
- one person's journey across days, or retention cohorts of people
- properties on events, such as price, plan or screen size
- install attribution or ad campaign measurement
- session replay, feature flags or experiments
Find your starting point
Whether you are switching tools, planning events or working in a sensitive field.
Questions buyers ask
Straight answers, including the ones that might send you elsewhere.
What is privacy-first mobile app analytics?
Analytics built so that it never needs to know who a user is. Respectlytics stores five fields per event: the event name, a rotating session ID, a timestamp, the platform and the country. It reads no device identifiers and writes nothing to the phone, and still shows conversion paths, drop-offs and funnels.
How does it count users without tracking them?
It counts sessions, not people. Each session gets a random ID that lives in memory and is replaced every two hours and on every launch. The server stores a hash of it salted with your app and the date, so sessions are never linked to each other.
What do I lose compared with Firebase or Mixpanel?
Anything that needs to know a person: one user's journey across days, user profiles, retention cohorts of people and event properties such as price. If you rely on those, a user-based tool fits better.
Do I still need a consent banner or the ATT prompt?
Your legal team decides that, based on everything your app does. Respectlytics never reads the IDFA and writes nothing to the device for analytics, so it gives your app no reason to show the ATT prompt.
Can I host it myself?
Yes. The Community Edition is free and open source under AGPL-3.0 and runs with Docker and PostgreSQL. The managed service adds automated path discovery, drop-off detection and segment comparison, hosted in the EU.
How is it priced?
By the number of events per month, with unlimited apps on every plan and a 14-day free trial without a credit card. Current prices are on the pricing page.
Apps that use Respectlytics
Apps in the stores today that send their events to Respectlytics.
Using Respectlytics in your app? Ask to be featured here
Why I built Respectlytics
Sinan, founder
I have developed several mobile apps over the years, and analytics was always one of the hardest problems because of privacy. I have no interest in tracking people, but like any app developer, I need to understand how my apps are used and how to improve them.
So I built my own solution. Respectlytics is built to track events, not people. It solves my problem, and I hope it helps other app developers and businesses too.
Try it on your own app
14-day free trial, no credit card. Unlimited apps on every plan.
This information is provided for educational purposes and does not constitute legal advice. Regulations vary by jurisdiction, so consult your legal team to determine the requirements that apply to your app.