Security · For IT and security teams

Is it safe to connect company email to textagent.io?

Short answer: it passed Google's CASA Tier 2 security assessment, it signs in through Google or Microsoft so it never sees a password, it can't delete email, and nothing goes out without the user's OK. Here's the detail your security review will ask for.

Google CASA Tier 2, passed September 29, 2026

textagent.io reads and sends Gmail, so Google treats it as using restricted scopes. Before an app gets those scopes, Google requires a Cloud Application Security Assessment (CASA). Ours is Tier 2, the OWASP ASVS-based level Google requires for the restricted gmail.modify scope and the Calendar scopes.

A Google-empanelled third-party assessor completed it on September 29, 2026 and submitted the Letter of Assessment to Google that day. Google requires it again every year, and we pay for it.

What it can access, and what it can't

When someone connects a mailbox, textagent.io asks for permission to:

It does not access contacts or files. It cannot permanently delete email.

Nothing goes out without the user's OK

textagent.io drafts replies and texts them to the user first. It sends only when the user says send. There's no fully automatic mode, and it isn't a setting an admin or user can switch on. An AI agent with inbox access shouldn't be the one approving its own actions, so the approval lives on the user's phone, in the text thread.

Sign-in and access

People connect with Google or Microsoft sign-in (OAuth). textagent.io never sees or stores an email password. Access can be revoked at any time from the Google account permissions page or the Microsoft account apps page, and it ends immediately on the provider's side. Google Workspace and Microsoft 365 admins can also allow or block third-party apps like textagent.io with the admin controls they already have.

How data is protected

AI and your data

The reasoning runs on Anthropic's Claude models through AWS Bedrock. Your email, calendar and conversations with the agent are never used to train any AI model, by us or by Anthropic. Data from Google Workspace APIs is used only to provide the features the user sees.

Who else touches the data

Only the providers needed to run the service, under contract:

We don't sell data, and none of these providers may use it for their own marketing. Full details are in the privacy policy.

What we don't have yet

There's no SSO, no DPA and no admin console today. Each person signs up and connects their own mailbox. If your approval depends on one of these, email [email protected] and tell us which one. That's how we decide what to build next.

Common security questions

Is it safe to connect company email to textagent.io?
textagent.io connects through Google or Microsoft sign-in, so it never sees or stores a password. It passed Google's CASA Tier 2 security assessment on September 29, 2026, which Google requires before an app can use restricted Gmail scopes. It can't delete email, and nothing is sent without the user's OK.
Has textagent.io passed Google's CASA assessment?
Yes. CASA Tier 2, completed September 29, 2026. A Google-empanelled third-party assessor ran the assessment and submitted the Letter of Assessment to Google. It covers the restricted gmail.modify scope and the Calendar scopes. Google requires it to be renewed every year.
Can textagent.io send email on its own?
No. It drafts, shows the user the draft by text, and sends only when the user says send. That isn't a setting anyone can turn off.
Can textagent.io delete email?
No. If the user explicitly asks, it can move a message to the trash folder. It cannot permanently delete anything.
Is our data used to train AI models?
No. Reasoning runs on Anthropic's Claude models through AWS Bedrock, and neither textagent.io nor Anthropic trains models on customer data.
Does textagent.io support SSO or sign a DPA?
Not yet. There's no SSO, DPA or admin console today. Each person signs up and connects their own mailbox. If your approval depends on one of these, email [email protected] and say so.
Who do we contact with security questions?
Email [email protected]. You'll hear back from the person who built textagent.io.
How do we cut off access?
Revoke textagent.io from the Google account permissions page or the Microsoft account apps page and access ends immediately on the provider's side. Workspace and Microsoft 365 admins can also block the app with the controls they already use.

Questions from your security team?

Email [email protected] and you'll get an answer from the person who built it.

Email a security question →