About Respectlytics
Mobile analytics that tracks events, not people. Made by a company in Sweden, with the SDKs and the server open source.
Return of Avoidance
The idea behind every decision: data you never collect needs no protecting.
Most analytics platforms collect as much as they can, then try to anonymize it later. That is complex to get right, risky when it goes wrong, and it asks people to trust a promise they cannot check.
Respectlytics goes the other way. It was designed from the start to leave personal data out, so what it stores is short enough to explain field by field, and the API refuses anything else.
What that means in practice
Enforced by the SDKs and the API, not by a setting someone can change.
No device IDs
The SDKs never read the IDFA, the IDFV, the Advertising ID or the Android ID, and Respectlytics stores no user IDs.
Sessions in memory only
A random session ID that lives in memory, is replaced every two hours and on each launch, and is never written to disk.
The country, not the IP address
The IP address is used to look up the country and then discarded. What is stored is a code such as US or DE.
Five fields per event
Event name, timestamp, session ID, platform and country. No custom properties that could carry personal data.
What we hold ourselves to
Four principles, and how each one shows up in the product.
Transparency
We say exactly what is collected and why. The SDKs and the server are open source, so you can read the code instead of trusting us.
Less to defend
Data is minimized by design, not by policy. When someone asks about your analytics, the answer is short.
A reason for every field
We can explain why event_name, timestamp, session_id, platform and country exist, and why nothing else does.
Respect
The people using your app are people, not data points. You can learn how your app is used without knowing who they are.
Why I built Respectlytics
Sinan, founder
I have developed mobile apps for over six years. Analytics has always been the most frustrating part, not because it is 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 far more data than I needed: device IDs, advertising identifiers, precise locations. Data I would then have to explain in privacy policies, App Store labels and consent dialogs.
So I built my own. Respectlytics tracks events, not people. It answers "what happened in my app?" without answering "who did it?"
I am sharing it because other developers face the same problem. You should not have to choose between understanding your app and respecting the people who use it.
Open source, so you can check
MIT-licensed SDKs, and an AGPL-3.0 server you can run yourself.
Read exactly what runs in your app, have your security team review it, and see for yourself that nothing else is collected. Bug fixes and improvements come from the people who use it.
- Swift Swift Package Manager, SwiftUI and UIKit iOS 15 and macOS 12 or later.
- Kotlin One Gradle line from Maven Central Android 7.0 (API level 24) and later.
- Flutter One package for five platforms iOS, Android, macOS, Linux and Windows.
- React Native Works with Expo and bare projects React Native 0.70 and later, with TypeScript types.
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 and change over time. Consult your legal team to determine the requirements that apply to your situation.