Launched on Launchit
Security

Yes, it reads your email.
Here is exactly what happens to it.

Your email is encrypted with AES-256-GCM at rest and TLS in transit. Some AI calls replace names with placeholders before the model sees the text. And nothing sends without your approval.

How it works

Three guarantees, built into the system.

Not policies we could quietly change — properties of how the product is put together.

Encrypted before it leaves you

Records, tokens and cache are encrypted with AES-256-GCM at rest and TLS in transit. Some AI calls replace names and addresses with placeholders before the model sees the text, and restore them after; not every call does yet. Email content is processed for the task at hand, not warehoused.

AES-256-GCM at rest, PII stripped in some model calls

Never used for training

Your email is never used to train AI models — not ours, not our providers', not anyone's. What the AI reads to finish a task stays in that task.

No training. Ever.

Google OAuth, revocable

Mailient connects to Gmail through Google's OAuth. We hold no password, we ask only for the scopes we use, and you can revoke access from your Google account in one click.

Isolated token, revoke anytime
What we ask Google for

Three permissions. No more.

Exactly what the Google consent screen shows you — and why each one is there.

gmail.readonly

Read your mail

So it can triage what arrives and draft replies in context. Reading is where the work starts.

gmail.modify

Label & organise

So it can archive, label and file — the tidying you'd otherwise do by hand. It cannot permanently delete on its own.

gmail.send

Send the replies you approve

So an approved draft actually goes out. Nothing sends without your say-so.

We never request access to Drive, Contacts, or the rest of your Google account.

Straight answers

What people ask before they trust us.

No hedging. If a question isn't here, the answer is one email away.

Can Mailient read my email?

It reads what it needs to do the job you asked for — you cannot triage an inbox without reading it. Stored data is encrypted with AES-256-GCM at rest and TLS in transit. Some AI calls swap personal details for placeholders before the model sees the text, and restore them after; not every call does yet. It is never used to train a model, and nobody here routinely reads your mail.

What exactly can it access?

Only the three Google permissions listed above — read, organise, and send. Nothing else in your Google account: not Drive, not Contacts, not your password.

Do you sell my data?

Never. Your email content and identity are not sold to advertisers, data brokers, or anyone. We also set no advertising or cross-site tracking cookies.

What happens if I delete my account?

Your personal data is deleted or anonymised within 30 days, except where the law requires us to keep a record. Revoking Mailient's Google access takes one click in your Google account and cuts off inbox access immediately.

Who else touches my data?

Only the vendors needed to run the service — cloud hosting, the payment processor, the AI model providers, and the email sender — each under a data-processing agreement that forbids using your data for their own purposes. Never for advertising or profiling.

Nothing sends without me, right?

Right. Every reply is a draft until you approve it. The agent proposes; you decide. There is no mode where it emails people on your behalf without a review step.

Read further

The full picture, in your own time.

The architecture, the policies, and the switch that's always yours to flip.

Every claim here is verifiable in how the product behaves: encryption happens in your browser, drafts wait for your approval, and revoking access takes one click in your Google account.

Security questions? Email mailient.xyz@gmail.com — you'll get an answer from the person who wrote the code.