Privacy Policy

a) Account and authentication

Saving highlights requires a Verbatim account. You can sign in using Google OAuth or with a one-time email code. When you sign in we collect your email address (which is managed by Supabase Auth, our authentication provider) and, if signing in with Google, your display name and profile image URL. Signed-in accounts also receive an internal user ID which we use to scope your data. Reading this website and using the Debate feature do not require sign-in; only saving highlights does.

b) Highlight data

When you save a highlight, we collect: the selected text, the source platform (ChatGPT, Claude, Gemini, Grok, or Perplexity), the conversation URL, a highlight color, an optional note, the page title, and a timestamp. Highlights are associated with your account's user ID, which the server derives from your authenticated session — the extension cannot submit highlights on behalf of another account.

c) Device identifier

We generate a random, anonymous device identifier (UUID) on first install. It is stored locally on your device and included with saved highlights for cross-device organization. Once you are signed in, the device identifier is a secondary attribute — your user ID is the primary owner of your data.

d) API keys (optional)

If you choose to enter your own API keys for Anthropic, OpenAI, Google Gemini, or xAI in the extension settings, these keys are stored locally on your device using Chrome's sync storage. API keys are sent only to their respective provider's API endpoint and are never sent to our servers.

e) Public activity feed

Anonymized, non-identifying usage activity is displayed publicly on our homepage to show platform usage. This includes only the type of action (highlight or debate), the platform name, aggregate outcome counts, and a bucketed timestamp. No user data, content, highlight text, or identifiers are included.

e) Debate and classification data

When you use the Debate feature, the text of the AI response you selected is sent to an AI provider (Anthropic, OpenAI, Google, or xAI) to generate an alternative perspective. When you save a highlight, the text may be sent to Anthropic's API for automatic life-area classification (e.g., Work, Health, Learning).

f) Payment information

If you purchase debate credits, payment is processed entirely by Stripe. We receive only a transaction confirmation and credit amount. We do not collect, see, or store credit card numbers or billing details.

g) Feedback submissions

When users submit feedback through the extension, the text of that feedback is stored in our database. Feedback may include any information the user chooses to write. We do not intentionally collect names, emails, or other identifiers alongside feedback submissions. Users should avoid including personal information in feedback text. Feedback is stored securely and is only accessible to the Verbatim team.

What we do NOT collect

a) Displaying your highlights

Saved highlights are retrieved from our database and displayed in the extension sidebar and dashboard. Highlights are filtered by your account's user ID so that you only see your own data.

b) Generating daily digest emails

If you have provided an email address and enabled the digest feature, we send a daily email featuring one of your saved highlights along with a brief AI-generated observation. The highlight text is sent to Anthropic's Claude API to generate this observation. Anthropic does not store your data beyond the API call per their data retention policy.

c) Debate and verification

When you use the Debate feature, the selected AI response text is sent to one of the supported AI providers (Anthropic, OpenAI, Google, or xAI) to generate an alternative perspective. The specific provider depends on which model you select in the extension.

d) Highlight classification

When a highlight is saved, it may be sent to Anthropic's Claude API for automatic classification into a life area (Work, Money, Health, Relationships, or Learning). This classification is stored with the highlight for organizational purposes.

e) Mobile highlight capture (optional)

If you email a screenshot of an AI conversation to our inbound email address, the image is processed using Anthropic's Claude Vision API to extract the text and detect the AI platform. The extracted text is saved as a highlight associated with your email address. The original image is not stored after processing.

a) Local storage (on your device)

The following data is stored locally on your device using Chrome's storage APIs and never leaves your device unless described above:

b) Remote storage (our servers)

The following data is stored in our database (hosted on Supabase, which uses AWS infrastructure in the United States):

c) Retention

Highlights are stored indefinitely until you delete them. You can delete individual highlights from the extension sidebar at any time. To delete all your data and your account, email us at verbatim.coach@gmail.com and we will remove everything within 7 days. Email addresses can be removed from the digest at any time using the unsubscribe link in any digest email.

d) Security

Data in transit is encrypted using HTTPS/TLS. Data at rest in our database is encrypted by Supabase. API keys stored in Chrome sync storage are encrypted by Chrome. Access to our database requires authenticated credentials.

a) Supabase (database hosting and authentication)

Supabase hosts our database and manages authentication. It receives: your account record (user ID, email address, and if signed in with Google: display name and profile image URL), saved highlight text, platform, URL, device ID, and classification data. Supabase acts as a data processor on our behalf. Supabase privacy policy: supabase.com/privacy

b) Anthropic (AI processing)

Anthropic receives: highlight text (for classification and digest observations), debate text (for generating alternative perspectives), and screenshot images (for mobile highlight extraction). Anthropic's API does not use submitted data for model training. Anthropic privacy policy: anthropic.com/privacy

c) OpenAI, Google, and xAI (AI processing)

If you use the Debate feature with a model from OpenAI, Google Gemini, or xAI Grok, the selected text is sent to the respective provider's API. This only occurs when you explicitly initiate a debate with that provider's model.

d) Resend (email delivery)

Resend receives your email address and email content for the purpose of delivering digest emails and mobile highlight confirmations. Resend privacy policy: resend.com/legal/privacy-policy

e) Stripe (payment processing)

Stripe processes payments for debate credits. We send Stripe your device ID and purchase amount. Stripe handles all payment details directly and does not share card information with us. Stripe privacy policy: stripe.com/privacy

f) Vercel (web hosting)

Vercel hosts our website and API endpoints. HTTP requests to our API endpoints pass through Vercel's infrastructure. Vercel privacy policy: vercel.com/legal/privacy-policy

storage

Used to store your device identifier, authentication session tokens, API keys, and profile settings locally on your device using chrome.storage.local and chrome.storage.sync.

identity

Used to obtain a Google OAuth token when you choose "Sign in with Google." The token is exchanged with Supabase Auth to create your Verbatim session. The token is not stored beyond the sign-in flow.

Host permissions

The extension requests access to the following domains. Content scripts run only on supported AI platforms to enable highlighting and debate. API domains are accessed only to send requests on your behalf.

—  Access your data — all your highlights are visible in the extension sidebar and dashboard

—  Delete your data — delete individual highlights from the sidebar, or request full account deletion by emailing verbatim.coach@gmail.com

—  Opt out of email communications — unsubscribe from digest emails using the link in any email or by visiting helloverbatim.com/api/unsubscribe

—  Withdraw optional data — remove your email address from extension settings at any time