Keep NDA threads out of the wrong LLMs.

You want AI help with your everyday inbox, but you’ve also signed NDAs with customers, investors, and outside counsel. Handing a personal LLM or a general-purpose assistant full Gmail access pulls confidential threads into unapproved models—and risks leaking context across clients. comail lets you wall off NDA conversations from your daily tools and isolate sensitive deals to dedicated, locked-down endpoints.

Takes a minute to apply. No credit card required.

you@company.com2 agents · strict NDA boundary

daily-assistant · personal harness / everyday triage

Reads routine threads; walled off from confidential mail

  • Sees ordinary inbox threads (default: allow)
  • Blocked from labels NDA, Board, and Legal
  • Blocked from domains @wsgr.com and @meridian.io

deny-list modeNDA threads hidden

deal-meridian · enterprise LLM (zero data retention)

Clean-room agent scoped to a single NDA counterparty

  • Only sees threads labeled co:deal-meridian
  • Rule auto-labels mail from @meridian.io
  • send restricted to @meridian.io — cannot email outsiders

allow-list modeisolated to 1 deal

Your everyday assistant never sees an NDA thread. When you do want AI help on a confidential deal, a separate agent connects only to your enterprise-approved LLM and can’t email anyone outside that counterparty.

The problem

Full inbox access breaks the promises you made in your NDAs.

Standard mutual NDAs require you to keep confidential materials inside approved systems and restrict them to people and tools with a need to know. All-or-nothing Gmail OAuth fails both tests.

01

Personal AI tools aren’t covered by your DPAs

You might use a personal Claude Desktop, ChatGPT, or OpenClaw setup to triage your inbox or prep for meetings. If that client has full Gmail access, a single search query pulls board decks, term sheets, and NDA-covered customer data into an unapproved model.

02

Context bleeds between clients and deals

If you advise multiple companies or run parallel enterprise deals from one inbox, an agent with full read access can pull facts from Client A’s confidential thread into its context window while drafting a reply to Client B.

03

Routine threads turn confidential mid-conversation

An ordinary intro thread can turn into an M&A discussion or legal dispute three replies in. With standard OAuth, you have no way to pull that single conversation back without disconnecting your assistant completely.

How it works

Wall off your everyday assistant. Isolate each confidential deal.

  1. Put your everyday assistant behind hard exceptions

    Create daily-assistant in deny-list mode (default: allow), then add exceptions for your NDA, Legal, and Board labels, plus outside counsel and counterparty domains like @wsgr.com. Those threads are completely invisible to your general assistant.

  2. Take any thread back from your phone

    When a casual thread turns into an NDA conversation, apply no:daily-assistant in Gmail on desktop or mobile. Because comail checks live labels on every request, the thread is cut off before the agent’s next tool call.

  3. Spin up a clean-room agent for an NDA project

    When you want an enterprise, zero-retention LLM to help with diligence on Project Meridian, create a dedicated deal-meridian agent in allow-list mode (default: deny). Add a rule for @meridian.io so it sees only that counterparty’s threads and nothing else in your inbox.

  4. Lock outbound mail to the counterparty

    Keep send set to drafts only, or restrict deal-meridian’s send permission strictly to @meridian.io. Even if the model hallucinates or misreads an address, comail will refuse to send an email to anyone outside that domain.

daily-assistant — personal harness

> Summarize my unread threads from this morning.

comail · search_threads (query: "is:unread")

thr_10a4: Stripe — “Your payout of $4,812.40 is on the way”

thr_10b9: Ana (Engineering) — “Week 12: what we shipped”

Withheld by exceptions: @wsgr.com, @meridian.io, label:NDA, label:Board

You have two unread threads: this week’s engineering update from Ana and a Stripe payout notice.

Your personal harness searches the inbox freely for everyday work, while NDA, counsel, and board threads are stripped out by comail.
deal-meridian — enterprise claude

> Check Meridian’s latest diligence questions and draft a reply.

comail · search_threads (query: "diligence")

thr_77c1: Meridian Corp <counsel@meridian.io> — “Re: SOC 2 & data residency”

Scope limited to threads carrying co:deal-meridian

comail · create_draft (thread_id: "thr_77c1", to: ["counsel@meridian.io"])

draft_id: "d-9041" · saved in Gmail Drafts

The clean-room agent runs on your enterprise LLM and sees only co:deal-meridian threads—never your other clients or internal mail.

Guardrails

Enforced by comail on every call, not by a system prompt.

Telling an agent “don’t read threads marked NDA” in a prompt doesn’t stop search_threads from pulling them into context. comail enforces the boundary at the API layer before calling Google.

Everyday triage

daily-assistant

Runs in deny-list mode for convenience, with hard exceptions for your NDA, Legal, and Board labels, law firms, and confidential counterparties.

view deny no:daily-assistant
view deny labels: NDA, Legal, Board
view deny domains: @wsgr.com, @meridian.io
view allow default
send deny drafts only

Clean-room deal agent

deal-meridian

Connected only to your enterprise DPA-covered LLM. Scoped to co:deal-meridian, with outbound mail restricted to @meridian.io.

view allow co:deal-meridian
view deny default
attachments allow —
send allow only @meridian.io
01

Whole-thread exception matching

For a deny-list agent, an exception hides the entire thread as soon as any message in it carries the excluded label or has the excluded address or domain in From, To, or Cc. If outside counsel is looped in on reply six, the whole thread is immediately withdrawn.

02

Recipient-locked outbound mail

A clean-room agent can be kept to drafts only, or restricted to emailing only specific addresses and domains. It cannot forward a confidential thread or attachment to a third party.

03

Clean teardown when a deal closes

When a project ends or a counterparty requests data destruction under an NDA, revoke the deal agent from the dashboard. Its credentials are invalidated immediately without disrupting any of your other agents.

FAQ

Common questions.

What happens when a lawyer or investor is CC’d mid-thread?

Exceptions on a deny-list agent are evaluated against the entire thread on every request. The moment a participant from an excepted domain (like @wsgr.com) is added to a conversation, the whole thread—including earlier messages—is hidden from the agent.

Can an excluded agent tell that an NDA thread exists?

No. Hidden threads are omitted from search and list results, and fetching one by ID returns “not found”—the exact same response as a thread ID that does not exist.

Can I let an agent read NDA email bodies without downloading attached PDFs?

Yes. attachments is a separate permission per agent. Turn it off, and the agent only sees attachment filenames and byte sizes—never the file contents.

How many separate client or deal agents can I run on one inbox?

Each inbox supports up to 10 active or paused agents. When a deal wraps up, revoking its agent frees up that slot immediately.

Request access

We’re onboarding beta users in small batches. Tell us what you want your agent to handle; specific use cases go to the front of the line.

Clients / harnesses (optional)

Select all that apply.

We’ll only email you about the beta. No card, no newsletter.