惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
Netflix TechBlog - Medium
I
InfoQ
Engineering at Meta
Engineering at Meta
Jina AI
Jina AI
Recent Announcements
Recent Announcements
T
The Blog of Author Tim Ferriss
P
Proofpoint News Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
D
Docker
Microsoft Security Blog
Microsoft Security Blog
宝玉的分享
宝玉的分享
Last Week in AI
Last Week in AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
GbyAI
GbyAI
博客园 - Franky
博客园 - 聂微东
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog RSS Feed
WordPress大学
WordPress大学
MyScale Blog
MyScale Blog
月光博客
月光博客
罗磊的独立博客

Buttondown's blog

Email could have been X.400 times better The physicists who convinced Fermilab to send Brazil's emails Better in-app previews Analytics 3.0 Subscriber ID variables Comments! Send latest premium action Automation filtering Free API subscribers Surveys in automations Reply to replies Labels for RSS feeds How Jeremy Singer-Vine curates curious datasets for readers 2023 (and what's next) Email vs web content Sort by engagement Better gift subscriptions How Andy Dehnart built a career reviewing television New email template Email-based automations Opt-in reply tracking Automatic alt text More social network integrations Sort by metadata Overlarge image warnings Automation tag actions Pause emails mid-flight Search tags and automations Gift via automations Subscriber-driving emails
A spring cleaning for our legal docs
Justin Duke · 2026-03-16 · via Buttondown's blog

tl;dr

None of the below changes reflect any shift in our stance on anything: we just clarified some outdated legalese, removed incorrect info (such as boilerplate copy about "sharing with third-party advertising companies", which we've never done), and pulled out our subprocessors into a formal table.

We just pushed a round of updates to our legal pages — partly prompted by good feedback from a customer working through GDPR compliance on their end, and partly because some of these docs were overdue for a refresh. Here's what changed:

Data processing agreement

Our DPA now includes:

  • A processing details annex (Annex 1), spelling out the subject matter, duration, types of personal data, and categories of data subjects — everything Article 28(3) of the GDPR asks for.
  • A reference to our sub-processor list in Section 5, so you have a stable URL to point to in your records.
  • A GDPR precedence clause in Section 12, clarifying that EU, UK, and Swiss data protection law takes priority over US governing law where there's a conflict.
  • An updated international transfers section (Section 8) that honestly acknowledges data is processed in the US and references Standard Contractual Clauses as the transfer mechanism.

Privacy policy

The privacy policy hadn't been updated since October 2019 — long overdue. The main changes:

  • Removed a reference to third-party advertising companies that was carried over from a template we used years ago. Buttondown has never shared subscriber data with ad networks, and the old language contradicted what we say on our GDPR compliance page. It's gone now.
  • Updated contact information from a personal email to support@buttondown.com across the board.
  • Fixed a broken anchor link and a heading formatting inconsistency.

Sub-processor list

We added two missing entries to our sub-processor list: Stripe (payment processing) and Seline (privacy-focused analytics, which replaced Vercel Analytics earlier this year).

GDPR compliance page

The GDPR page previously said data was only shared "for the purposes of sending your newsletter" — but sub-processors like AWS, Cloudflare, and Sentry aren't really about newsletter delivery. We updated the language to "providing the service" and linked directly to the sub-processor list and DPA.

Cookie policy

We also published a new cookie policy that documents every cookie Buttondown sets, organized by category: essential, functional, and analytics. No third-party advertising cookies, no surprises.

If you're working through your own GDPR compliance and something's missing or unclear, let us know — this latest round of updates came directly from a customer asking good questions.