Privacy Policy

1. Information We Collect

• Account Information: When you register, we collect personal information such as your name, email address, and authentication credentials.
• User-Generated Data: We process the text, files, configurations, and workspace data you input into LifeNode OS to provide the orchestration and automation services.
• Log and Usage Data: We automatically collect standard information sent by your browser or device, including your IP address, browser type, pages visited, and timestamps.
• Google Account Data (optional integrations): If you connect Google services through LifeNode OS, we access only the Google user data described in Section 6, and only after you grant consent on Google's OAuth screen.

2. How We Use Your Information

We use the collected data to:

• Provide, operate, and maintain the features of LifeNode OS.
• Improve, personalize, and expand our application's functionality.
• Process transactions, manage user accounts, and handle password recovery.
• Communicate with you regarding updates, security alerts, and support.
• Operate optional Google integrations (Calendar, Gmail, and Drive) as described in Section 6.

3. Data Sharing and Third-Party Services

We do not sell your personal data. We only share information with trusted third-party services necessary to run our platform, including:

• Hosting & Infrastructure: Cloud providers (e.g., Vercel, Google Cloud) and database management systems (e.g., Supabase / PostgreSQL).
• Authentication & Email Providers: Services used to manage secure logins and dispatch system emails (e.g., transactional email APIs).
• Google APIs: When you connect Google Calendar, Gmail, or Google Drive, LifeNode OS exchanges OAuth tokens with Google to provide those features. We do not sell Google user data to data brokers or advertisers.

4. Data Security

We implement industry-standard technical and organizational security measures to protect your data from unauthorized access, alteration, or disclosure. However, no method of transmission over the internet is 100% secure, and we cannot guarantee absolute security.

OAuth access and refresh tokens for Google integrations are stored server-side (not in client-side localStorage), transmitted over HTTPS, and scoped to your LifeNode OS account. API routes that use those tokens authenticate your session before reading or writing data.

5. Your Rights

Depending on your location, you may have the right to access, update, correct, or delete your personal data. You can manage most account settings directly within the app interface or contact us for assistance.

You may disconnect Google integrations at any time from Connected Apps / Inbox / Calendar surfaces in LifeNode OS, and you may revoke LifeNode OS access from your Google Account permissions.

6. Google API User Data

LifeNode OS uses Google OAuth and Google APIs only when you explicitly connect an integration. Sign-in with Google (identity only) is separate from Calendar, Gmail, and Drive connectors.

6.1 Data access (what we access)

Subject to the scopes you approve on Google's consent screen, LifeNode OS may access:

• Google Calendar: Calendar event data (such as titles, times, descriptions, and attendees as provided by the API) needed to sync and display your schedule in LifeNode OS, and to create events you initiate in the app.
• Gmail: Message metadata and content (and related labels/settings as needed) to power Inbox sync, unread/urgent monitoring, archiving/label updates you initiate, and compose/reply you initiate.
• Google Drive: File metadata and content available under the read-only Drive scopes you approve, when Drive is connected, so you can browse or link existing files to workspace items. We do not request full Drive or Google Docs edit/delete scopes for this product.
• Account email: Your Google account email address associated with a connection, when requested via userinfo scopes, so we can identify which Google account is linked.

We may process both raw Google user data retrieved from these APIs and aggregated signals derived from it (for example, unread counts or schedule conflict counts) solely to operate those user-facing features.

6.2 Data use (how we use it)

Google user data is used only to:

• Provide and improve user-facing LifeNode OS features you enable (unified Calendar, Inbox productivity, optional Drive linking).
• Sync display state in your account (for example, inbox items and calendar events stored in your LifeNode OS workspace).
• Perform write-backs you explicitly trigger (for example, creating a Calendar event, archiving a Gmail message, or sending a reply).

We do not use Google user data for targeted advertising, data brokerage, credit determination, or other purposes prohibited by the Google API Services User Data Policy.

6.3 Data transfer & sharing

We do not sell Google user data. We do not transfer Google user data to third parties for advertising or data-broker purposes. Google user data may be processed by infrastructure providers that host LifeNode OS (for example, application hosting and our database provider) solely to store and serve your connected workspace. Access is limited to operating the product for your account.

6.4 Data protection

Tokens and synced payloads are stored on secured server-side systems, protected in transit with HTTPS, and associated with your authenticated LifeNode OS user ID. Client applications do not receive service-role database credentials. Additional operational controls are described on our Security documentation.

6.5 Retention & deletion

• While connected: Synced Google-derived workspace data (such as inbox items or calendar events synced into LifeNode OS) is retained in your account so the product can function.
• On disconnect: You may disconnect an integration in-app. We stop further Google API access with that connection and remove or invalidate stored OAuth tokens for that provider. You should also revoke access in Google Account permissions if desired.
• On account deletion: When your LifeNode OS account is deleted, we delete or irreversibly de-identify associated account data and integration credentials in line with our deletion practices and backup cycles.

6.6 Limited Use & AI/ML

The use of raw or derived user data received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• Google API user data is used only to provide or improve user-facing features of LifeNode OS for that user (and limited cases allowed by Google's policy).
• We do not use Google Workspace API user data to develop, improve, or train generalized AI/ML models.
• We do not transfer Google Workspace API user data to third-party AI services for those services to train their models. Optional in-app assistants (such as Linos) process prompts you explicitly send in chat; we do not automatically pipe your full Gmail mailbox or Drive library into model-training pipelines.

7. Contact

Questions about this Privacy Policy or Google API data handling may be sent through the support channels listed on lifenodeos.com.