Your List Is the Only Audience You Actually Own

Here's the uncomfortable math. You spent two years building 90k followers. A platform tweaks one ranking signal on a Tuesday and your reach halves. You didn't lose the audience — you just lost the permission to reach them, which is the only part that ever mattered.

An email list is the version of your audience that can't be throttled, deprioritized, or shadow-anything. It works if the app dies. It works if you leave. Email capture is now live on Zippy — Hero & up — and it turns the taps you were already losing into that list.

Where it lives: the page you were already showing

When someone taps your link from a place that flatly refuses to hand off to a native app, Zippy shows your rich fallback page instead of dumping them into a broken tab. That page was already doing the polite thing.

Now it can do the useful thing too. One small form:

That's the whole play. The tap that was about to bounce becomes a contact with your name on it. And because the form sits on the fallback page, it never gets in the way of the happy path — if the tap can open the real app, it opens the real app. You don't trade conversions for emails.

Consent-first is a feature, not a chore

Most tools treat consent as the compliance tax you pay after building the growth hack. We built the checkbox first and the feature around it.

The box is unchecked. Always. No pre-ticked dark pattern, no "by continuing you agree" buried under a button. If consent isn't an explicit true, the submission is dropped before a single byte is stored. There is no toggle to disable this, because there shouldn't be.

Zippy writes the consent wording, not your form. The exact sentence — "I agree to receive email updates from Ada's Studio via Zippy. I understand I can unsubscribe at any time." — is generated server-side with your name in it and stored per contact. Nine months later when someone asks "when did I sign up for this?", you have the receipt, and it's in your CSV export.

Why this is a feature and not a chore: a list built this way is a list you can actually send to. Everyone who's on it chose to be, knows who you are, and remembers the moment. Open rates follow. A scraped list is a number; a consented list is an audience.

The endpoint tells nobody anything

Small engineering detail with a big privacy consequence. The public capture endpoint returns 204 No Content on literally every path — good email, bad email, honeypot triggered, missing consent, slug that doesn't exist, feature switched off, and crucially: email already on your list.

That last one is the point. If the endpoint said "already subscribed," anyone on the internet could type [email protected] into your form and learn whether that person follows you. That's a leak, and it's your fans' privacy, not yours to spend. So the endpoint is a black hole. Your dashboard knows the truth; the open internet doesn't.

There's a hidden honeypot field for bots and a 254-character cap on emails, because the internet is the internet.

Erasure is free, on every plan, forever

Email capture is a Hero power. Deleting a contact is not.

DELETE on a contact has no tier gate and no flag gate. Free plan? Works. Downgraded from Hero last week and lost access to the list view? Deletion still works. Someone emails you asking to be removed and you're between plans? Still works.

We'll happily charge you for collecting emails. We will never charge you for honouring someone's request to be forgotten. Putting a paywall in front of a data-subject right is the kind of thing that makes people hate software, and any tool that does it is telling you exactly what it thinks of the people on your list.

Getting the list out

It's your data, so it leaves easily:

• CSV export — email, source link, country, the exact consent text, and the timestamp. Formula-neutralized, so nothing weird executes when it hits Excel.
• Webhook — every genuinely new contact fires contact.captured at your own endpoint, email included. Straight into your ESP or CRM, live.
• Dashboard — newest 500 with a running total, and the sourceSlug on every contact so you can see which drop actually built the list. That's the underrated number.

Setup and every field is in the email capture docs.

Pair it with segments

Last week we shipped audience segments — named, live slices of your clicks, including the one nobody else measures: whether the tap actually opened the native app.

Segments answer who is my audience. Capture answers how do I reach them. Segments never store a person; capture stores exactly the people who asked to be stored. Two halves of owning your audience instead of renting it.

And your links still never expire

Nothing on this page changes the deal: a Zippy link redirects forever. Nobody gets a dead link because you turned a form on, turned it off, or never touched it. Capture is additive — it sits on the page, asks nicely, and gets out of the way.

FAQ

How do I collect emails from my link in bio?

Turn on the rich fallback page for your link, then switch on Collect emails. Anyone who taps the link and can't be handed straight to a native app lands on your fallback page and sees a "get updates from you" form with a consent checkbox. Their email goes to your Audience list, and you can export the whole thing as CSV whenever you want.

Do I need a separate email tool to collect emails from my links?

Not to collect them, and — since broadcasts shipped — not to send to them either: you can email a saved segment straight from Zippy, with consent enforced and a one-click unsubscribe on every message. A dedicated tool (ConvertKit, Beehiiv, Mailchimp) is still better at full newsletter operations, and the contact.captured webhook pipes new contacts into one automatically.

Is collecting emails from a link in bio GDPR compliant?

It can be, and Zippy is built for that shape: unchecked consent box, explicit consent required, the exact wording stored per contact with your name in it, and free deletion on every plan. You're the data controller — you decide what you send and you honour unsubscribes. Send what your consent copy promised and you're on solid ground. Double opt-in isn't implemented yet; we'd rather tell you than let you assume a confirmation email goes out.

Will Zippy tell me if someone's already on my list?

Not through the public form — it returns the same empty 204 for every outcome, so nobody can use it to probe who's subscribed. Your dashboard and CSV export show you the real list.

What plan do I need for email capture?

Hero ($19/mo) and up. Deleting a contact works on every plan including Free, permanently, because erasure isn't a feature we're willing to sell.

Followers are a loan. A list is an asset. It shipped here in the changelog — start zipping →