WhatsApp Relay: how TNABoard members chat without exposing their phone numbers
WhatsApp is the fastest way for two people to arrange something. It is also the fastest way to hand a stranger a permanent link to your real identity. A phone number can be searched, saved, shared, and tied to a name, a face and an address. Once it has been given out, it cannot be taken back.
TNABoard is a community where that trade-off matters more than almost anywhere else. Members want the immediacy of WhatsApp. They do not want their number in someone else's contacts. The WhatsApp Relay, built on WAGate, is how the board gives them both. This post walks through how it works, what it protects against, and why it was designed the way it was.
What is TNABoard?
TNABoard is a community forum for independent escorts, providers and hobbyists, and it has been in operation since 2009. Members use it for open discussion, reviews and advertising, with verified providers, community guidelines and a dedicated support team behind it. Because the people on the board value discretion, member privacy shapes how it is built, and it is the reason the WhatsApp Relay exists. The board runs on WAGate every day. You can visit tnaboard.com to see the community for yourself.
The idea in one sentence
Every member talks to one board-owned WhatsApp number, and the board does the switching. You message the board, the board delivers it to the member you are talking to under your username, and their reply comes back to you the same way. Neither of you ever sees the other's number, because neither of you is ever messaging it.
Think of it as a switchboard operator who knows everyone by their screen name and never reads out a phone number.
Step one: proving your number without typing it
Most sites that verify a phone number ask you to type it into a form, then send you a code. That means your number passes through a web page, a form submission, a server log, and often a third-party SMS provider before it even reaches you. The relay turns this around.
When a member presses Link WhatsApp on the board, WhatsApp opens on their phone with a six-digit code already filled in and the board number as the recipient. They press send. The board sees the code arrive from a WhatsApp number, matches it to the pending request, and marks that number as verified. The page updates by itself.
This is sometimes called reverse OTP, and it has three privacy benefits:
- The number is never typed into the website. It arrives from WhatsApp itself, so there is no form field to be autofilled, logged or intercepted.
- It proves control, not just knowledge. Anyone can type a number they have seen somewhere. Only the person holding the phone can send a message from it.
- Codes are short-lived. A code expires after fifteen minutes and is single-use, and repeated failed attempts are rate-limited.
Even after linking, the member's own account page shows only a masked version of the number. The full number lives in one place, the board's database, and is used for exactly one thing: delivering relay messages to that member.
Step two: nobody gets a message they did not agree to
A verified number does not make a member reachable. It makes them able to be asked. The relay is consent-first at every point:
- A member finds someone they want to talk to: on their profile, on an ad, or through a share link the person has put in a signature. They press Chat on WhatsApp.
- The board sends the other member a request on WhatsApp. The request names only the requester's username.
- The recipient replies
#acceptor#decline. Until they accept, nothing is relayed. If they decline, the requester is told no more than that. - Either member can
#blockthe other at any time, from WhatsApp or from the site. A blocked member cannot send a new request and cannot see that they were blocked rather than declined.
Because every contact starts with a request and an acceptance, there is no equivalent of “someone got my number and started messaging me”. The relay simply has no path for an unaccepted message to reach a member.
Step three: the conversation itself
Once accepted, the two members chat normally. Each one messages the board number, and the board forwards the text, photo, or voice note to the other side, prefixed with the sender's username. Replies go to the person you last spoke to, so for a single conversation it feels like an ordinary chat.
When a member has several contacts, a few short commands keep things straight, all sent to the same board number:
@username your messageswitches to a different contact and sends in one step.#whoshows the current contact;#listshows all accepted contacts.#endcloses the current chat;#stoppauses all inbound relay messages until the member resumes.#block nameand#unblock namedo what they say, immediately.
Media follows the same rule as text. A photo is received by the board number and re-sent from the board number. The recipient's phone shows it as coming from the board, labelled with a username. WhatsApp attaches no sender metadata from the original phone, because as far as WhatsApp is concerned the board sent it.
What the other person can and cannot learn
| About you | Visible to a relay contact |
|---|---|
| Username | Yes |
| Phone number | No |
| WhatsApp profile name or photo | No |
| “Last seen” or online status | No |
| Read receipts | No |
| Whether you blocked or declined them | No |
The last two rows are worth pausing on. In a normal WhatsApp chat, blocking someone is visible: their messages stop getting double ticks and your profile photo disappears. Through the relay, a blocked member just hears nothing. There is nothing for them to react to.
Share links: reachable without being findable
Members who want to be contacted can generate a share link and place it in an ad, a signature or a profile. Anyone who opens it gets a button that starts a relay chat with that member. The link contains no phone number and no account identifier beyond what is already public, and the chat it starts still goes through the request-and-accept flow. A member can also show a small WhatsApp icon next to their name on the board; it links to their relay page, never to a number, and it can be hidden with a single untick.
Data that expires
A relay that nobody could moderate would quickly become a harassment tool. So relayed messages are logged, and staff can check a log when a member reports abuse. But the board treats that log as a liability, not an asset:
- Messages, commands and system replies are purged automatically after 90 days. Only messages that are still waiting to be delivered are kept longer.
- A member can delete their number at any time, which also ends every relay contact.
- Unknown numbers that message the board get one automated reply and are otherwise ignored, so the board does not accumulate a list of people who were simply curious.
The security underneath
Privacy features are only as good as the plumbing beneath them. The relay runs on a WAGate number, and the board's integration leans on WAGate's security model:
- Signed webhooks. Every inbound event WAGate delivers to the board carries an HMAC signature. The board rejects anything whose signature does not match, so nobody can forge an incoming message to impersonate another member or inject a command.
- One API key per number, rotatable. The board holds an API key, not the WhatsApp session. If the key is ever exposed it can be rotated from the WAGate panel in seconds without re-linking the phone.
- Session credentials encrypted at rest. The WhatsApp session that makes the board number work is stored encrypted inside WAGate.
- Permission-gated. Only user groups that have been granted relay access can use it. A banned or unconfirmed account cannot send through the relay even if it once verified a number.
- Paced and capped. WAGate sends with human-like pacing and the board can set a per-member daily cap. The relay is a conversation tool, and the limits make it useless as a broadcast tool.
Why TNABoard takes this so seriously
Privacy on TNABoard is not a feature bolted on at the end. It is the reason most of the board's custom tooling exists. Members of an adult-industry community face a specific set of risks: doxxing, stalking, blackmail, and the simple fact that a leaked number can end a career or a relationship. The board's design starts from the assumption that any piece of personal data it holds will eventually be requested, subpoenaed, leaked or scraped, and asks what happens then.
The answer, for the relay, is: not much. There is no table that maps usernames to numbers in a way other members can reach. The message log expires. Media is re-sent rather than forwarded. The same thinking shows up elsewhere on the board: WhatsApp-based login that needs no password to phish, notifications that name a sender but never carry the message, verification tiers that prove a member is real without publishing who they are, and billing through crypto so that no card number sits in a database.
The relay is the clearest example of that philosophy because it takes the most privacy-hostile channel available, WhatsApp, and makes it usable without anyone giving anything up.
A note on limits
No system removes every risk, and it would be dishonest to pretend otherwise. The relay stops your number from being exposed. It cannot stop a contact from screenshotting what you wrote, or from recognising you by what you say. It does not encrypt messages end-to-end between the two members, because the board has to see them to route them, which is also what makes moderation possible. Members who need total deniability should treat the relay the way they would treat any chat: say only what they would be comfortable having read back.
Within those limits, the relay does what it set out to do. On TNABoard, two members can go from a profile page to a live WhatsApp conversation in under a minute, and at the end of it neither has anything the other did not choose to give.
Build the same thing for your community
The relay talks to WAGate through the same REST API and signed webhooks every customer gets. Any XenForo, WordPress or custom site can do what TNABoard does.
Start free trial Read the TNABoard story