Editorial & authorship

Who writes these

Articles are written and maintained by Robert Mical, who edits Vobo. His account of how the site started, how an article gets written, and what he refuses to claim to know is on his page.

A byline is only worth anything if it is real, so it is worth being precise about what it does and does not assert. It does not claim insider knowledge: nobody here has worked at WhatsApp or Meta, and the site has no relationship with either company. It claims responsibility — that a named person checked the steps, chose the sources, and can be written to when something is wrong.

Where an article contains a first-person note, it describes work actually done: a menu path walked on a real handset, a figure we could not verify, a claim found repeated everywhere and traced back to nothing. It is never a story about a life nobody lived.

What expertise stands behind the articles

Honestly stated: Vobo is a research-and-writing operation, not a laboratory and not an insider. Its competence is in reading primary documentation carefully, testing what can be tested on ordinary consumer devices, and being disciplined about the difference between the two. That is a real skill and it is also a limited one, and the limit is worth being explicit about.

What we can genuinely claim

• Close reading of WhatsApp's own help centre, privacy policy, terms and published security documentation, including tracking when their wording changes.
• Hands-on verification of interface steps on current iOS and Android builds, which is how menu paths in these articles are checked before publication.
• Tracing widely repeated claims back to their origin, and reporting when that origin turns out to be nothing more than another blog post.
• Reading the technical literature on the underlying cryptography closely enough to represent it accurately and to know where a summary would overstate it.

What we cannot claim

• Any view inside WhatsApp's servers, code or internal policy. We know what is documented and what is observable, and nothing else.
• Independent cryptanalysis. Where this site describes the security of the underlying protocol, it is reporting peer-reviewed work by others and citing it, not conducting an analysis of its own.
• Knowledge of your specific account, device or situation. Nothing here is an assessment of whether you in particular have been compromised.
• Region-by-region completeness. Features roll out unevenly, and an article can be right in one country and premature in another. Where we know that is the case, we say so.

How a claim gets onto the site

• Start from the question. Article topics come from search demand — the actual phrasing people use — rather than from what would be interesting to write.
• Find the primary source. Behavioural claims are checked against WhatsApp’s own documentation; corporate facts against Meta’s filings and announcements; adoption figures against published research such as Pew Research Center and the Reuters Institute.
• Test what is testable. Step-by-step instructions are walked through on a current device before publication, not transcribed from a help page.
• Check every link. Every cited URL is requested before publication and must resolve. Papers are verified through the Crossref API by DOI, so a citation cannot silently point at a journal homepage instead of the paper.
• State the uncertainty. If a question cannot be answered reliably from outside, the article says that in the short answer, not in a footnote.

Across 35 articles the site cites 36 distinct external sources, each listed at the foot of the article it supports with a line naming the specific claim it backs up. If a source does not support a specific claim, it does not get listed — a bibliography of impressive-looking links that nobody used is decoration, not evidence.

Corrections policy

Corrections are made on the article itself and the updated date changes. Where a correction changes the substance of the answer rather than a detail, the article says what changed. We do not quietly rewrite a page to pretend it always said the right thing.

Report an error to contact@vobo.online with the URL and, if you can, what your screen shows. Corrections take priority over everything else in the mailbox.

Independence and funding

Vobo has no relationship with WhatsApp LLC or Meta Platforms, Inc. Nothing published here is reviewed by, approved by, or supplied by either company. The site is funded by automated advertising, which is selected by Google and has no bearing on editorial decisions. No article is written in exchange for payment, and no third party sees a draft before it is published.

The full statement of what this site is and is not — including what it cannot do for you — is on the disclaimer page, and the way the site is built and researched is described on the about page.