Frequently asked questions
How Respectlytics works, what it stores, what it costs and how to work with its API.
About the product
What Respectlytics is, and how it differs from the tools you know.
How is Respectlytics different from Firebase Analytics?
Respectlytics stores five fields per event and only the properties you declare, refuses unknown fields, reads no device identifiers, and works out conversion paths and drop-offs for you once you name your conversion events. Firebase Analytics ties events to an app instance ID and can use advertising IDs. See them side by side.
What do you mean by automated analysis?
Once you name your conversion events, Respectlytics works out the top conversion paths, a lift score for each event, where sessions drop off and how segments compare, with no reports to build. How it works.
Is this AI or machine learning?
No. Lift scores are ratios of conversion rates and paths are frequency counts. Every result shows the session counts behind it, so you can check the arithmetic.
Privacy and data
What is stored, where it lives, and what it means for your users.
How does the privacy architecture work?
Five fields are stored: event_name, session_id, timestamp, platform and country, and on a paid plan the properties you declared, each a value from your list or a number kept as a band. The session ID lives in memory on the device and is replaced every two hours and on each launch. The IP address is used to look up the country, then discarded. Any other field, such as a user ID or an email, makes the API answer 400 Bad Request, and nothing is saved. On a paid plan, a property is kept only when you declared it and its value; any other property is dropped.
Where is my data stored?
On servers and databases in the European Union. A company in Sweden runs the service.
Does this make compliance easier?
It leaves less to document: no user IDs, no device IDs and no IP addresses are stored. What your app needs, such as consent or an entry in your privacy policy, depends on everything it does, so decide that with your legal team.
Can I count monthly active users?
No, by design. Sessions are never linked, so there are no users to count. You can count active sessions per day, week or month. Counting people needs a tool that stores a persistent ID, with the privacy cost that comes with it.
How do I handle a user's deletion request?
No stored field ties an event to a person, so there is nothing to look up by user. If your own records show when and where someone used the app, you can delete by date range, platform and country; deleting a little more session data than needed does no harm. The data deletion guide has the steps.
Pricing and the free plan
How you pay, and what you get for it.
Is there a free plan?
Yes. Every account starts on it: one app, 20,000 events a month and the last 30 days of history, with every analytics feature and no time limit. No credit card is needed.
What do paid plans add?
More events each month, unlimited apps and two years of history. The plans differ in how many events they include: see pricing.
What happens at a plan's limit?
On the free plan, new events wait until the 1st of the next month, or until you upgrade. A paid plan keeps recording up to twice its monthly events while we email you, so your dashboard stays complete while you decide; beyond that, new events wait for the next billing period.
Why pay for analytics when Firebase is free?
A free tool is paid for some other way. Respectlytics is paid for by the people on its paid plans, and what they pay for is the analysis: paths, lift scores and drop-offs worked out for you, from data that holds no user or device IDs.
Integration
What it takes to add Respectlytics to an app.
Which SDKs are there?
Swift for iOS and macOS, Kotlin for Android, Flutter and React Native. All four are open source and send the same five fields, and only the properties you declare. Read the SDK docs.
What does an integration involve?
Add the package, call configure() once with your app key, and call track() where something happens. There are no free-form properties to map. Most of the work is choosing which events to track.
Developers and the API
Your data, from your own code.
Can I build my own dashboards with the API?
Yes. With a secret key from your account settings, the REST API returns events by day and by name, counts, countries, funnels, event names and the events themselves, so you can query your data from your own code or a BI tool.
How are API requests authenticated?
With two keys. The app key, sent in the X-App-Key header, ships inside your app and can only send events; each app has its own. Reading and deleting take a secret key you make in your account settings, sent as a Bearer token together with the app key of the app you want.
Can I export or delete my data?
Yes. With a secret key, export your events as CSV or JSON through the API. Delete by filter after previewing exactly what will be removed, in the dashboard or through the API. Every deletion is logged.
Where is the API reference?
The API reference documents sending events and every endpoint a secret key opens, and the interactive Swagger UI lets you try requests in the browser.
Still have a question?
Write to us. The people who build Respectlytics answer.
Try it on your own app
Free for one app and 20,000 events a month, no card needed. Unlimited apps on every paid plan.