How do you respond when a sponsor asks for subscriber data or list access?

Sponsors sometimes ask for email addresses, demographics, or a co-registration option. Most of those requests can be met with aggregate data and clear boundaries, without handing over your readers.

Julien Jimenez

September 7, 2026 · 4 min read

Why the request comes up, and why the answer is usually no

Sponsors want to know who they are reaching and to prove the spend worked. Sometimes that turns into a request for the email addresses of everyone who clicked, or an ask to add your subscribers to their list. The sponsor's marketer is rarely being sinister; they are used to lead-generation channels where contacts are the product. Newsletter sponsorship is not that. Your readers subscribed to you, not to your sponsors, and handing over their addresses breaks the promise your signup form made, whether or not your privacy policy technically permits it. Related: How to Price Newsletter Sponsorships

There is a legal dimension as well. Sharing personal data with third parties triggers obligations under state privacy laws (California's is the best known, and several other states have followed with their own) and under your own published privacy policy, which readers can hold you to. Even where sharing might be permitted with notice, the reputational cost when readers figure it out is high and lasting. The simplest position, and the one most publishers take, is that subscriber data is never shared with sponsors in identifiable form. That is not legal advice; check your own policy and, for anything unusual, a lawyer.

Keep reading: How to Price Newsletter Sponsorships, Building a Rate Card That Sells, What Sponsors Actually Want to Know. See how AdSlotly helps you sponsorship rate card and slot booking for newsletters.

Aggregate audience data answers most of what the sponsor really wants to know. List size and typical delivered volume. Open and click ranges from recent sends. The share of readers by broad role, industry, or region if you have surveyed them. Email domains grouped by type, such as corporate versus personal or by sector, without listing individual addresses. Reader survey results about job titles, company size, or purchasing responsibility. None of that identifies anyone, and it is far more persuasive to a buyer than a spreadsheet of email addresses would be. Related: Reporting Results to a Sponsor

Per campaign, share what the sponsor's link actually did: total clicks, unique clicks, the click rate against your typical range, and how clicks were distributed over the days after the send. If they use tracking parameters on their link, they will see downstream behavior in their own analytics anyway. If you are comfortable, offer to run a short reader poll with a sponsor-relevant question as part of a package. Sponsors value that highly, and readers opt in by choosing to answer.

Co-registration and lead capture, if you offer them

Some publishers offer a sponsored signup: a checkbox or a separate form where readers actively choose to hear from the sponsor. This can be legitimate if the reader's consent is explicit, specific to that named sponsor, and not pre-checked, and if the sponsor receives only the people who opted in. Price it separately from sponsorship, and be candid that it usually converts a small fraction of the audience. Do not imply otherwise to close the deal.

Do not run co-registration if your platform cannot record consent per sponsor, if you cannot honor a reader's request to know who received their data, or if the sponsor will not commit in writing to using the contacts only as consented. Many publishers decide the revenue is not worth the operational and trust burden and stick with aggregate data and plain sponsorship. That is a reasonable choice, and it is easy to explain to a sponsor in one sentence. Related: Filling Your Open Sponsorship Slots

How to say it and where to write it down

Answer the request directly and without lecturing: you do not share subscriber data with sponsors in any identifiable form, and here is what you can provide, followed by the aggregate package. Most sponsors accept that immediately, and the ones who do not are often not a fit anyway. If a sponsor cites a contract clause, ask them to point to it, and check it against your own terms before responding. Requests like this are much easier to handle when the answer is a policy rather than a judgment call.

Put the policy in three places: your rate card (one line under audience data), your sponsorship terms (a short clause), and your public privacy policy (what you do and do not share, in plain words). Then make sure your practice matches. If you use a booking or reporting tool, confirm that sponsors can see only aggregate campaign data. A written policy ends the conversation faster than any argument, and readers who go looking will find that you meant what you said. Related: Building a Rate Card That Sells

Key takeaways

Never share subscriber data with sponsors in identifiable form; your readers signed up for you, not for them.
Aggregate audience and campaign data answers the sponsor's real question and sells better than a list would.
Co-registration is only defensible with explicit, per-sponsor, unchecked consent and written limits on use.
State the policy on the rate card, in your terms, and in your privacy policy, and confirm your tools match it.

Written by

Julien Jimenez

Julien Jimenez is an independent software builder based in Paris. He designs, ships, and operates focused SaaS products for small businesses and independent professionals. Read the full author page.