Respectlytics Respect lytics
Menu
⚖️ Comparison Guide

The Privacy-First
Amplitude Alternative

Amplitude collects IDFA, IDFV, device IDs, and IP addresses for tracking. Respectlytics stores only 5 essential fields with no device identifiers.

Try Respectlytics → View Pricing

Quick Comparison

See the key differences at a glance

Feature
📈 Amplitude
Respectlytics Respectlytics
Device IDs (IDFA/IDFV)
⚠️ Collected Via IDFA plugin
✅ Never collected By design
IP Address Storage
⚠️ Stored in events ip_address field
✅ Discarded after geo Never stored in analytics
User Tracking
📝 user_id + device_id Cross-device tracking
🛡️ session_id only Rotates every 2 hours
User Properties
⚠️ Unlimited Stored on user profile
🛡️ Not supported No user profiles exist
Event Properties
⚠️ Unlimited PII leak risk
🛡️ Not allowed API rejects extra fields
Location Precision
📍 City + lat/long location_lat, location_lng
✅ Country only 2-letter ISO code
Conversion Intelligence
🔧 Manual funnels Define steps yourself
🤖 Automatic Auto-discovered

Privacy Architecture

The fundamental difference in how user data is handled

📈

Amplitude

Product analytics platform

What Amplitude Collects:

  • ⚠️
    device_id

    Persistent device identifier

  • ⚠️
    IDFA / IDFV

    Via IDFACollectionPlugin

  • ⚠️
    ip_address

    Stored in raw event data

  • 📍
    location_lat, location_lng

    Precise coordinates

Privacy Implication: Amplitude's raw event export schema includes ip_address, idfa, device_id, and precise location coordinates. These are personal data fields that may require consent management.

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 device identifiers, no IP storage, no precise location. Only 5 data fields are ever stored. This may reduce compliance complexity in many jurisdictions.

📋 Amplitude's Raw Event Data (from official docs)

Amplitude raw event export schema (partial) 
{
  "user_id": string,
  "device_id": string,
  "ip_address": string,         // ⚠️ Personal data
  "idfa": string,               // ⚠️ Advertising ID
  "location_lat": float,        // Precise latitude
  "location_lng": float,        // Precise longitude
  "city": string,
  "country": string,
  "device_manufacturer": string,
  "device_model": string,
  "os_name": string,
  "os_version": string,
  "event_properties": dict,     // Unlimited custom data
  "user_properties": dict       // Unlimited user data
}
Respectlytics event schema (complete) 
{
  "event_name": string,        // ✅ Required
  "timestamp": ISO 8601,       // ✅ When it happened
  "platform": "ios"|"android"|"web",
  "country": "US"|"DE"|...,  // ✅ Country only, no city
  "session_id": string        // ✅ Rotates every 2 hours
}
// That's it. No more fields accepted.

Privacy Controls Comparison

Amplitude requires opt-out configuration. Respectlytics is private by default.

📈 Amplitude Privacy Controls

Opt-out approach - tracking is on by default

1.

setOptOut(true)

Must call to disable tracking per user

2.

enableCoppaControl()

Disables IDFA, IP, location for children

3.

deferInitialization

Wait for consent before tracking

4.

IDFACollectionPlugin

Manual plugin to collect advertising IDs

Respectlytics Respectlytics

Privacy by design - nothing to configure

✓

No IDFA/IDFV collection

Not even an option in the SDK

✓

No IP address storage

Discarded after country lookup

✓

No user properties

API rejects any custom data

✓

Session-only identification

Rotates every 2 hours, RAM-only

When to Choose Each

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

📈 Choose Amplitude If:

  • • You need cross-device user tracking
  • • Detailed user properties are essential
  • • You need A/B testing and experiments
  • • Session replay is a requirement
  • • You have resources for privacy compliance

Respectlytics Choose Respectlytics If:

  • • Privacy is a core value for your company
  • • You want to avoid IDFA/IDFV collection entirely
  • • Aggregate insights are sufficient (no individual tracking)
  • • You want automated conversion intelligence
  • • You value data minimization by design

See also: Firebase vs Respectlytics • Mixpanel vs Respectlytics

Ready to Go Privacy-First?

Join developers who choose transparent analytics over device surveillance.

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