A Firebase Analytics alternative that reads no device IDs

Firebase Analytics is free and deep. It also ties events to an app instance, can use advertising IDs, and brings the AD_ID permission into your Android build. Respectlytics shows funnels, conversion paths and drop-offs from five stored fields and no identifiers at all.

Start your free trial Try the live demo

14-day free trial, no credit card. The demo runs on sample data, no signup.

Why teams move off Firebase Analytics

Usually not because it is bad at analytics. Because of what comes with it.

The AD_ID permission. Firebase Analytics brings Android's advertising ID permission into your build through its dependencies, and Google Play then asks you to declare why your app uses it.
Identifiers on every event. Each event carries an app instance ID stored on the device, and your user ID once you call setUserId(). On iOS it can use the IDFA when your app links AdSupport and the user allows tracking.
Anything can go into a parameter. Events accept any parameters and user properties, so an email address or a user name can end up in your analytics through one careless line.
Long privacy forms. All of the above has to be declared in your App Store privacy label and Google Play Data Safety form.

Firebase Analytics and Respectlytics, side by side

Based on each product's public documentation as of 8 October 2026.

What it is about Firebase Analytics Respectlytics

What an event is tied to Firebase AnalyticsAn app instance ID kept on the device, plus your user ID if you call setUserId() RespectlyticsA random session ID kept in memory, replaced every two hours and on each launch

Advertising IDs Firebase AnalyticsCan use the IDFA on iOS and the Advertising ID on Android RespectlyticsNever read

Android AD_ID permission Firebase AnalyticsAdded to your build through its dependencies unless you remove it RespectlyticsNot added

Data per event Firebase AnalyticsAny parameters you send, plus user properties RespectlyticsEvent name only; the API rejects any other field

Location Firebase AnalyticsDown to city, derived from the IP address RespectlyticsCountry only; the IP address is discarded after the lookup

Source code Firebase AnalyticsThe analytics library is closed source RespectlyticsMIT-licensed SDKs and an AGPL-3.0 server you can host yourself

Funnels and paths Firebase AnalyticsFunnels you build in Google Analytics explorations RespectlyticsFunnels you build, plus conversion paths and drop-offs found for you

Cost Firebase AnalyticsFree RespectlyticsPaid plans by monthly events, with a 14-day free trial

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.

When Firebase Analytics is the better choice

Stay with it if one of these matters more to you than privacy.

You need analytics that costs nothing at any volume.
You build audiences for Google Ads, or export raw events to BigQuery.
You need one person's journey over days and weeks.
You report on event parameters such as price or content type.

Switching, step by step

The tracking calls map one to one. The parameters go away.

Before: Firebase Analytics

Analytics.setUserID(user.id)
Analytics.logEvent("purchase", parameters: [
    "value": 9.99,
    "currency": "EUR"
])

After: Respectlytics

Respectlytics.track("purchase_completed")

Install the Respectlytics SDK for Swift, Kotlin, Flutter or React Native, and configure it once at launch.
Replace each logEvent() call with track(), and drop the parameters. Remove setUserId() and setUserProperty() calls.
Remove the Firebase Analytics dependency: FirebaseAnalytics on iOS, firebase-analytics on Android, firebase_analytics in Flutter or @react-native-firebase/analytics. Keep the other Firebase libraries you use.
Check your merged Android manifest for the AD_ID permission, and update your privacy label and Data Safety form to match what your app now collects.

The Firebase migration generator turns your existing logEvent() calls into Respectlytics calls, in your browser.

Questions buyers ask

Straight answers, including the ones that might send you elsewhere.

Can I keep Crashlytics or Remote Config?

Yes. Firebase products are separate libraries. You can remove only the Analytics library and keep Crashlytics, Remote Config or Cloud Messaging.

Will my app still need the ATT prompt?

Respectlytics never reads the IDFA, so it gives your app no reason to show the prompt. Other libraries in your app may still need it, so check what else you ship.

Does removing Firebase Analytics remove the AD_ID permission?

Only if nothing else in your build adds it. Respectlytics never adds it. Check your merged manifest after the switch to see what is left.

Can I compare the two before switching?

Yes. Ship both for a few weeks and compare event counts per day. Expect differences in sessions and users, because the two tools count them in different ways.

How Respectlytics compares with the other tools teams move from.

Mixpanel Product analytics without user profiles Amplitude No user IDs, no IP addresses, no device IDs PostHog Only the analytics, self-hostable on PostgreSQL

Try it on your own app

14-day free trial, no credit card. Unlimited apps on every plan.

Start your free trial Read the SDK docs

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.