Never sign up for a newsletter with the address that unlocks your accounts. Newsletters are the quietest way a real address gets shared, tracked and exposed, so use one reading alias for every subscription, and pause it the moment a sender shares it or gets too noisy. I run AliasFleet, an email-alias service: one forwarding address per site, so a leak names its source.
A newsletter feels small. You type your address, a welcome email lands, you read a few issues. But that one form puts your address in more hands than the sender's: their list and their email platform. Sometimes partners and sponsors get a copy too. Every new subscription is another copy of your address in another database, and you get no say in how long any copy is kept.
The signup that keeps sharing
Pick a newsletter you like and read its privacy policy. The sharing is usually in plain sight. Adweek's policy says it "selectively makes its postal mailing address list and email list, for customers in the United States, available to third party partners" and passes event-registration data to event sponsors. Adweek offers an opt-out. Adweek is not unusual. Passing lists around is documented business, and your address is what gets passed.
I am not saying every newsletter sells its list. No source I read supports a blanket claim. What is verified is that sharing with partners happens, and that the law has to forbid a worse version of it. The FTC's CAN-SPAM guide says that once someone opts out, the sender cannot sell or transfer their address, except to a company hired to help with compliance. A rule like that exists because transfer is live practice, not hypothetical.
Before you subscribe, run one check. Open the privacy policy, search for "third party" and "partners", and see what happens to your address after you hand it over. If the policy stays vague, treat that as the answer. Use the alias.
What opening the email tells the sender
Open a newsletter and it phones home. Inside most marketing mail sits a tracking pixel, a transparent image one pixel square, tied to a unique subscriber ID. Load it and the sender's server notes the open, the time, your IP, your device, and your mail client. Sendigram's explainer states it plainly: each pixel belongs to one subscriber, so every open is pinned to a person, not just added to a total.
That log builds across campaigns. Open every issue and the sender learns when you read and on what device. Keep opening and they learn how often too. Click a link and the picture sharpens, because links usually run through the sender's redirect server first, which records the click before it sends you on.
Two settings blunt the reporting. In Gmail, set Images to "Ask before displaying external images" and nothing loads until you say so. Gmail otherwise proxies images, which hides your IP, yet the open still reaches the sender, as Live2Tech's Gmail walkthrough explains. Apple Mail preloads remote content through Apple's proxies and hides your real IP, which makes open events unreliable for senders, while clicks still track, per Braze's breakdown. The full pixel mechanics are in our email tracking guide.
Pixel blocking stops the reporting, not the database entry. The sender still holds your address, and no setting fixes that.
A mailing list is a breach waiting for a vendor
A newsletter list is a database of addresses, and databases leak. The worst cases hit the vendor that sends the mail, not the newsletter itself.
| Incident | What happened | What it meant for subscribers |
|---|---|---|
| Epsilon, 2011 | Email service provider breached; about 75 client companies affected | Conservative estimates put 50 to 60 million customer email addresses breached, possibly up to 250 million, per the Privacy Rights Clearinghouse |
| Mailchimp, 2022 | Attackers reached Mailchimp internal tools through phishing and social engineering; 214 accounts affected | Stolen addresses were used to attempt password resets on DigitalOcean accounts; accounts with two-factor authentication were protected, per BleepingComputer |
| HubSpot, 2022 | A compromised employee account exposed data from fewer than 30 portals | Names, email addresses and phone numbers exposed, per TechTarget |
| OpenSea via Customer.io, 2022 | An employee of email vendor Customer.io misused access to download and share addresses | Newsletter subscriber emails were included; OpenSea told anyone who had shared an email to assume they were impacted, per Cointelegraph |
The subscriber did nothing wrong. They joined a list that turned into someone else's phishing list. One leaked address does not empty an account on its own. It feeds the phishing that tries to. If your address turns up in a known breach, check Have I Been Pwned and follow our breach-response guide.
Unsubscribe stops the mail, not the record
Unsubscribe is worth using. From a legitimate sender, it is the clean exit. US law, in the CAN-SPAM Act itself, requires commercial mail to carry a working opt-out, honoured within 10 business days, with the mechanism kept working for at least 30 days after the message is sent. From a sender you signed up with, the unsubscribe link is the right move.
It stops the mail, not the record. The sender still holds your address. One publisher, The AI Journal, states it keeps unsubscribed addresses for 12 months for a suppression list, plus up to 30 to 90 days in backups. That is one publisher's policy, not an industry standard. It shows the shape of it: unsubscribe takes you off the sending list, not out of the database.
Pausing an alias stops its mail for now and can be undone, while killing one ends it for good. Killing an alias is the other tool, for a different situation. Unsubscribe when the sender is legitimate and you just do not want the mail. Kill the alias when the sender shared your address, sold it, got breached, or will not stop mailing you. Unsubscribe depends on the sender playing along; kill the alias and you are done. Our spam guide covers both exits.
One exception. Never click unsubscribe on obvious scam mail. The click tells the scammer the address is live, and a live address draws more attention. Report it as spam instead. That rule covers mail you never signed up for. For a real newsletter, unsubscribe is safe.
The one case for your real address
One case calls for your real address. A newsletter tied to a paid account or an identity check should use that account's address. A bank, a broker, or a membership that verifies you by email needs the matching address. Moving it to an alias can break verification or lock you out of recovery.
Account notices, receipts, and security alerts are not newsletters. They are transactional mail, and they belong on the address that owns the account. This rule covers subscriptions you read for interest, not mail the account sends.
One reading alias for all of them
Set up one alias, called something like reading, for every newsletter signup. It forwards to your real inbox, so everything lands in one place. The sender never sees your real address. An email alias is a persistent forwarding address under your control, not an address with an expiry date, and it keeps working until you decide otherwise.
When a sender misbehaves, pause that one alias and the whole channel goes quiet. The rest of your mail carries on. Start with the one shared alias; if you later want to know exactly which sender leaked an address, you can upgrade to one alias per sender, so the address on any junk mail names the sender, as our leak-tracing guide explains.
The set-up guide takes about two minutes. Create the alias, paste it into the next signup form instead of your real address, and send yourself a test message.
Start with the next signup
Start with the next newsletter, not the whole backlog. Create the reading alias, use it on the next signup, and let the habit build. For subscriptions you already hold, move the ones you read when you next open them, and leave the rest alone. Your old address is already out there. No alias pulls it back.
Change the image setting in your mail client too, so pixels stop reporting your opens. The alias keeps your address out of the database, while the image setting stops the opens from reporting back. Between them, a newsletter turns back into what it should have been: something you read, not something that reads you.
