About Respectlytics
Analytics that tracks events, not people
Our Philosophy: Return of Avoidance
Most analytics platforms collect as much data as possible, then try to "anonymize" or "de-identify" it later. This approach is legally risky, technically complex, and fundamentally disrespectful to users.
We believe the best way to handle sensitive data is to never collect it in the first place.
This is what we call Return of Avoidance (ROA). Instead of building complex systems to protect data after collection, we architected Respectlytics to avoid collecting personal data from the start. The result? A system that's transparent about what it collects, defensible because it minimizes data by design, and clear about why each field exists.
What This Means In Practice
No Device IDs
We never touch IDFA, GAID, ANDROID_ID, or any persistent device identifier. Your users remain anonymous by design.
RAM-Only Sessions
Session identifiers exist only in device memory. They rotate every 2 hours and disappear when the app closes. Never written to disk.
Transient IP Processing
IP addresses are processed for country lookup, then immediately discarded. We store "US" or "DE"βnever the actual IP.
5 Fields. That's It.
Every analytics event in Respectlytics contains exactly 5 fields:
event_name
What happened
timestamp
When
session_id
Ephemeral link
platform
iOS/Android
country
Geo only
No user IDs. No device fingerprints. No custom properties that could leak PII. The API rejects anything else.
Our Values
The principles that guide every decision we make
Transparency
We're clear about exactly what data is collected and why. No hidden trackers, no surprise data sharing, no buried terms. Our SDKs are open sourceβyou can verify everything yourself.
Defensibility
We minimize data by design, not by policy. When you're asked about your analytics setup, you can confidently explain that you collect only what's essential. Less data means less risk.
Clarity
Every field we store has an explicit purpose. We can explain why event_name, timestamp, session_id, platform, and country existβand why nothing else does.
Respect
We treat app users as people, not data points. We don't need to know who they are to understand how they use your app. Analytics should serve developers without surveilling users.
Meet the Founder
Why I Built Respectlytics
I've developed mobile apps for over 6 years. Analytics has always been the most frustrating partβnot because it's technically hard, but because of the privacy implications.
I have no interest in tracking people. But like any developer, I need to understand how my apps are used. Which features work? Where do users get stuck? What drives conversions?
Every analytics tool I tried collected way more data than I neededβdevice IDs, advertising identifiers, precise locations. Data I'd then have to explain in privacy policies, App Store labels, and consent dialogs.
So I built my own solution. Respectlytics tracks events, not people. It answers "what happened in my app?" without answering "who did it?"
I'm sharing this tool because I believe other developers face the same problem. You shouldn't have to choose between understanding your app and respecting your users.
Open Source Commitment
Trust, but verify. All our SDKs are open source so you can see exactly what code runs in your app.
Why Open Source?
- β Verify claims β Don't take our word for it. Read the code.
- β Security audits β Your security team can review exactly what data is collected.
- β No hidden trackers β Unlike closed-source SDKs, there's nowhere to hide.
- β Community contributions β Bug fixes and improvements from real users.
Ready to try privacy-first analytics?
Get started in minutes. No credit card required for free tier.
Legal Disclaimer: This information is provided for educational purposes and does not constitute legal advice. Regulations vary by jurisdiction and change over time. Consult your legal team to determine the requirements that apply to your situation.