Which WhatsApp monitoring software is legal for a business?

Search this and you mostly get stalkerware

Type “WhatsApp monitoring software” into a search engine and the first page is largely one product category wearing a business costume.

These are apps installed onto a handset. To read an encrypted messaging app from the inside they need root access on Android or a jailbreak on iOS, which lets them hook into core operating system services and watch everything running there.

What they capture is not limited to WhatsApp, because it was never designed to be. Keystroke logs, screenshots, intercepted text messages and recorded calls are the standard feature set. The messaging app is one row in a long list.

They are also built to stay unnoticed by the person holding the phone. Security vendors classify this category as stalkerware for exactly that reason, and it is the reason the category does not belong anywhere near a sales team.

Why that is not a business tool

Three separate problems, any one of which is disqualifying.

The first is ownership. Installing a monitoring app on a phone you do not own, without the owner’s agreement, is not a grey area in most of the United States. It is the conduct the computer-misuse and wiretapping statutes were written about.

The second is scope. An app with root access on a rep’s personal handset reads their banking app, their photos, their family group chats and their location. A business has no legitimate interest in any of it, and having collected it you now have to protect it.

The third is that it does not answer a business question. You wanted to know whether customers are being answered. What you bought was a general-purpose reader of one person’s entire digital life, which is a different thing that happens to include the answer.

The line that actually matters

Two questions decide whether a monitoring approach is defensible, and neither is about features.

Whose device is it? A company-owned number, on company-owned equipment, used for company business is your asset to keep records of. A rep’s personal phone is not, and no amount of policy language makes it so.

Who was told, and when? Notice before the fact is what separates record-keeping from something else. Several states require it in writing: New York’s Civil Rights Law § 52-c-2 requires written or electronic notice acknowledged by the employee, plus a posted notice, with civil penalties of up to $500 for a first offense, $1,000 for a second and $3,000 after that, enforced by the attorney general. Connecticut’s § 31-48d requires prior written notice of the types of monitoring that may occur, with the same 3 penalty tiers levied by the Labor Commissioner.

Get those 2 right and the legal question mostly resolves itself. Get either wrong and no product choice rescues it.

What a linked companion device does instead

The mechanism is the one you already use when you open WhatsApp on a laptop.

A company number is linked as a companion device by scanning a QR code from the dashboard. That takes about a minute per number. Nothing is installed on anyone’s phone, because nothing needs to be: the archive is a device on the account, not an app inside the handset.

From there, messages on that number are written to an append-only archive as they arrive. Deleted and edited messages arrive as new events with both timestamps rather than overwriting the original.

What it does not reach is the rest of the phone. No camera, no location, no other app, no ordinary phone calls. Call events on the linked number record direction, whether they connected and how long they lasted, with no audio and no transcript.

And it cannot send from a linked number. There is no send path on one at all, which is a design decision rather than a switch someone could flip. An observer that could also speak as your rep would be a different and worse product.

Visible by design, including to the team

The uncomfortable half of this is the half that makes it work.

Reps are told the archive exists before their number is linked. That is not a courtesy, it is the thing that distinguishes this from the category at the top of this page.

Every read of the archive is recorded. Opening a conversation, running a search, viewing an attachment and downloading an export are each written to an access log before the data appears on screen, and no row can be edited, deleted or turned off. Access records are kept for 3 years.

The log is read by your workspace owner and any auditor the company brings in. Reps do not read it themselves, and it would be wrong to imply otherwise. What they are given instead is a plain account of what is and is not captured, which is what the for employees page is for.

Where this is the wrong choice

If your team sells on personal WhatsApp accounts, there is no version of this that is appropriate. The honest fix is to move the selling onto company numbers first, which is a management change rather than a purchase.

If you are a regulated broker-dealer or investment adviser, this is not the right product. WAOversight is not FINRA or SEC-grade archiving, and Smarsh and its peers are built for that obligation.

If what you actually want is to know what one specific person is doing all day, this product will disappoint you, and that is deliberate.

What to do about it

Decide the ownership question before you shop. If the numbers are not company-owned, no tool on the market makes the rest of this lawful.

Then write the notice and get it acknowledged, before anything is linked. The security page covers where the data sits, who can reach it and how long it is kept, and the demo shows the archive against sample data if you would rather look before committing a real number.