Privacy

Know where your mail goes.

It depends on the mode you pick. PigeonBox never switches for you.

Sealed by default

Data flow

Local

Free · Open source
  1. Gmail

    The tab you have open. No Gmail API OAuth.

    RawMeta
  2. PigeonBox extension

    Keys stay in the extension, never the page.

    Raw
  3. Browser index

    Index, drafts and settings on this computer.

    RawMetaDerived
  4. Local AI

    On-device or Ollama. Your own key only if you add one.

    Raw · requestDerived
  5. Your tracker (optional)

    A tracker you host. Never bodies.

    MetaEvents

Cloud beta

Early access
  1. Gmail

    Via the extension, plus Google APIs if you connect.

    RawMeta
  2. Cloud, over TLS

    Processed for the task. Never logged.

    Raw · in transit
  3. Hosted processing

    One model. No silent fallback.

    Raw · in memoryDerived
  4. Cloud store

    Metadata and encrypted summaries. Deleted with your account.

    MetaDerived · encrypted
  5. Cloud tracker · testing

    Metadata and events. Never bodies.

    MetaEvents

Cloud doesn’t keep mail bodies by default. Opt-in Fast Recall stores encrypted excerpts until you turn it off.

Local

  • Works in your open Gmail tab. No Gmail API OAuth, no Google cookies.
  • Index, drafts, rules and settings stay in your browser.
  • On-device models and Ollama keep AI on your machine.
  • Add your own provider key, and that provider sees what you send it.

Cloud

  • Opt-in, private beta.
  • Requests go over TLS to PigeonBox Cloud and one configured model.
  • Request bodies are never logged.
  • If Cloud fails, you get an error. Nothing reroutes.
  • Connecting Google is a separate step, scope by scope.
  • Real-time Pidgy checks are off until you turn them on. Then, while you write, a short phrase from your unsent draft (up to 700 characters, never the whole draft) is checked against your calendar and Brain, then discarded. It isn’t stored, logged or turned into a memory.

What Cloud keeps

  • Metadata: senders, recipients, subjects, IDs, times.
  • Derived data: summaries, drafts, search text. Encrypted.
  • Fast Recall: opt-in encrypted excerpts, for as long as you choose.
  • Usage: counts and timing. No content.
  • Account: sign-in and subscription status. Stripe handles cards.

Not message bodies, by default. Every row is locked to your account.

Tracking

Optional. A tracker keeps the subject, sender, recipients and send time, plus each open or click with a hashed IP. Never the body.

An open is a signal, not proof of a read.

Analytics

No ads, no cookies, no fingerprinting. This site counts page views, install clicks and dashboard sign-ins without cookies or browser storage: PigeonBox Cloud receives the page path, a referrer category (such as search or webmail) and known campaign tags (such as utm_campaign=sent_with from the Free email footer), derives a visitor hash from the day, IP address and browser that changes every day, and forwards the event to PostHog. The IP address is not forwarded or kept. Global Privacy Control and Do Not Track turn this off.

The extension sends anonymous usage events by default, such as “footer kept” or “first tracked email”, with its version, a few fixed labels and a random install ID. Never mail, subjects, addresses, searches, document names, Gmail IDs or your account. Turn it off in Settings → Privacy & data; that deletes the install ID. For accounts, PigeonBox records signup, first hosted-tracking use, checkout and plan changes under a keyed hash of the account ID, never the email address.

Cloud waitlist

Submitting the waitlist form stores your normalized email address, signup source (website or extension), and signup time in our Supabase project for Cloud launch access. Only the PigeonBox backend and project administrators can access these records. Duplicate emails are stored once. We send no automatic email and use no mailing service.

Opening the waitlist does not enable Cloud or authorize Gmail access. Rate limiting uses a salted IP hash. Signups are kept until launch access is handled or you request removal through our contact page.

Deleting data

Clear the local index in Settings, or uninstall. Deleting a Cloud account is designed to remove its Cloud data.

Describes the current architecture, not a final legal notice. Details: privacy policy, privacy model, security.