Frequently Asked Questions

Firebase Analytics collects device identifiers (IDFA/GAID), IP addresses, and allows custom user properties that can contain PII. Respectlytics architecturally blocks all of this—we only store 5 fields:

• event_name
• session_id (rotates every 2 hours)
• timestamp
• platform
• country (derived from IP, IP never stored)

Plus, we provide automated conversion intelligence that Firebase requires manual setup and analysis to achieve.

Unlike traditional analytics where you manually build funnels and analyze data, Respectlytics automatically:

• Discovers your top conversion paths
• Calculates which events drive conversions (lift scores)
• Identifies where users drop off
• Compares segments (iOS vs Android, by country)

All without any configuration. Insights appear as soon as data flows in.

This can save you several hours per month that you'd otherwise spend building reports and analyzing data manually.

No. Our algorithms are statistical and completely transparent—not AI/ML black boxes.

Lift scores are simple ratios comparing conversion rates. Path discovery uses frequency counting. Every insight shows its supporting data so you can verify the numbers yourself.

We believe in explainable analytics.

We store exactly 5 fields: event_name, session_id, timestamp, platform, and country.

Session IDs rotate every 2 hours and are stored only in RAM (never persisted to device storage). IP addresses are used transiently for country lookup then immediately discarded.

Our API rejects any additional fields—it's architecturally impossible to send us PII.

All data is stored in EU data centers. We're a Swedish company subject to EU data protection laws.

Significantly. Less data = simpler compliance audits. When you don't collect personal data, you have less to document, explain, and protect.

Our approach follows the principle of "Return of Avoidance"—the best way to protect data is to never collect it in the first place.

Note: Consult your legal team to determine your specific requirements.

No, by design. Our 2-hour session rotation makes persistent user tracking impossible.

If you need MAU/DAU metrics, consider tools that use persistent identifiers—but understand the privacy tradeoffs involved. Persistent user tracking requires storing identifiers that can re-identify users across sessions, which is exactly what we avoid.

We believe being honest about this limitation builds more trust than hiding it.

Because Respectlytics stores only anonymous data (5 fields, no user IDs), it is technically impossible to identify which entries belong to a specific person.

However, you can use filter-based deletion via the dashboard or API (by date range, platform, country) to remove data that may correlate with a user based on your own records. Over-deletion of anonymous data is acceptable.

See our Data Deletion Guide for step-by-step instructions and API examples.

"Free" analytics tools have hidden costs:

• Your users' data becomes the product — free tiers often monetize through advertising profiles
• Manual work adds up — building funnels, analyzing paths, creating reports takes 8-10+ hours per month
• Privacy complexity — complex privacy labels, consent requirements, and audit headaches

With Respectlytics, you're not paying for data collection. You're paying for:

• Automated intelligence — conversion paths, lift scores, and drop-offs discovered automatically
• Architectural privacy — only 5 fields stored, no PII possible by design
• Time back — insights appear in minutes, not after hours of manual setup

The time you save on manual analysis often pays for Respectlytics many times over.

We're a bootstrapped company—no VC funding.

Companies with generous free tiers often monetize through data or cut corners on privacy. We chose a different path: charge fairly from day one and make privacy our core architecture, not an afterthought.

You get a 14-day free trial with 20,000 events to evaluate us fully.

Every plan includes:

• Automated conversion analysis — paths, lift scores, drop-offs
• Segment comparisons — iOS vs Android, by country
• Privacy architecture — only 5 fields stored, no PII possible
• Unlimited apps (on all plans)
• 2-year data retention

You're not just paying for event storage—you're paying for automated analysis that would otherwise require manual work.

After 14 days, you'll need to choose a paid plan to continue using Respectlytics. Your data from the trial period is preserved.

We offer flexible plans based on how many events you need per month. No credit card required during trial. View our pricing plans.

We have native SDKs for:

• Swift (iOS)
• Kotlin (Android)
• Flutter (cross-platform)
• React Native (cross-platform)

All SDKs are open source and enforce the same strict 5-field schema.

A few minutes.

Add the SDK dependency, initialize with your API key, and call track("event_name"). That's it.

No complex configuration, no property mapping, no data layer setup.

Yes. Our REST API provides endpoints for:

• Event summaries with time-series data
• Event counts with flexible filtering
• Geographic breakdowns by country
• Funnel analysis with step-by-step conversion rates
• Event types & filter options for dynamic UIs

You can query your analytics data programmatically and build dashboards in any framework or BI tool you prefer.

All API requests are authenticated using an app key (UUID). Include it via the X-App-Key HTTP header:

You create apps and obtain keys from the Respectlytics dashboard. Each app gets its own key, so you can separate analytics by project.

The API provides rich querying capabilities:

• Summaries — time-series data with configurable granularity
• Counts — total events with date, platform, and country filters
• Geo data — event distribution by country
• Funnels — multi-step conversion analysis
• Event types — list of all tracked event names
• Recent activity — latest events for real-time monitoring

All endpoints support filtering by date range, platform, country, and event name.

Yes to both.

• Export — download your data as CSV via the export endpoint
• Delete — preview exactly what would be removed before confirming (dashboard or API)
• Audit trail — full deletion history for your compliance records

You own your data completely. No lock-in, no surprises.

For handling user erasure requests, see our Data Deletion Guide.

Our complete API Reference is available at:

• API Reference — full endpoint documentation with schemas and examples
• Interactive Swagger UI — test endpoints directly in your browser

Both pages cover all endpoints, request/response schemas, authentication details, and error codes.