Privacy and safety

How your data is kept apart, what leaves the server, and the guards on sending.

Your data

• Each Gmail address has its own database file; requests can only ever open the signed-in account's file.
• Google tokens are stored encrypted. Sign-in uses an encrypted, http-only cookie that page scripts can't read.
• Changes from other websites are rejected, so another site can't act as you.
• The app reads only threads it started, never your whole inbox.

What leaves the server

To do their jobs, the AI providers receive the text they work on: lead details and facts for writing, reply text for labels, your words for routing and voice. See AI features for the list.

Guards on sending

• Every single email needs your review and confirmation; campaigns need approval of the exact version and a confirmed first send.
• Opted-out and bounced addresses are blocked everywhere.
• A draft can be sent only once.
• No tracking pixels or rewritten links: emails go out exactly as written, and opens aren't tracked.
• Text from web pages and replies is treated as data, never as instructions to the assistant.