How writers are reacting to Substack’s AI transparency tools
Honest conversation, the first wave of “How I make this” statements, and an upcoming series on how publishers are using and feeling about AI
Substack promotes its AI transparency tools, which allow readers to scan text for AI assistance and enable writers to disclose their creative process. The company aims to bring transparency to AI use in writing, helping authors get credit for their work and readers make informed choices. Substack features reactions from various writers on the topic of AI disclosure and its impact on writing.
Read this email as text
for screen readers, or when images don't load
Forwarded this email? Subscribe here for more
How writers are reacting to Substack’s AI transparency tools
Honest conversation, the first wave of “How I make this” statements, and an upcoming series on how publishers are using and feeling about AI
READ IN APP
“Spot the difference” by Joro Chen, Brand Designer at Substack
Earlier this week, we announced a feature that allows readers to scan text published to Substack to see how much of it is estimated to be written by hand or with AI assistance. We also launched tools for publishers, including the ability to run the program—Pangram—on drafts prior to publication, disable scanning on a post-by-post basis, and add a “How I make this” statement explaining their creative process to set expectations for their readers. These features do not use publisher content, either through Substack or Pangram, to train generative AI models and are now available on web, iOS, and Android.
Norms around AI use and its disclosure are unsettled. But we have made the assessment that while the use of AI isn’t necessarily a problem, a lack of transparency around it definitely is. Our aim is to help writers get credit for the work that’s theirs and help their audiences make more informed choices about what they spend their time on.
Email headers
sender, ESP fingerprints, unsubscribe and auth headers
As received, minus the delivery side: the archive's own addresses appear as [recipient], relay hops and signatures are left out, and unsubscribe links are trimmed to their host.
- Received-SPF
- pass ([receiver]: domain of [recipient]@mg-d1.substack.com designates 159.112.244.6 as permitted sender) receiver=[receiver]; client-ip=159.112.244.6; envelope-from="[recipient]@mg-d1.substack.com"; helo=v56.v5375b7fa.use4.send.mailgun.net;
- Authentication-Results
- [receiver]; dkim=pass header.d=mg-d1.substack.com header.s=k1 header.b=Lg2fBOj8; dmarc=pass header.from=substack.com policy.dmarc=reject; spf=none ([receiver]: no SPF records found for [email protected]) smtp.helo=v56.v5375b7fa.use4.send.mailgun.net; spf=pass ([receiver]: domain of [recipient]@mg-d1.substack.com designates 159.112.244.6 as permitted sender) smtp.mailfrom=[recipient]@mg-d1.substack.com; arc=none smtp.remote-ip=159.112.244.6
- X-Mailgun-Sid
- WyJkOWY3MSIsInN1YnN0YWNrQGluYm94YXJjaGl2ZS5vcmciLCIzOWIwOGM2Il0=
- X-Mailgun-Sending-Ip
- 159.112.244.6
- X-Mailgun-Batch-Id
- 6a639d875a750c9c58b1e053
- Mime-Version
- 1.0
- Content-Type
- multipart/alternative; boundary="65ca9fe5633dd9e93203a39c7a35e32a63115c786f83f9cc14788fa1a276"
- Subject
- How writers are reacting to Substack’s AI transparency tools
- From
- Substack <[email protected]>
- X-Mailgun-Tag
- post
- X-Mailgun-Track-Clicks
- false
- Message-Id
- <[email protected]>
- Date
- Fri, 24 Jul 2026 16:00:34 +0000
- Feedback-Id
- post-208261413:cat-post:pub-1:substack
- Sender
- Substack <[email protected]>
- References
- <[email protected]>
- In-Reply-To
- <[email protected]>
- Reply-To
- Substack <reply+3fzrj9&8psttm&&9c819bdbdfe925340f6bd6780912c4bb34201f6b0ec2455424f426db11526a4a@mg1.substack.com>
- List-Owner
- <mailto:…@substack.com>
- List-Url
- <https://on.substack.com/…>
- List-Archive
- <https://on.substack.com/…>
- List-Id
- <on.substack.com>
- List-Post
- <https://on.substack.com/…>
- List-Unsubscribe
- <https://on.substack.com/…>
- List-Unsubscribe-Post
- List-Unsubscribe=One-Click
- X-Mailgun-Variables
- {"category": "post", "email_generated_at": "1784913287279", "is_freemail": "true", "post_audience": "everyone", "post_id": "208261413", "post_type": "newsletter", "pub_community_enabled": "true", "publication_id": "1", "subdomain": "on", "user_id": "527064826"}
Archived for reference and commentary. Substack, its logos and content are the property of their respective owners; Inbox Archive claims no affiliation and has disabled all links. If you own this content and would like it removed, get in touch.
Similar campaigns from other brands
Different brands running the same play. Compare any of them side by side.