Inbox Brief

Privacy Policy

Last updated: July 19, 2026

What Inbox Brief Does

Inbox Brief summarizes recent Gmail messages and recommends sender cleanup actions. It does not send, modify, delete, archive, or block emails.

Data We Access

Inbox Brief requests Gmail readonly access through Google OAuth. The extension uses this access to fetch message metadata and limited message text for the inbox range selected by the user.

How We Use Data

Email data is used only to generate important message summaries, middle-ground review suggestions, sender cleanup recommendations, and deadline notes.

Data Processing

Selected message data is sent to the Inbox Brief backend API. The backend verifies that every submitted message ID is currently in the Gmail inbox and falls within the selected 24-hour, 48-hour, or seven-day range using Gmail's message metadata before sending selected message text to the OpenAI API. The backend does not intentionally persist email content. OpenAI Responses requests set store: false, which disables Responses application-state storage. OpenAI states that API data is not used to train its models by default, but its standard abuse-monitoring logs may retain customer content for up to 30 days unless enhanced data controls apply to the account.

Local Storage

Inbox Brief stores settings and the latest generated brief locally in Chrome storage. Users can disable local brief caching in the extension settings.

Tokens And Secrets

Gmail OAuth tokens are managed by Chrome Identity. The backend uses the token only in memory to verify the signed-in Gmail account and the inbox status and internal date of submitted message IDs for the current request. Inbox Brief does not intentionally log, persist, or send Gmail OAuth tokens to OpenAI, Stripe, or Upstash. OpenAI and Stripe secret keys are stored only on the backend and are not included in the Chrome extension.

Usage Quotas

Inbox Brief uses Upstash Redis to enforce daily brief quotas. For signed-in requests, Upstash receives an opaque keyed account identifier and quota counter, not an email address, Gmail token, message ID, or email content. During the short legacy-extension migration, the backend uses a one-way keyed hash of the network address for a one-brief-per-day quota; it does not send the raw network address to Upstash. Free accounts currently receive three briefs per day and Pro or trialing accounts receive 20.

Billing Data

If you start a trial or subscribe to Pro, Inbox Brief sends your verified Gmail email address and a one-way, opaque identifier derived from your stable Google account subject to Stripe. Stripe uses these details to create and manage your customer account, subscription, payment method, invoices, and billing portal. Stripe processes payment details under its own privacy terms. Inbox Brief does not send email content or Gmail OAuth tokens to Stripe and does not store full card details.

Data Sharing

Inbox Brief does not sell user data. Email content is processed only to provide the requested inbox brief. Account and billing data is shared with Stripe only when needed to provide trials, subscriptions, and billing support.

Google API Limited Use

Inbox Brief's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

For support or privacy questions, email pranjal.chaya@gmail.com.