Your Phone Number is Everywhere
That's a privacy problem we're solving
That's a privacy problem we're solving
Why not for phone numbers too?
We already use proxy emails every day:
Widely accepted by services
Now you can have proxy phone numbers:
Same privacy, for phone numbers
Privacy-preserving phone verification through cryptographic proxy numbers
From phone verification to privacy protection in four steps
Prove phone ownership to a trusted issuer. This is the only time you share your real number.
Receive a unique proxy number that protects your actual phone number.
Get a cryptographic certificate proving you own a verified phone number.
Share your proxy number with any service. They verify it cryptographically.
Services verify your proxy number using the issuer's public key. No phone calls or SMS needed.
Services that need phone verification without the privacy liability
Signal, WhatsApp, Telegram
Verify users are real without collecting phone numbers. Even privacy-focused apps currently require real numbers. Hesha changes that.
eBay, Facebook Marketplace, Craigslist
Enable buyer-seller communication without exposing personal phone numbers. Reduce harassment and maintain user trust.
Tinder, Bumble, Hinge
Let users connect safely before sharing personal info. Verify real people without compromising privacy during early interactions.
Airbnb, Uber, TaskRabbit
Enable host-guest or driver-rider communication without exposing personal numbers. Protect both parties' privacy.
Discord, Steam, Twitch
Verify real users to prevent bots and spam without collecting personal data. Build trust in your community.
VPNs, Encrypted Email, Privacy Tools
Verify users without contradicting your privacy mission. Prevent abuse while respecting user anonymity.
Just add one check to your existing phone verification flow and start saving immediately
User provides either a regular phone number or a Hesha proxy number
Simple pattern check: does it contain "00" after country code?
if (number.matches("+*00*")) { /* Hesha */ }
Share your integration needs and use cases
No SMS gateway setup, no per-message fees, no delivery failures
User pays issuer once to verify their phone and get a proxy number
They provide proxy number + attestation when signing up
Check the JWT signature - that's it. No SMS needed.
Run an issuer node, verify phone numbers, and earn revenue
Issuers can charge for attestation services. Early partners will help define the business model and pricing structure.
If you already verify phone numbers, you can extend your service to issue privacy-preserving attestations.
Help protect user privacy worldwide. Be part of the decentralized identity revolution while building a profitable service.
Future possibilities and extensions for the Hesha protocol
A relay service that forwards SMS messages to your real number while preserving privacy. Apps send to your proxy, you receive on your real phone.
Protocol extensions for revoking compromised attestations and managing proxy lifecycle. Ensures users maintain control over their digital identity.
Use proxy numbers as human-readable Bitcoin addresses. Send crypto to phone numbers instead of complex wallet addresses.
Extend attestations to include verified attributes like age, residency, or KYC status while maintaining privacy.
Map proxy numbers to human-readable names across different platforms and services.
Use attestations as oracles for smart contracts, enabling phone-verified DeFi and governance.
Have an idea? We'd love to hear it!
Join the DiscussionIndustry-standard cryptography, no proprietary magic
Modern elliptic curve signatures for unforgeable attestations
Cryptographic hashing ensures phone numbers stay private
Standard token format for maximum compatibility
Memory-safe implementation for security-critical code
No, it's better. Burner numbers are temporary and tied to specific services. Hesha proxy numbers are permanent, cryptographically verifiable, and work everywhere.
Yes! That's the beauty of it. Services can cryptographically verify you own a real, verified phone number without ever seeing what that number is.
Services need to fetch the issuer's public key to verify attestations. Future versions will support key caching for better resilience.
Absolutely. You're not hiding from law enforcement or evading regulations. You're simply choosing what personal information to share, which is your right.
Hesha Protocol is in alpha. Help us make it better.