Editorial standards
How these guides are made
Who writes the WaveTalk blog, how it is researched and checked, what we refuse to put in it, and how to tell us we got something wrong.
Who writes these
The WaveTalk team — the same small group that builds and runs the site. There is no outside content agency and no guest-post programme, and we do not accept paid placements or sponsored links in these guides.
That is worth stating plainly because it is also the limit of our expertise. We can write with real authority about how anonymous voice chat works technically, what a moderation queue actually looks like from the inside, and which safety advice holds up — because we built the relay, we read the reports, and we see what goes wrong. We are not psychologists, lawyers or doctors, and where a topic touches loneliness, mental health or the law, we say what we know and point you to people who know better.
How a guide gets written
Topics come from questions people actually ask — search queries, emails to [email protected], and the things that come up repeatedly in support. We do not pick topics because a keyword tool says they are easy.
Research and first drafts are AI-assisted. We think it is more honest to say so than to imply a newsroom we do not have. What that assistance does not do is decide what is true. Before anything is published, a person on the team reads it end to end and checks it, and nothing goes up that has not been through that.
In particular we verify, by hand, every time:
- Any claim about how WaveTalk works — against the code, not against what the last post said. Privacy claims are the ones that get checked hardest, because an approximation repeated often enough becomes a promise the software does not make.
- Any number. If we cannot source it, it comes out. We would rather a sentence be vaguer than invented.
- Anything said about another service. Described as a category where we have not used it ourselves, and never with a specific accusation we cannot stand behind.
What we will not publish
- Invented statistics. No "73% of users report…" unless there is a study behind it that we link.
- Privacy guarantees the code does not make. Our privacy page is the source of truth, and a blog post is never allowed to be more flattering than it.
- Scare tactics. Safety advice works when it is specific and calm. Frightening people into clicking is both worse writing and worse advice.
- Reviews of competitors we have not used.
- Medical or legal advice. We will explain what a law appears to say and link the source; we are not qualified to tell you what it means for you.
Our obvious conflict of interest
We run a voice chat site, and many of these guides end up recommending it. That is a real bias and we are not going to pretend otherwise.
What we hold ourselves to instead: the recommendation has to be earned by something specific and checkable — calls are relayed so the other person cannot see your IP, there is no account, nothing is recorded — rather than by talking the alternatives down. Where another kind of service genuinely suits you better, the guides say so. A comparison that always arrives at the same answer is an advert, and readers can tell.
WaveTalk is free to use and carries advertising. Advertisers have no involvement in what these guides say and no sight of them before they are published.
Corrections
We get things wrong. When we do, we fix the post rather than quietly deleting it, and the Updated date on the page changes so you can see it has moved.
If something here is wrong, email [email protected] with the page and what is wrong with it. Corrections about how WaveTalk itself works are the ones we most want to hear about, and they get fixed fastest.
Why posts get revisited
This subject moves. Sites close — Omegle did, in 2023 — laws change, and the product these guides describe changes too. A guide written once and left alone becomes wrong without anyone touching it.
So posts are revised in place rather than replaced by a near-identical new one at a new address, which is why you will see guides whose published and updated dates are months apart.