Skip to content
Decoded Signal

Testing standard

How we decode claims

Monitoring apps are sold on promises that are hard for a buyer to verify. Hands-on reviews use accounts and devices we control. Research guides use current primary sources and say plainly when no new product test was performed.

1 apps tested · 3 claims checked · methodology last updated Nov 2, 2026

The four steps behind a hands-on review

  1. Step 1

    We create or purchase the accounts

    Every test runs on accounts and devices we control — bought at retail, configured like a real household, never vendor-supplied.

  2. Step 2

    We test the advertised functionality

    We reproduce each marketing claim as written, on both platforms where relevant, and record exactly what appears.

  3. Step 3

    We document limitations and consent requirements

    Where a feature works only with consent, permissions or specific conditions, we say so — the conditions are the finding.

  4. Step 4

    We date every check and record meaningful changes

    Each article carries its last-checked date and an update history, so you know when the facts were current.

How source-based guides work

Some questions can be answered from current product pages, platform documentation and existing Decoded Signal findings. These articles name their sources, record the review date and avoid first-person test claims. Vendor features stay labelled as vendor claims until we reproduce them ourselves.

What each claim status means

  • Verified

    Reproduced during testing

  • Limited

    Works only under stated conditions

  • Unsupported

    Advertised but not demonstrated

  • Impossible

    Conflicts with platform or device privacy controls

A status applies to a specific claim under the conditions stated in the article — not to a product as a whole. When a vendor changes a feature, the status is re-tested and the article's update history records what changed.

Consent is part of the test

Parental controls, family locators and monitoring tools are tested exclusively in consent-based scenarios: our own accounts, devices we own, and participating testers who know exactly what is running. Legitimate location sharing and private-account access generally require consent, account approval or appropriate device permissions — when a product claims otherwise, that claim gets tested and, so far, has always failed.

We do not publish workarounds for platform privacy controls, and we flag products whose marketing encourages covert use of another adult's device.

Independence and corrections

We buy the subscriptions we test at retail and never accept payment for coverage or placement. Some outbound links earn affiliate commissions; they never change a claim status, a verdict or a ranking — see the affiliate disclosure. If you spot an error, tell us — corrections are logged in the affected article's update history.