---
title: "Do you have to disclose AI in emails? The rules in 2026"
url: https://signatoro.com/email-signature-compliance/ai-email-disclosure
description: "When an email written or sent by AI needs a disclosure: EU AI Act Article 50, Utah, California, CAN-SPAM, PECR, FINRA and the AI vendors. Not legal advice."
---

# Do you have to disclose AI in emails?

It turns on who sends. An AI agent that writes and sends email to people generally has to say it is an AI and whom it acts for. A draft you review and send yourself carries fewer duties.

> **Not legal advice.** This page is for general educational purposes about email signatures and related compliance themes. It is not legal advice. Signatoro is not a law firm or legal specialist. Laws and guidance change, and what applies to you depends on your jurisdiction, industry, and message type. Consult qualified counsel for your situation.

An email you draft with AI and send yourself generally needs no label. An AI agent that writes and sends email to people carries a duty: since 2 August 2026, the EU AI Act expects it to disclose that it is an AI and, per the Commission, on whose behalf it acts. Utah, California and AI vendors add narrower rules.

## Who this applies to

This page covers email written or sent with AI, by a person or by an AI agent acting for one. The EU AI Act binds the provider of the AI system, which includes a company that builds its own agent and puts it into use under its own name, and it reaches providers outside the EU when the output is used in the EU. In the US there is no single federal AI-disclosure rule for email; Utah and California have narrower state rules. The sender-identity laws (CAN-SPAM in the US, PECR and the ePrivacy Directive in the UK and EU) apply whoever, or whatever, writes the message, and so do the professional rules for brokers and lawyers.

## What it actually requires

### Work out who is actually sending

The Commission's Article 50 guidelines treat an AI system's capability "to write and send messages to natural persons" as direct interaction with people. They leave out "AI assistance tools" that help a person communicate, and AI output passed on by a person rather than by the system itself. A draft you read, edit and send as your own sits on the assistance side; an agent that sends by itself sits on the other.

### If an agent sends, say it is an AI and whom it acts for

Article 50 of the EU AI Act asks for that disclosure in a clear way, no later than the first email - the Commission's own example is an AI label at the top of the message, paired with naming the person or company the agent acts for. Our EU AI Act Article 50 guide covers what that means for a signature in full.

### Answer truthfully when someone asks "is this an AI?"

In Utah, a supplier using generative AI in a consumer transaction must disclose it when the person makes "a clear and unambiguous request" to know (Utah Code 13-75-103). A disclosure made at the outset and throughout the interaction earns a safe harbor (13-75-104). California makes it unlawful to use a bot online with intent to mislead about its artificial identity to drive a sale or influence a vote, and a clear disclosure removes liability (Bus. & Prof. Code 17941).

### Keep the sender identity accurate

CAN-SPAM bars materially false or misleading header information on commercial and on transactional or relationship email (15 U.S.C. 7704(a)(1)). PECR regulation 23 and Article 13(4) of the ePrivacy Directive bar marketing email that disguises or conceals the identity of the person on whose behalf it is sent. The FTC's impersonation rule (16 CFR 461.3) bars falsely posing as a business or its officers.

### Follow your AI vendor's policy

Anthropic's Usage Policy says "All consumer-facing chatbots, including any external-facing or interactive AI agent, must disclose to users that they are interacting with AI rather than a human", and prohibits using outputs to convince people they are talking to a human. OpenAI's Usage Policies prohibit using its services for "deceit, fraud, scams, spam, or impersonation".

### In regulated work, supervise and keep records

FINRA's advertising FAQ D.8 says "Firms are responsible for their communications, regardless of whether they are generated by a human or AI technology", including supervision and recordkeeping. ABA Formal Opinion 512 says lawyers "must disclose their GAI practices if asked by a client" and that firms need clear policies on generative AI use.

## Myths we hear often

**The myth:** A human glance before sending exempts the agent.

**What the source actually says:** The Commission's guidelines say "the mere possibility for humans to intervene or review the AI system's outputs should not be used to circumvent" the disclosure duty. The exemption covers output "properly reviewed and sent by humans as the main interlocutors". On our reading, a one-click approval of mail the agent wrote and sends itself sits closer to the agent side.

**The myth:** The AI Act only applies to EU companies.

**What the source actually says:** Article 2(1) covers providers placing AI systems on the EU market "irrespective of whether those providers are established or located within the Union or in a third country", and providers and deployers abroad "where the output produced by the AI system is used in the Union". A US company whose agent emails people in the EU is generally in scope. The guidelines add that incidental, unforeseeable downstream use alone should not trigger it.

**The myth:** You must label every AI-assisted email.

**What the source actually says:** Article 50(1) is about AI systems that interact with people directly, and the guidelines exclude AI tools that help a person write. The separate labeling duty for AI text in Article 50(4) covers text "published with the purpose of informing the public", and the guidelines list "private, interpersonal correspondence (for professional purposes)" as text that is not published. Labeling assisted email remains a choice many people make.

**The myth:** If the AI wrote it, the AI is responsible for it.

**What the source actually says:** Utah Code 13-75-102 says it "is not a defense" to a consumer protection violation that generative AI made the statement or undertook the act. Under CAN-SPAM, whoever procures a commercial message "initiates" it (15 U.S.C. 7702(9)). FINRA holds firms responsible for AI-generated communications.

## A worked example

### A fictional example: Tallowmere Foods

