Do you read my entire inbox?

No. We only fetch on Pub/Sub events (one message at a time) plus a one-time bootstrap of your sent folder for voice learning. Bootstrap bodies are purged within 7 days; only derived style patterns persist.

What scope do you ask for?

gmail.modify (so we can draft and send), gmail.settings.basic (for filters), and calendar.events. We do NOT ask for gmail.readonly because we have to be able to send the drafts.

Yes — at any time from /settings/connectors or directly from your Google account. Revoking stops all drafting immediately.

Does it work with a personal Gmail address?

Yes, but Tacitry is designed for high-volume work email. Personal accounts rarely have enough repeat-recipient patterns for autonomy to compound.

Tacitry × Gmail

Tacitry for Gmail

Drafts every inbound, sends what it has earned the right to send.

By Sid Sharma, founder · May 23, 2026

Start my free trial →7 days free. Cancel anytime from settings.

Tacitry connects to Gmail via OAuth (gmail.modify scope, no full inbox sync) and drafts a reply to every inbound that needs one. Voice is learned once from your last ~300 sent replies (purged within 7 days), then refined by every correction you make. Tacitry uses the same OAuth account as Google Calendar (one consent screen, one connection), reads inbound via Pub/Sub the moment a message lands, and writes drafts the way you would write them. No bulk inbox sync — we only fetch on events, plus the one-time bootstrap.

What Gmail data flows into Tacitry?

Inbound message bodies and headers (only on Pub/Sub events, never bulk scan).
Your last ~300 sent replies, used once to seed voice + style counters, then purged within 7 days.
Thread context resolved via In-Reply-To / Message-ID headers, not heuristics.

What does Tacitry do with Gmail data?

Drafts a reply to every inbound that needs one — using your voice, your facts, your rules.
Sends RFC-compliant mail when you have earned trust for that recipient (per-recipient autonomy curve).
Marks autonomous sends with RFC 3834 headers so they never trigger loops.
Routes corrections back into the rule store so the next draft does not repeat the same mistake.

Tacitry + Gmail live in every draft. Setup takes about a day.

Start my free trial →

How do I connect Gmail to Tacitry?

Sign in with Google on tacitry.app. We request gmail.modify (not readonly — we need to send) and calendar.events.
Approve the consent screen. Tacitry stores an encrypted refresh token and registers a Pub/Sub watch.
Bootstrap runs in the background — your last ~300 sent replies are read once to build a voice profile.
New inbound triggers a draft within seconds. Open the review queue or your Gmail drafts folder.

Frequently asked

Do you read my entire inbox?: No. We only fetch on Pub/Sub events (one message at a time) plus a one-time bootstrap of your sent folder for voice learning. Bootstrap bodies are purged within 7 days; only derived style patterns persist.
What scope do you ask for?: gmail.modify (so we can draft and send), gmail.settings.basic (for filters), and calendar.events. We do NOT ask for gmail.readonly because we have to be able to send the drafts.
Can I revoke access?: Yes — at any time from /settings/connectors or directly from your Google account. Revoking stops all drafting immediately.
Does it work with a personal Gmail address?: Yes, but Tacitry is designed for high-volume work email. Personal accounts rarely have enough repeat-recipient patterns for autonomy to compound.

Other integrations

Tacitry, with Gmail in every draft.

Start my free trial →

7 days free. Cancel anytime from settings.