Respectlytics Respect lytics
Menu
⚖️ Comparison Guide

The Privacy-First
Mixpanel Alternative

Mixpanel uses distinct_id to track users across sessions and stores unlimited custom properties. Respectlytics stores only 5 essential fields with session-based IDs that rotate every 2 hours.

Try Respectlytics → View Pricing

Quick Comparison

See the key differences at a glance

Feature
📊 Mixpanel
Respectlytics Respectlytics
User Identification
⚠️ distinct_id Cross-session tracking
✅ session_id only Rotates every 2 hours
User Profiles
📝 Full user profiles Name, email, custom props
🛡️ No user profiles By design
Custom Event Properties
⚠️ Unlimited PII leak risk
🛡️ Not allowed API rejects extra fields
Data Fields Stored
📦 Extensive Events + profiles + properties
✅ 5 fields only Strict allowlist
Privacy Compliance Complexity
⚠️ Higher GDPR API, opt-out required
✅ Reduced No PII stored server-side
Conversion Intelligence
🔧 Manual funnels Define steps yourself
🤖 Automatic Auto-discovered
IP Address Handling
📍 Used for geolocation Can set ip=0 to disable
✅ Discarded after geo Never stored in analytics

Privacy Architecture

The fundamental difference in how user data is handled

📊

Mixpanel

Product analytics platform

What Mixpanel Collects:

  • ⚠️
    distinct_id

    Persistent user identifier across sessions

  • ⚠️
    User Profiles

    Name, email, custom properties stored

  • ⚠️
    Unlimited Event Properties

    Any data can be attached to events

  • 📍
    Geolocation Data

    City, region, country from IP

Privacy Implication: Mixpanel's identify() function links all user activity to a persistent ID. User profiles can contain PII like names and emails. This may require consent management depending on your jurisdiction.

Respectlytics

Respectlytics

Privacy-first by architecture

Only 5 Fields Stored:

  • ✅
    event_name, timestamp

    Core event data

  • ✅
    platform

    Technical context (ios, android, web)

  • ✅
    country

    Country-level geolocation only

  • ⚡
    session_id

    2-hour rotating, RAM-only in SDKs

Privacy by Design: No identify() method exists. No user profiles. No custom properties. Only 5 data fields are ever stored. This may reduce compliance complexity in many jurisdictions.

🛡️ How Respectlytics Enforces Privacy

analytics/privacy_guards.py 
# Strict allowlist - only these 5 data fields are stored (plus app_key for auth)
STORED_FIELDS = frozenset({
    'event_name',    # Required
    'timestamp',     # Optional timing
    'platform',      # ios, android, web
    'country',       # 2-letter ISO code
    'session_id',    # 2-hour rotating, RAM-only
})

# API rejects any request with extra fields
if unexpected_fields := request_fields - ALLOWED_FIELDS:
    raise PrivacyValidationError(
        code="DISALLOWED_FIELDS",
        reason=f"Custom fields not allowed: {unexpected_fields}"
    )

This strict allowlist makes it technically difficult to leak personal data through Respectlytics and is designed to prevent PII in analytics events. Any attempt to send custom properties is rejected with a clear error message.

User Tracking Comparison

Mixpanel's identify() vs Respectlytics session-based approach

📊 Mixpanel User Tracking

Persistent cross-session user identification

// Link all activity to a persistent user ID
mixpanel.identify('user_12345');

// Store personal data in user profiles
mixpanel.people.set({
    '$name': 'John Doe',
    '$email': '[email protected]',
    'plan': 'premium'
});

// All future events linked to this user
mixpanel.track('Purchase', {
    'amount': 99.99,
    'product': 'Pro Plan'
});
⚠️ User tracked across all sessions indefinitely
⚠️ Personal data stored in user profiles
⚠️ Requires GDPR deletion API for user requests

Respectlytics Respectlytics

Session-based, no persistent user tracking

// Configure once - no user identification
Respectlytics.configure(appKey: "your_key")

// Track events - session_id auto-generated
// Rotates every 2 hours, stored in RAM only
Respectlytics.track(eventName: "Purchase")

// No identify() method exists
// No user profiles
// No custom properties allowed
✅ Session ID rotates every 2 hours automatically
✅ No personal data can be stored
✅ No user deletion needed - no user data exists

When to Choose Each

Both platforms have their place. Here's our honest assessment.

📊 Choose Mixpanel If:

  • • You need individual user journey analysis
  • • User profiles with names/emails are required
  • • You need cohort syncing with marketing tools
  • • Custom event properties are essential
  • • You have resources for privacy compliance

Respectlytics Choose Respectlytics If:

  • • Privacy is a core value for your company
  • • You want to minimize data collection by design
  • • Aggregate insights are sufficient (no individual tracking)
  • • You want automated conversion intelligence
  • • You value transparent, explainable analytics

See also: Firebase vs Respectlytics • Amplitude vs Respectlytics

Ready to Go Privacy-First?

Join developers who choose transparent analytics over user surveillance.

Get Started with SDKs → View Pricing
SDK Documentation • Contact Sales • Privacy Policy