The Contact Page Is a Privacy Hazard—It Doesn't Have to Be
The moment you hand over a number
I keep hearing versions of the same story. A freelance designer publishes her phone number on her portfolio page—the same way everyone does—because people wanted an easy way to reach her.
Within a week, the calls started. Not from potential clients. Robocalls. Then came the texts asking to confirm her bank login. Then a trickle of inquiries from people claiming to be from the IRS. Within months, she had to change her number. The number that was supposed to make her easier to reach had become a liability.
A public figure gets their SIM swapped. A small business owner's voicemail becomes a vector for fraud. A content creator watches their number get harvested and resold. The contact page, meant to be a gateway, turns into an attack surface. And we've all normalized it—we see the phone number on every website and assume this is just how it works.
But it isn't. It's broken. And it was never inevitable.
The web contact pages were built for doesn't exist anymore
Contact pages were invented for a different web. A web with a few hundred trusted readers who saw your page once or twice. A web where scrapers were rare and phone numbers weren't commodities. That web is gone, but the contact page didn't update.
Today, the moment you publish a phone number on a public webpage, scrapers harvest it. It gets indexed, cached, and mirrored across dozens of databases. Robocaller lists buy it. Doxxers use it as proof. Your number is no longer yours to control—it belongs to the scraper ecosystem.
From there, the threats compound. A SIM-swap attacker doesn't need to guess your password—they call your carrier and convince someone you're you. A robocaller doesn't ask permission; they dial down lists of 10,000 numbers scraped from contact pages. And every service that touches that number—your carrier, your cloud provider, any support line—becomes a weak link.
The person who posted the number pays the cost. The person who dialed it got convenience. This asymmetry is the core problem.
Contact pages shouldn't ask you to sacrifice privacy
The contact page exists for a real reason: it creates a way for the right people to reach you. But the solution isn't more forms, CAPTCHA, or hoping people don't copy your number. The solution is rethinking what a contact page actually needs to do.
A contact page should:
- Let the right people reach you. No barriers for someone who genuinely wants to get in touch.
- Filter without surrendering data. Create friction for spam and scrapers—not through security questions, but by not publishing the attack surface in the first place.
- Give you control, not your carrier. Your contact flow should live on your page, not depend on a phone number indexed somewhere you can't see.
- Work on mobile. Most people messaging you are on their phones. The page should reflect that.
This isn't a feature list. It's a philosophy: what you choose not to do matters as much as what you do.
We don't ask you to publish your number. We don't harvest email addresses. We don't fingerprint users or log analytics to trace where visitors come from. We don't require a form that's longer than the actual message. We just let people reach you—directly, on your page, without giving scrapers a trail to follow.
You claim a Dingdong.tel page, customize it in under a minute, and share it. No setup, no landing page builder, no database to manage. People message you through it. You read the messages. That's the system.
How it works—and why it takes a minute
Claim your page at dingdong.tel/<yourname>. Pick a background color if you want one. Add a headline that says what you do. Done.
People who want to reach you go to your page, type a message, and hit send. No phone number. No email harvest. No form asking for their life story. Just a way in.
You get a notification, read it, and respond if you want. The person messaging you doesn't see your phone number or email. They don't get added to a mailing list. They don't get tracked. It's that simple.
The friction isn't in the design—it's in the intent. Real inquiry, quick to send. Spam, slower and less likely.
What's next
More is coming—verified pages for teams is next—but the broader thesis stands: the contact page is overdue for a redesign, and we're going to keep pushing it.