Respectlytics Respect lytics
Menu
🔒 Privacy-First Feature

Understand Engagement
Without Persistent User Tracking

Session-based analytics gives you actionable engagement metrics while maintaining strong user privacy protections. No persistent identifiers, no cross-session tracking, designed with privacy as the priority.

Session Metrics Dashboard

Comprehensive engagement analytics without compromising user privacy

📊

Events per Session

Distribution of engagement depth across sessions

1-5 events 34%
6-10 events 28%
11-20 events 24%
21+ events 14%
🕐

Hourly Patterns

When your users are most active (with timezone support)

Peak Hour 2 PM
Sessions 1,234
Conversion 8.2%
⏱️

Session Duration

How long users engage with your app

Average 4m 12s
Median 2m 45s
Trend ↑ 12%
🎯

Session Conversion

Percentage of sessions that convert

Overall Rate 6.8%
Deep Sessions 18.4%
Shallow 2.1%

The Privacy Advantage

How session-based analytics protects user privacy while delivering actionable insights

👤

User-Based Analytics

With persistent user identifiers

  • ⚠️
    Persistent User IDs

    Tracks same user across sessions, days, devices

  • ⚠️
    Device Storage Required

    Writes identifiers to disk (UserDefaults, Keychain)

  • ⚠️
    Personal Data Stored

    Writes identifiers to device, retains personal data

  • ⚠️
    Retention Cohorts

    Can track D1, D7, D30 retention (but privacy cost)

Trade-off: Rich user-level insights at the cost of storing personal data and increased privacy compliance complexity.

🔒

Session-Based Analytics

Respectlytics approach

  • 2-Hour Rotating Session IDs

    Automatically rotates every 2 hours or on app restart

  • RAM-Only Storage

    Session IDs never written to device storage

  • No Personal Data Retained

    Privacy by design—may reduce compliance complexity in many jurisdictions

  • Session Quality Metrics

    Depth, duration, patterns—all privacy-safe

Design Choice: Intentionally cannot track users across sessions. This is a feature, not a limitation—it's privacy by design.

How Session IDs Work

Our SDK generates session identifiers that protect privacy by design

1

App Launch

SDK generates a new random session ID in memory

2

RAM Only

Never written to disk—lost when app closes

3

2-Hour Rotation

Session ID automatically rotates after 2 hours of use

4

Server-Side Hash

Session ID is hashed server-side with daily salt

SDK Session Management
// Session ID lifecycle in Respectlytics SDK

class SessionManager {
    // Generated fresh on each app launch
    private var sessionId: String = UUID().uuidString
    private var sessionStart: Date = Date()

    func getSessionId() -> String {
        // Rotate after 2 hours
        if Date().timeIntervalSince(sessionStart) > 7200 {
            sessionId = UUID().uuidString
            sessionStart = Date()
        }
        return sessionId
    }

    // Note: sessionId is NEVER persisted to UserDefaults,
    // Keychain, or any device storage. RAM only.
}

Actionable Use Cases

What you can learn from session-based analytics

🔔

Peak Engagement Hours

Identify when sessions are most active and have the highest conversion rates. Use this to time push notifications, feature releases, and marketing campaigns.

Example insight: "Sessions starting at 2 PM have 3x higher conversion than 8 AM sessions"

📈

Session Depth Patterns

Understand how deep users engage in a single session. Sessions with 11+ events convert at 18.4% vs 2.1% for shallow sessions—focus on increasing depth.

Example insight: "Sessions that reach the pricing page have 5x conversion lift"

📊

Platform Comparison

Compare session behavior across iOS, Android, and Web. Identify which platform has longer sessions, deeper engagement, and higher conversion.

Example insight: "iOS sessions average 5.2 minutes vs Android at 3.8 minutes"

Frequently Asked Questions

What is session-based analytics?

Session-based analytics measures user engagement within individual app sessions rather than tracking users across sessions. Each session is identified by a temporary ID that rotates every 2 hours or on app restart, making it technically impossible within Respectlytics to link sessions to the same user over time. This provides engagement metrics while maintaining strong user privacy protections.

How is this different from other analytics solutions?

Other analytics solutions use persistent user identifiers (like IDFA, IDFV, or custom user IDs) that track the same user across sessions, days, and even devices. This enables features like retention cohorts and user journeys, but comes with significant privacy implications. Respectlytics intentionally uses non-persistent session IDs that rotate every 2 hours and are stored only in RAM—providing engagement metrics without retaining personal data.

How does Respectlytics protect user privacy?

Respectlytics is designed with privacy as the foundation. We use 2-hour rotating session IDs stored only in RAM (never to device storage). IP addresses are processed transiently for approximate geolocation and immediately discarded—no personal data is persisted server-side. Cross-session tracking is technically impossible by design. This privacy-by-design approach may reduce compliance complexity, but regulations vary by jurisdiction—we recommend consulting with your legal team to determine your specific requirements.

Can I do retention analysis without user tracking?

Traditional day-over-day retention (D1, D7, D30) requires persistent user tracking, which session-based analytics intentionally avoids. However, you can analyze session quality metrics, engagement patterns, and conversion rates which provide actionable insights without compromising privacy. Focus on improving session depth and conversion—these are often more actionable than retention numbers anyway.

What engagement metrics can I track?

You can track: events per session (engagement depth), session duration, hourly engagement patterns, session conversion rates, and compare these metrics across platforms, countries, and app versions. You can also analyze conversion paths, drop-off points, and which events correlate with conversion—all without tracking individual users.

Ready for Privacy-First Analytics?

Get session-based engagement metrics without relying on persistent user tracking. Privacy by design, session-based analytics, no persistent user tracking.