# Data Handling

Last updated: January 21, 2026

**We cannot see or access your data.** Your context logs, screenshots, and chat history are stored locally on your device only. When you use cloud AI features, your data is processed in real-time with **zero retention**.

This document explains, in practical terms, what data Waylight touches, when network requests occur, and which services are involved. It is meant to complement the Privacy Policy and make it easy to evaluate Waylight for sensitive work.

## 1. Overview

- **Local-first:** Chat history and context logs are stored on your device and are never sent to our servers unless you explicitly use cloud features.
- **Clear modes:** You can use **local-only AI** and/or **Offline Mode** to keep processing on-device and prevent most network connections (update checks continue to ensure you receive important updates).
- **Minimal telemetry:** Telemetry is optional, can be fully disabled, and never includes your content.
- **No surprise connections:** There is no hidden crash reporting, license/activation checks, or background data uploads.

## 2. When network requests happen

Waylight initiates network requests only in these situations:

- **Authentication and profiles**  
  - Endpoints such as `/auth/signup`, `/auth/signin`, `/auth/profile`  
  - Data: email, password (securely handled), basic profile fields, subscription status.  
  - Purpose: account creation, login, syncing profile information.
- **Cloud AI features**  
  - Endpoints such as `/llm/stream`, `/llm/evaluate-productivity`, `/todos/generate`  
  - Data (when you choose cloud mode):  
    - Current chat messages and prompts  
    - Summaries of your context logs (window titles, app names, activity summaries)  
    - Todo generation inputs and productivity evaluation summaries  
  - Purpose: send this content to AWS Bedrock to generate responses and analyses.
- **Subscription and payments**  
  - Endpoints such as `/stripe/products`, `/stripe/get-payment-link`, `/stripe/subscription-status`  
  - Browser redirect to Stripe Checkout.  
  - Data: email, user ID in metadata, billing details and payment method (handled by Stripe).
- **Telemetry/analytics** (optional)  
  - Connection to PostHog (e.g., `us.i.posthog.com`).  
  - Data: app version, OS info, CPU/memory/device model, feature usage events, and user ID when authenticated.  
  - No chat content, context logs.
- **Updates** (optional)  
  - Periodic version checks via Velopack against an S3-based update server.  
  - Data: current app version, platform/OS, anonymous update check requests.
- **Feedback submission**  
  - Endpoints such as `/feedback/general`.  
  - Data: your written feedback, optional attachments, survey responses.

All of these respect the global **Offline Mode** setting, which prevents non-essential network requests. Note that update checks continue even in Offline Mode to ensure you receive important updates.

## 3. What stays on your device

The following data is created and stored locally within your OS-specific application data directory and is not uploaded unless you explicitly choose cloud features:

- **Chat history**  
  - Stored as JSON files per chat.  
  - Contains user messages, assistant responses, and metadata (titles, timestamps, model used).
- **Context logs**  
  - Stored as compressed JSON (e.g., Brotli).  
  - Contains window titles, app names, timestamps, and optional screenshot data if enabled.  
  - Used to build summaries for local or cloud AI features.
- **Settings and preferences**  
  - Stored via encrypted Electron store.  
  - Includes telemetry and offline mode toggles, blocked apps/windows, onboarding status, and todo/feature flags.
- **Authentication tokens**  
  - Supabase session and refresh tokens stored encrypted locally.
- **Local AI models**  
  - Model files already bundled with the app.  
  - All inference happens on-device, without calling external APIs.

To remove this data, you can:

- Use any in-app data deletion features (if available), and/or  
- Manually delete the Waylight application data directory for your OS.

## 4. Cloud AI vs local AI

Waylight supports two main AI paths:

- **Local AI** (default privacy-maximizing option)  
  - Uses local models already bundled with the app.  
  - All prompts, context logs, and responses remain on your device.  
  - No network calls to AWS Bedrock or other AI providers.
- **Cloud AI** (optional)  
  - Uses models via AWS Bedrock in `us-east-2`.  
  - When you choose cloud mode, the following are sent to our backend and then to AWS Bedrock:  
    - Current chat messages and system prompts  
    - Selected context summaries (window titles, app names, activity summaries)  
    - Todo generation and productivity evaluation summaries  
  - AWS processes the request and returns a response; we log usage metadata (tokens, cost, model, timestamp) but **none** of the content.

If you do not want any of your data to leave your device, use local AI only and/or enable Offline Mode.

## 5. Telemetry and analytics

Telemetry exists to understand how Waylight is used, not what you write or view.

- **What telemetry collects** (when enabled)  
  - App version, OS/platform, CPU and memory info  
  - User ID when signed in  
  - Feature usage events (e.g., "opened settings", "started session")
- **What telemetry does not collect**  
  - Chat messages or prompts  
  - Context logs or screenshots  
  - Keystrokes or fine-grained user behavior such as individual window content
- **Control**  
  - You can disable telemetry in the app settings at any time.  
  - Enabling Offline Mode also prevents telemetry from sending.

Telemetry is implemented with PostHog and configured with session recording disabled and identified-only profiles.

## 6. Updates and licensing

- **No license/activation checks**  
  - Waylight does not perform hidden license or DRM checks on launch.  
  - The app can be used fully offline without recurring activation network calls.
- **Update checks**  
  - The app periodically checks the update server to see if a newer version exists.  
  - Update checks continue even when Offline Mode is enabled to ensure you receive important updates.  
  - Only version and platform data are transmitted; no identifying information is attached.

## 7. Payment processing

Payments for paid plans are handled by Stripe:

- Waylight never receives or stores card numbers or CVV codes.
- Stripe collects billing details and payment method information on its hosted checkout pages.
- Waylight stores only the Stripe customer ID, subscription ID, subscription status, and relevant billing period dates.

You can use Waylight on the free plan without providing payment information.

## 8. GDPR considerations and data subject rights

For organizations subject to GDPR:

- **Controller/processor roles**  
  - Waylight acts as a controller for user account and subscription data stored in Supabase.  
  - For content you process through the App (e.g., context logs), your organization is typically the controller; Waylight provides tools that can operate fully locally or, when you choose cloud features, as a processor via AWS Bedrock.
- **Support for data subject rights**  
  - We can help you:  
    - Export account and profile data stored in our backend  
    - Delete account-related data (profiles, subscriptions, cloud usage logs, feedback) upon verified request  
  - Local data on your device (chats, context) remains under your direct control and can be deleted by removing the corresponding directories or using in-app features.

If you need a signed Data Processing Agreement (DPA) or more detailed architecture diagrams, contact us at hello@waylight.ai.

## 9. How to get clarification

If you are evaluating Waylight for a GDPR-sensitive deployment or need clarification on any data flows, please reach out:

- **Email:** hello@waylight.ai

We can provide additional technical details (for example, environment configuration, data residency options of our vendors, or sample DPIA inputs) without exposing proprietary implementation details.