How to disclose automation and personalization transparently?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

You've probably received an email that said something like "Because you bought X, we thought you'd love Y." Did that feel creepy or helpful? The answer usually depends on how clearly the sender framed it. That's the whole game with disclosing automation and personalization.

The good news is you don't need a legal disclaimer buried in 8-point font. You need plain, human language that tells the recipient why they're getting what they're getting. Think of it as giving context, not confessing a crime.

Where to disclose

The right spot depends on what you're disclosing. For personalized product recommendations or curated content, a brief note near the content itself works best. Something close to "Picked based on your recent order" sitting right above the product block lands far better than a footnote nobody reads. For fully automated sequences (like onboarding flows or re-engagement triggers), a single line near the top or in the preview text is enough. You don't need to repeat it every email.

What language actually works

Keep it useful, not clinical. These phrases land well in practice.

  • Behavior-triggered emails: "We noticed you left something behind" or "You visited this page recently, so we wanted to follow up."
  • Personalized recommendations: "Based on your purchase history" or "We picked these for you based on what you've opened before."
  • Automated sequences: "This is part of your welcome series" or "You're getting this because you signed up for X on [date]."
  • Data-driven segmentation: "We send this to customers who've been with us for a year or more."

Notice what all of these have in common. They explain the reason the recipient is getting this specific email. That's the whole point of disclosure. It's not about admitting you use software. It's about showing the reader you're paying attention to them specifically, not just blasting everyone.

What you don't need to disclose

But you don't owe anyone a tour of your tech stack. Nobody needs to know you're running Klaviyo flows or that your recommendation engine uses purchase history from the last 90 days. What matters is the experience from the recipient's side. Did they get something relevant? Do they understand why? That's it.

There's a meaningful difference between how you use someone's data and how you talk about it. Most recipients don't care that you automated something. They care whether you used their data in a way that felt respectful. A clear, brief signal that you're personalizing for a reason goes a long way toward making automation feel like service rather than surveillance.

The footer question

Footers are fine for legal disclosures, but they're not a substitute for in-body context. If the whole email is a triggered recommendation series and the only mention of that is buried in your ToS link, that's not transparency. It's plausible deniability. Put the relevant context near the relevant content, and save the footer for your physical address and unsubscribe link (where it actually belongs).

If you're thinking about ethical reactivation campaigns, the same principle applies. Tell people why they're hearing from you again, and what you're basing it on.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get disclosure language suggestions for your setup

I'm setting up automated or personalized emails using your ESP or tool and want to disclose this clearly without sounding robotic or legal-heavy. My emails are triggered by describe trigger: purchase, browse, signup, inactivity, etc. and include [describe personalization: product recs, name, location, past behavior]. Suggest specific disclosure phrases I can use, where to place them in the email (subject line, preview text, body, or footer), and whether I need different language for different trigger types.

Edit the yellow boxes, then send to the AI of your choice.