Official Respectlytics SDK for Flutter. Privacy-first analytics with automatic session management, zero device storage, and no device identifier collection.

• RAM-Only Event Queue — Events are no longer persisted to SharedPreferences. The entire SDK now writes zero bytes to the device for analytics
• Zero Device Storage — Session IDs AND event queue are held exclusively in RAM
• Removed shared_preferences dependency — One fewer dependency to audit

Add to your pubspec.yaml:

dependencies:
  respectlytics_flutter: ^3.0.0

Or run:

flutter pub add respectlytics_flutter

import 'package:flutter/material.dart';
import 'package:respectlytics_flutter/respectlytics_flutter.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  // 1. Configure (call once at app launch)
  await Respectlytics.configure(apiKey: 'your-api-key');

  runApp(MyApp());
}

// 2. Track events anywhere in your app
await Respectlytics.track('purchase');

Initialize the SDK. Call once in your main() before runApp().

• apiKey (required) — Your Respectlytics API key
• baseUrl (optional) — Server URL. Defaults to https://respectlytics.com/api/v1

Track an event. Custom properties are not supported (privacy by design).

Force send queued events. Rarely needed - SDK auto-flushes every 30 seconds.

If you're running the Respectlytics Community Edition, point the SDK at your own server:

await Respectlytics.configure(
  apiKey: 'your-api-key',
  baseUrl: 'https://your-server.com/api/v1',
);

The baseUrl must include the /api/v1 path. If omitted, the SDK defaults to the Respectlytics cloud at https://respectlytics.com/api/v1.

Session IDs are managed entirely by the SDK - no configuration needed.

Key points:

• 🔄 New session on every app launch
• ⏱️ Sessions rotate after 2 hours of continuous use
• 🧠 Session IDs stored in RAM only (never persisted to disk)
• 🚫 No cross-session tracking - each session is independent

Respectlytics helps developers avoid collecting personal data in the first place. Our motto is Return of Avoidance (ROA) — the best way to protect sensitive data is to never collect it.

| Field | Purpose | |-------|---------|| | event_name | The action being tracked | | timestamp | When it happened | | session_id | Groups events in a session (RAM-only, 2-hour rotation, hashed server-side) | | platform | iOS, Android, macOS, Linux, Windows | | country | Derived server-side from IP address (IP immediately discarded) |

• RAM-only sessions: Session IDs exist only in device memory, never written to disk
• RAM-only event queue: Events are held in memory until flushed to the server — zero device storage
• 2-hour rotation: Sessions automatically expire and regenerate
• New session on restart: Each app launch starts a fresh session
• Server-side hashing: Session IDs are hashed with daily-rotating salt before storage
• Strict allowlist: API rejects any fields not on the 5-field allowlist
• Open source SDKs: Full transparency into what data is collected

This architecture is designed to be transparent (you know exactly what's collected), defensible (minimal data surface), and clear (explicit reasoning for each field).

Consult your legal team to determine your specific compliance requirements.

Events are queued in memory and sent automatically:

• Every 30 seconds
• When 10 events are queued
• When app goes to background
• When flush() is called
• When the device comes back online

Unsent events are lost on force-quit — this is a deliberate privacy trade-off. The SDK writes zero bytes to the device for analytics purposes. The ~1-3% event loss from force-quits has no meaningful impact on session-based aggregate analytics.

• Flutter 3.10+
• Dart 3.0+

Breaking Change: Event queue no longer persists to SharedPreferences.

Update your dependency version:

# Before
respectlytics_flutter: ^2.2.0

# After
respectlytics_flutter: ^3.0.0

No code changes required. The public API (configure, track, flush) is unchanged. Events previously stored in SharedPreferences under the old key will be ignored (they remain inert but are never read).

What changed:

• Events are now held in an in-memory list (RAM-only)
• Unsent events are lost on force-quit — this is by design
• shared_preferences is no longer a dependency

Breaking Change: The screen parameter has been removed from track().

- await Respectlytics.track('purchase', screen: 'CheckoutScreen');
+ await Respectlytics.track('purchase');

If you need screen context, include it in your event name (e.g., checkout_screen_purchase).

⚠️ Breaking Changes:

• REMOVED: identify() method - no longer needed
• REMOVED: reset() method - no longer needed
• REMOVED: SharedPreferences storage for user IDs

What to do:

1. Remove any calls to Respectlytics.identify()
2. Remove any calls to Respectlytics.reset()
3. That's it! Session management is now automatic.

• 📖 SDK Documentation
• 🐛 Issue Tracker
• 💬 Support

MIT License. See LICENSE file.