Send-only privacy

We never read your inbox. By design, forever.

Other outbound tools ask for mailbox read access to detect replies and bounces. We refuse. Wowere requests gmail.send only — Microsoft Graph uses the equivalent send-only surface. Reply detection works through signals that don't require touching your mail.

Scope comparison

What Wowere asks for — vs. what a typical outbound tool asks for.

Wowere

  • gmail.send
  • Microsoft Graph Mail.Send
  • gmail.readonly
  • gmail.modify
  • Mail.Read

Rejecting read scopes is a permanent rule in this codebase. A pull request that adds one is a PR we refuse to merge.

Typical outbound tool

  • gmail.send
  • gmail.readonly
  • gmail.modify
  • Read your inbox + sent
  • Parse replies from your mailbox
  • Access labels and threads

Powerful — and also a massive attack surface, compliance burden, and trust ask.

Why we drew the line

The cost of reading your mailbox is bigger than the feature it unlocks.

Once a tool has mailbox read access, it has everything — client emails, HR threads, personal notes. The least-privilege version of outbound is simpler to secure, simpler to audit, and simpler to trust.

Reply detection works fine from the recipient side — tracking pixels on our own wrapper domain, click signals, calendar-link redemptions. For bounces, we surface the provider-level feedback that Gmail and Microsoft return during the send itself. None of that requires reading a single message in your inbox.

If a feature we wanted seems to require read scopes, it's either out of scope forever or rebuilt around signals we can collect without touching your mail.

Policy lives in AGENTS.md, enforced in OAuth configuration, verified in code review.

Start with a search

Try it with a real search.

Describe the customers you want. Wowere returns 100 — with LinkedIn, email, and more.

Free to start — 25 searches and 10 verified emails included. No credit card required.

Keep reading

CampaignsSecurity overviewAutomation