Privacy

Data Storage

Data is stored on secure U.S. servers. We retain data only as long as necessary to provide Linse.

Third-Party Services

We may use the following AI model providers depending on the request type and routing decisions:

• Anthropic (Claude): for code, reasoning, and EU-compliant requests
• OpenAI (GPT): for vision, math, and tool-use requests
• Google (Gemini): for vision, long-context documents, and Workspace integration
• Groq: for fast simple responses (the majority of routing)
• Perplexity: for web search and current information queries
• Inworld: for custom voice synthesis (text-to-speech) in voice mode
• Google Cloud Speech-to-Text: for voice transcription in voice mode

These providers operate under contractual agreements that prohibit training their models on data submitted via our API, and require deletion after processing.

For cloud infrastructure, we use Amazon Web Services (AWS) and Google Cloud Platform (GCP) for secure storage, compute, and bandwidth. All data is encrypted in transit (TLS 1.3) and at rest (AES-256).

Voice & Audio Processing

Linse offers a voice mode where you can speak to the holographic assistant. When you use voice mode, your audio is processed in real time by the following services:

What happens when you speak

1. 1.Your audio is transmitted via WebSocket using LiveKit's transport infrastructure.
2. 2.Audio is sent to Google Cloud Speech-to-Text for transcription into text.
3. 3.The transcribed text is processed by our AI model providers (per Third-Party Services above) to generate a response.
4. 4.The response text is converted back to speech via Inworld's custom voice synthesis.
5. 5.The synthesized audio is streamed back to you in real time.

What we do with your voice data

• Audio is processed in real time and is not stored as audio files in our systems.
• Transcribed text becomes part of your conversation history, which follows our standard data retention rules (see Memory & Conversation Storage below).
• Voice transmissions are encrypted in transit (TLS).
• Inworld and Google STT operate under contractual agreements prohibiting use of your audio for training their models.

Voice in sensitive contexts

For users in healthcare, legal, or other professional contexts handling confidential information, we recommend reviewing our HIPAA disclaimer in the Terms of Service before using voice with protected information. Voice mode is not HIPAA-compliant.

Opting out

You can use Linse entirely in text mode without ever activating voice. Voice features are only triggered by your explicit action.

Memory & Conversation Storage

Linse is designed as a "Living AI" with persistent memory across sessions. This requires storing and retrieving information about your conversations and preferences.

What we store

• Conversations: full message history of your interactions, organized by Space (workspace).
• Memory facts: when relevant, Linse extracts and stores semantic facts from your conversations (e.g., your name, preferences, ongoing projects) to provide continuity across sessions. These facts are stored in our Elasticsearch infrastructure and indexed for retrieval.
• Spaces metadata: titles, descriptions, "Notes for Linse" you provide, and configuration of your custom Spaces.

Where it lives

• Conversation messages: PostgreSQL on AWS infrastructure.
• Memory facts and semantic search index: Elasticsearch on AWS infrastructure.
• Configuration and account state: PostgreSQL.
• Short-term context cache: Redis (7-day TTL by default).

Your control

You can at any time:

• View all memory facts Linse has stored about you in Settings → Memory.
• Delete individual memory facts or clear all memory.
• Disable memory entirely (Linse will respond without persistent context across sessions).
• Export your full conversation history.
• Delete your account, which permanently removes all stored data within 30 days.

Retention

By default, memory and conversations are retained as long as your account is active. We may introduce tier-based retention windows in the future (e.g., shorter retention for free accounts); any such changes will be announced in advance and reflected in this policy.

For data export and deletion requests, contact privacy@scopeagi.com or use the in-app controls in Settings.

Google User Data

Linse integrates with Google services (Gmail, Google Calendar, Google Drive, Google Contacts) through OAuth to provide features you explicitly authorize. When you connect a Google account, we access only the data covered by the scopes you approve.

What Google User Data We Access

• Gmail (gmail.send): permission to send emails on your behalf. We do not read, store, or index your inbox.
• Google Calendar (calendar.readonly, calendar.events): to view and create events when you ask Linse to schedule or check availability.
• Google Drive (drive.file): limited to files you explicitly select via the Google Picker. We cannot access other files in your Drive.
• Google Contacts (contacts.readonly): to suggest recipients when you compose messages.
• Basic profile (openid, userinfo.email, userinfo.profile): to identify your account.

How We Use Google User Data

Google user data is used solely to provide the features you explicitly request within Linse. We do not use Google user data for advertising, profiling, or any purpose unrelated to the feature you invoked.

With Whom We Share Google User Data

We do not sell, rent, or trade Google user data. We share Google user data only with the following categories of service providers, and only to the minimum extent needed to operate the feature you requested:

• Cloud infrastructure providers (Amazon Web Services, Google Cloud) for secure storage and compute. Data is encrypted in transit (TLS 1.3) and at rest (AES-256).
• AI model providers (OpenAI, Anthropic, Google) only when processing a specific user request that requires it. These providers operate under contractual agreements that prohibit training their models on data submitted via our API, and require deletion after processing.
• Legal compliance: only if required by valid legal process.

We do not share Google user data with advertisers, data brokers, or any third party for marketing purposes.

AI and Machine Learning Model Training

Linse does not use Google Workspace APIs data to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models, including foundational models.

Google user data obtained through Workspace APIs (Gmail, Google Calendar, Google Drive, Google Contacts) is used only to execute user-facing features you explicitly invoke. It is not retained for model training, is not used to build aggregated datasets for AI/ML research, and is not shared with third parties for those purposes.

Any "Improve Linse with my data" opt-in setting in our product explicitly excludes data obtained through Google Workspace APIs.

Limited Use Compliance

Linse'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.

Retention and Revocation

Google user data is retained only as long as needed to deliver the feature you requested. You can revoke Linse's access at any time at https://myaccount.google.com/permissions, which stops all further access. You can also request deletion of stored Google user data by emailing privacy@scopeagi.com.

ChildrenNotice

Linse is not intended for children under 13.