Privacy Policy

Overview

The Third Eye is a personal AI assistant. Each account's data belongs to that account holder and is used only to provide the service to them. We do not sell personal data, and we do not share it with third parties for advertising or any other purpose unrelated to running the product.

Data We Collect

• The name, email address and profile photo from the Google account you use to sign in
• Messages and queries you send to the assistant, and its replies
• Documents and files you upload to the knowledge base
• Tasks, notes, goals, reminders, and expense records you create
• Voice recordings you initiate, which are transcribed to text
• Google Workspace data you explicitly connect (see below)

Google User Data

Signing in with Google requests only your name, email address and profile photo (openid, email and profile). That identifies your workspace. Gmail and Calendar are not part of sign-in. They are granted only if you complete the “Connect Google” step in Settings, and can be revoked at any time from that screen or from your Google Account permissions page. We request these scopes and use them only as described:

• gmail.readonly — to read messages you ask the assistant to summarise, search, or extract tasks from
• gmail.send — to send an email you asked the assistant to write, only after you review it and press Confirm, and to email you the reminders and daily briefing you switched on. Sent mail appears in your Gmail Sent folder
• calendar.events.owned.readonly — to list events on your own primary calendar when you ask about your schedule. We never create, change or delete events

Message and event content is fetched when a request or ingest pass needs it and is processed in memory. We do not store raw email bodies, attachments or calendar event payloads. We persist only: extracted task titles and due dates you can edit or delete; Gmail message IDs already processed (so we do not re-scan them); and an encrypted Google refresh token. Google user data is not used to train any machine-learning model, is not sold, and is not transferred to anyone except the AI providers listed below, and only to the extent needed to answer your request.

Limited Use of Google User Data

The Third Eye's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve, or train generalised AI or machine-learning models. We do not allow humans to read your Google user data except with your explicit consent for a specific message, where it is necessary for security purposes such as investigating abuse, or where required by law.

How We Protect Your Data

Sensitive data — Google OAuth tokens, message and calendar content, uploaded documents, and the contents of your conversations — is protected by the following controls:

• Encryption in transit. All traffic to the application and to every third-party API is served over TLS (HTTPS). The site is served with HTTP Strict Transport Security, so browsers refuse to connect over plaintext.
• Encryption at rest. Data is stored in a managed PostgreSQL database that encrypts data at rest.
• Additional encryption of Google credentials. Google refresh tokens are encrypted with AES-256-GCM under a key held only in the server environment, before being written to the database. A copy of the database alone does not yield usable access to any Google account.
• Access control. Every table carries the owning account and has row-level security enabled, so the public API key shipped to browsers cannot read another account's rows. Privileged database credentials exist only in server-side code and are never sent to the browser.
• Server-enforced identity. The account a request acts for is taken from the verified session or a scoped API credential — never from the request body — so a caller cannot read or write another account's data by naming it.
• Credential hygiene. API credentials issued for automation are stored only as a SHA-256 hash, are limited to specific capabilities, and can be revoked individually.
• Accountability controls. Actions the assistant takes on your behalf are recorded in an append-only audit log visible to you, and a stop control halts all assistant activity on your account immediately.

No system is perfectly secure, and we do not claim otherwise. If we become aware of a breach affecting your data, we will notify you at the email address on your account.

Third-Party Services

• Google — your name and email to sign in. Gmail and Calendar only if you connect them in Settings
• AI model providers (Anthropic, OpenAI, Google, Groq, and similar) — to generate responses and transcribe audio. Only the content needed to answer a given request is sent.
• Supabase — database
• Vercel — application hosting
• Stripe — subscription payments. Card details are handled by Stripe; we never receive or store them.

Retention and Deletion

Data is retained while your account exists. You can delete individual items at any time from within the app. Deleting your account from Settings removes your records across every table that holds them, including your stored Google tokens, and cannot be undone. You can withdraw Gmail and Calendar access separately at any time from your Google Account permissions page, which immediately stops the stored token from granting any access.

Children

The Third Eye is not directed to children under 13, and we do not knowingly collect their personal data.

Changes

If this policy changes materially, the date at the top of this page will be updated. Continued use after a change constitutes acceptance of the revised policy.

Contact

For any privacy-related question, or to request deletion of your data, contact anchit.tandon@gmail.com.