Tallowmere Foods, a fictional food wholesaler with suppliers in the US and the EU, runs an AI agent that sends follow-ups on late deliveries and open purchase orders. Each email opens with one line: "This message was written and sent by an AI agent." The agent signs with its own signature block: "Ordering assistant (AI agent), on behalf of the Purchasing team, Tallowmere Foods Ltd", followed by the team's direct email and phone number and the company's registered details. The top line answers whether the reader is dealing with an AI; the signature answers on whose behalf it writes and how to reach a person. Because the agent fetches the same signature block on every send, a supplier sees the same disclosure on the first email and on the tenth.

## Questions people ask

### Do I have to disclose AI in emails?

If you write an email with AI help and send it yourself, generally no: no EU, UK or US federal rule covered here requires a label on it. If an AI agent writes and sends email to people, the EU AI Act expects it to disclose that it is an AI and, per the Commission, on whose behalf it acts. Utah adds a duty to answer truthfully when a consumer asks.

### Do I have to tell customers an email was written by AI?

Generally only in three cases: when the AI sends on its own to people in the EU, when a Utah consumer clearly asks whether they are talking to an AI, and when a California bot would otherwise mislead someone about its artificial identity to make a sale. Sector rules can add more, such as a lawyer whose client asks how the work was done.

### Do AI-written emails need a disclaimer?

For an AI agent, the EU AI Act asks for a clear notice at the first email that the reader is dealing with an AI, plus the name of whom it acts for. A short line the reader sees first does that job better than a block of small print at the bottom.

### Is it legal for an AI agent to send cold email on your behalf?

Generally yes, if the email meets the same rules a person would: accurate sender details, a postal address and opt-out on US commercial email under CAN-SPAM, an undisguised sender, a valid opt-out address and, where PECR requires it, consent or a soft opt-in in the UK. In the EU, the agent should also disclose that it is an AI and whom it acts for.

### Where should the AI disclosure go, the top of the email or the signature?

The Commission's worked example puts an AI label at the top of the email. The signature suits the second half of the disclosure, the person or company the agent acts for, because readers already look there for who is writing. Using both is our reading of the guidelines.

### What is a good AI disclosure statement for an email?

Short, plain and placed where the reader sees it first, for example "This email was written and sent by an AI assistant on behalf of [name or team]." Commune's guide to agent email signatures offers three lengths: "AI-assisted reply", "This email was composed by an AI agent.", and a longer line that adds that the reader can reply as usual and a person can review the email. Use the longer one only when a person does review the replies.

### Can an AI agent's email signature carry the disclosure?

Yes. In Signatoro, an AI assistant or company agent signs with a line such as "Sent by Ada, AI assistant to Maya Okafor, Northwind Supply", and gets a matching sentence it can put at the top of the email. A company owner can require one line for every agent. Which wording your situation calls for is for you, or your lawyer, to decide.

## Related guides

- [AI agent email signature compliance](https://signatoro.com/email-signature-compliance/eu-ai-act-article-50-email)
- [AI agent email signature](https://signatoro.com/email-signatures-for-ai-agents)
- [Give your signature to an AI agent](https://signatoro.com/docs/install-signature/agent)
- [Email signature MCP](https://signatoro.com/email-signature-mcp)
- [AI disclosure statement examples](https://signatoro.com/blog/ai-disclosure-statement-examples)
- [Should your AI assistant sign emails as you?](https://signatoro.com/blog/should-ai-sign-emails-as-you)
- [Can an email your AI agent sends bind you?](https://signatoro.com/blog/ai-agent-email-legally-binding)
- [Send email with a signature through the Gmail API](https://signatoro.com/docs/install-signature/agent/gmail-api)
- [Add an Outlook signature with Microsoft Graph](https://signatoro.com/docs/install-signature/agent/microsoft-graph)

## Sources

- [Commune: How do I set up email signatures for my agent? (knowledge base)](https://docs.commune.email/knowledge-base/agent-email-signatures)
- [Regulation (EU) 2024/1689 (AI Act), Articles 2, 3 and 50 - EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202401689)
- [European Commission: Guidelines on the transparency obligations under Article 50 AI Act, C(2026) 5054](https://digital-strategy.ec.europa.eu/en/library/guidelines-transparency-obligations-providers-and-deployers-ai-systems)
- [Utah S.B. 226 (2025), enrolled: Utah Code 13-75-101 to 106](https://le.utah.gov/Session/2025/bills/enrolled/SB0226.pdf)
- [California Business and Professions Code 17941 (bots)](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC&sectionNum=17941)
- [Anthropic Usage Policy (effective September 15, 2025)](https://www.anthropic.com/legal/aup)
- [OpenAI Usage Policies (effective October 29, 2025)](https://openai.com/policies/usage-policies/)
- [16 CFR 461.3 - Impersonation of businesses prohibited](https://www.law.cornell.edu/cfr/text/16/461.3)
- [15 U.S.C. 7704 - CAN-SPAM requirements for transmitting messages](https://www.law.cornell.edu/uscode/text/15/7704)
- [PECR 2003, regulation 23 (UK)](https://www.legislation.gov.uk/uksi/2003/2426/regulation/23)
- [Directive 2002/58/EC (ePrivacy Directive), Article 13](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219)
- [FINRA Advertising Regulation FAQ D.8: AI Created Communications](https://www.finra.org/rules-guidance/guidance/faqs/advertising-regulation)
- [ABA Formal Opinion 512: Generative Artificial Intelligence Tools](https://www.americanbar.org/content/dam/aba/administrative/professional_responsibility/ethics-opinions/aba-formal-opinion-512.pdf)
