Google API Services User Data Policy
LifeOS's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We use Google Calendar API solely to read calendar event data for the purpose of automating "Recovery Buffers" - rest periods scheduled after high-drain meetings. This data is processed in real-time and is not stored beyond the current session's processing needs.
Biometric Sensor Data Processing
LifeOS processes biometric sensor data, including keystroke patterns and mouse movements, solely to generate a local-first 'neuroScore' that helps optimize your productivity and cognitive load management.
This processing occurs entirely on your device and is used to:
- Calculate your current cognitive energy level
- Recommend optimal work modes (Focus, Calm, or Recovery)
- Schedule tasks based on your peak performance windows
- Prevent cognitive burnout through proactive rest suggestions
Local-First Security: The Vault
Raw sensor logs are stored ONLY in your local 'Vault' (WatermelonDB) and are NEVER synced to LifeOS servers.
Your privacy is our top priority. All raw keystroke and mouse movement data remains on your device. Only aggregated, anonymized features (such as average typing speed or movement patterns) are used for local machine learning inference.
The Vault architecture ensures that:
- Raw biometric data never leaves your device
- Only refined scores (neuroScore) are synced to our servers for cross-device continuity
- You maintain complete control over your sensitive data
Google Calendar Integration (Neural Slotting)
For Architect Tier subscribers, LifeOS reads your Google Calendar event data to automatically create "Recovery Buffers" after meetings that exceed 60 minutes in duration.
Data Usage:
- We read calendar event start times, end times, and durations
- This data is processed in real-time to determine if a recovery period is needed
- Calendar data is not stored beyond the current session's processing needs
- No calendar event details (titles, descriptions, attendees) are stored or transmitted
This feature is only available to Architect Tier (PRO) subscribers and requires explicit Google OAuth consent with read-only calendar access.
What Data We Collect
We collect the following types of data:
- Account Information: Email address, display name (via Clerk authentication)
- Productivity Metrics: Task completion, focus session duration, XP and level progression
- Aggregated Neuro Data: Refined neuroScore values (0-100 scale), not raw sensor data
- Usage Patterns: Feature usage statistics to improve the product
Data Storage and Security
All data is stored securely using industry-standard encryption. Your account information is managed by Clerk, a trusted authentication provider. Productivity data is stored in our secure database (Neon PostgreSQL).
Raw biometric sensor data remains exclusively on your device in the local Vault and is never transmitted to our servers.
Your Rights
You have the right to:
- Access your personal data
- Request deletion of your account and associated data
- Revoke Google Calendar access at any time
- Export your productivity data
- Opt out of data collection (note: this may limit app functionality)
Contact Us
If you have questions about this Privacy Policy, please contact us at privacy@lifeos.vc