1. Data Collection Philosophy

Friction + Flow is designed to measure operational velocity and distractions without recording personal identification details. Core architectural parameters guarantee complete anonymity:

• Zero Accounts Required: The mobile application does not require user profiles, password creation, email address validation, or third-party federated logins (such as Google or Apple).
• Zero Remote Pipelines: There are no external databases, server API endpoints, cloud backup vaults, or central telemetry networks. All data inputs remain confined to your device.
• Zero Tracker SDKs: We do not load commercial advertising SDKs, behavioral analytics scripts, or cookies. Your workspace behavior is private.

2. SQLite Local Storage Quarantine

All logged categories, labels, custom coordinates, and timestamps are written strictly into an on-device local database:

The application initializes a private SQLite transaction database named `frictionless.db` via the sandboxed expo-sqlite framework. This file is housed exclusively inside the application's physical sandboxed document directory on your hardware. Other mobile applications cannot read this database, and it is never synchronized or backed up to external cloud repositories by default.

3. Hardware & Sensor Governance

To provide precise spatial analytics without battery depletion or privacy leaks, Friction + Flow utilizes device sensors under strict sandboxed rules:

• Geolocation (expo-location): Coordinates are queried only at the exact millisecond of a user logging action. To optimize speed, the app first checks foreground permission status (getForegroundPermissionsAsync) and queries cached device locations (getLastKnownPositionAsync). If empty, it triggers the sensor via balanced accuracy parameters (Location.Accuracy.Balanced).
  Strict Isolation: Latitude and longitude coordinates are appended solely to the offline SQLite `logs` table. They are processed entirely on-device to compile your spatial blueprint heatmap. No coordinates are ever transmitted, sold, or shared.
• Native Haptics (expo-haptics): Distinct tactile vibration patterns confirm successful database entries in Phase 1:
  • 🔴 Friction: Double-pulse native Error vibration signature.
  • 🟡 Noise: Single-tick native Light impact vibration.
  • 🔵 Flow: Triple-pulse native Success validation vibration.

4. User Agency & Data Portability

You hold total administrative control over the lifecycle of your behavioral dataset:

• Instant Database Purge: Activating the in-app "Reset System" instruction instantly executes clear queries against all database tables. Deleting the application from your mobile device immediately wipes the sandboxed frictionless.db file, permanently destroying all records.
• Dual-Stream Export Menu: You can export raw metrics on your own terms. Option A compiles an RFC 4180-compliant CSV spreadsheet stream (systemores_flow_logs.csv). Option B generates a high-quality PNG report graphic utilizing react-native-view-shot, watermarked for professional networks:
  GENERATED VIA FRICTION + FLOW BY SYSTEMORES

5. App Store & Google Play Compliance

This policy satisfies the strict data privacy disclosure mandates outlined in Apple's App Store Review Guidelines (specifically Section 5.1 regarding data privacy) and Google Play's Developer Content Policies.

For auditing parameters: Friction + Flow has no background tracking permissions, does not monitor location when the application is closed, collects zero system device identifiers, and will function gracefully as a offline time-tracker even if system-level location permissions are entirely denied.

6. Legal & Support Portal

For inquiries regarding our sandboxed architecture, compliance certifications, or the SYSTEMORES behavioral diagnostics engine, contact our engineering desk: