A contact-graph app you can actually trust.
Every contact-network app dies the same way: it leaks. Sometimes by accident, mostly by design. We built Rewinity backwards from that failure mode.
Our six promises
What we will never do.
No phone numbers in search.
Phone numbers are never displayed in search results — not to searchers, not to intermediaries, not to anyone. They unlock only after the target accepts the intro.
Hashed on your device.
Contacts are hashed with HMAC-SHA256 + a server-side pepper, on your device, before they ever reach our infrastructure. We cannot reverse them without exhaustive search on the pepper.
Per-contact consent, default off.
Every synced contact starts invisible. You explicitly toggle the ones you're comfortable bridging through. There are no dark patterns to flip the default.
No ads. Ever.
We make money from intros — a small fee when we connect you through the chain. We do not sell access to your graph for advertising. This is documented in our brand promise — and reflected in the absence of any ad tech.
One-tap revocation.
Pause your graph presence in one tap. Delete your account in one tap. Cascading delete completes within 60 seconds. Export your data as JSON before you go.
Honest limits.
We document what we can and cannot do — including lawful disclosure under valid legal process. We do not claim zero-knowledge contact matching today; stronger cryptographic approaches are on our roadmap.
Five gates between a search and a phone call
Walk the corridor. Every arch is owned by a different person. All five must be open.
Phone numbers never appear in search results. They unlock only after the target accepts — enforced in architecture, not just terms.
You set the radius
Choose how far you can be found.
A single setting controls the furthest someone can be from you and still see you in their search results — from direct contacts only, out to your whole network. Your direct contacts can always reach you, and beyond your limit you only ever appear as an anonymous link in a chain, never as a result.
Direct only
Only people who already have you in their contacts can surface you in search.
Friends of friends
Reachable through one trusted intermediary — the classic warm intro.
3 degrees
A little wider: friends of friends of friends, when you want more reach.
Whole network
Anyone who can reach you through the trust graph (up to five hops) can find you when you allow it.
Talk safely
Chat in-app first — then take it anywhere.
Once an intro is accepted, an in-app chat opens automatically — no phone number needed to start. It's real-time, with delivery and read receipts and image & document sharing.
In-app chat is always on — it can never be switched off, so every accepted intro has a private place to begin. Each conversation is a focused 50-message warm-up: enough to establish trust without becoming another inbox to manage.
When you're ready to go deeper, share a phone number, email or WhatsApp right inside the chat and continue on whichever channels you enabled — entirely on your terms.
Threat model
The people we built defenses against.
We took the time to write down who might abuse the platform — and how we'd stop them. Here's the short version.
Nosy user trying to find an ex
No name-based reverse search. Tag-only matching. Targets see aggregate match-counts weekly.
Cold-sales spammer
Rate limits per searcher. Declined intros count against rate. Category-level mute on the target side.
Scraper / data broker
Per-IP and per-user rate limits; authenticated API access; complexity caps on search.
Insider with DB read
Role-restricted production access, audit logging, and least-privilege policies. Pepper is not stored alongside hashes in a single trivial dump.
External hacker dumping the DB
Hashed contacts require the server pepper to attack at scale; TLS and access controls in depth; encrypted backups where configured.
Government data request
Legal review per request; minimum-necessary disclosure; documented in our privacy policy.
Future temptation: us, monetising contacts
Architecturally prevented — we don't store cleartext numbers usefully. Documented in privacy whitepaper.
The honest limits
What we can do, can't do, and won't do.
We can match your contacts to platform members because we hash both sides with the same function. That means — under subpoena — we could be asked to list the users matching a specific number. We document this. We do not pretend otherwise.
A fully zero-knowledge architecture using PSI (Private Set Intersection) or oblivious PRFs is on our roadmap. The cost overhead is significant; we will ship it when it clearly benefits users.
Until then, our privacy policy, DPDP page, and this section are the contract — updated as the product and law evolve.
Your network awaits
The people you need are already connected to you.
Download Rewinity — illuminate the golden threads in your graph. Consent at both ends. Rewards for everyone who bridges.
Phone-verified · Default-off discoverability · No ads