Research Archive

Evidence Classification Methodology

A documented, repeatable method for compiling and classifying records on commercial spyware — so every finding is independently checkable and the archive's own analysis is never confused with the evidence it rests on.

Purpose

What this archive is

The Spyphone Research Archive is an original, evidence-classified reference on commercial mobile spyware and the surveillance industry. Each record is a structured, citation-ready entry built from primary documents wherever they exist. The archive exists to give researchers, journalists, and compliance professionals a single place where a finding, its evidence status, its sources, and its attribution are all visible on the same page — and where the archive's own analysis is clearly separated from the quoted or summarised material it interprets.

Who compiles the records

Records are compiled by the Spyphone Research Archive editorial team at RedSec LTD. The team identifies primary sources, extracts the factual record, drafts the archive's own analysis, and assigns an evidence classification. Every record carries a named author or editor and a credential. The archive does not conduct its own forensic laboratory testing; where a finding rests on technical forensics, it is attributed to the laboratory that performed the work, not to this archive.

Evidence status taxonomy

Every record carries one evidence status. The status describes the strength of the support, not the seriousness of the underlying conduct.

Verified

The finding is established by a primary source of the highest authority — a court judgment, a peer-reviewed forensic lab report, or a vendor security advisory — and the underlying primary document is linked and checkable.

Partially Verified

Core elements are supported by primary sources, but one or more specifics (e.g. attribution of an operator, a victim identity, or an exploit chain detail) rest on secondary reporting or inference and are marked as such.

Alleged

The finding is reported by a credible source but has not been independently confirmed by a primary authority. The reporting party is named; the claim is presented as an allegation, not as established fact.

Disputed

Material evidence exists but a named party contests the finding, or competing accounts conflict. The dispute and each party's position are documented.

Retracted

A prior finding has been withdrawn by its original source or superseded by a later primary record. The original claim and the retraction are both preserved.

Evidence classes

Court record

Judgments, indictments, filings, and transcripts from a recognised court or tribunal.

Forensic lab finding

Technical analysis published by an accredited forensic laboratory (e.g. Citizen Lab, Amnesty Security Lab, Google TAG, Microsoft MSTIC).

Vendor advisory

A security patch, threat report, or bulletin issued by the platform vendor (Apple, Google, Meta, Microsoft).

Government record

Sanctions designations, export-control filings, parliamentary or regulatory reports, and official statements.

News report

Reporting from an established news organisation. Treated as secondary unless corroborated by a primary source.

Academic research

Peer-reviewed or university-affiliated scholarly publication.

How records are verified
  1. Locate the primary document. For each factual claim, the team first seeks the highest-authority primary source — the court filing, the forensic report, the vendor advisory, the sanctions designation.
  2. Link it directly. The primary document is linked in the record's source list. Where a source is paywalled or removed, the original publication and an archived copy are cited.
  3. Cross-reference. A claim that rests on a single news report is marked Alleged until a primary source corroborates it. Two independent primary sources move a claim toward Verified.
  4. Classify. The evidence status and evidence class are assigned from the strongest available source, not the most recent.
  5. Separate analysis. The archive's interpretation is written in a distinct, labelled section and never presented as part of the quoted record.
Attribution policy

Attribution is precise. The phrase "Spyphone Research Archive analysis" is used only for findings this archive produced by interpreting the underlying record. Forensic findings are attributed to the laboratory that performed them. Court decisions are attributed to the court that issued them. Allegations are attributed to the reporting organisation or the party making them. No finding is presented as this archive's own unless the archive itself produced the synthesis.

Update cadence

Each record carries a last-verified date. Records are reviewed when a material primary source is published — a new court filing, a vendor patch, a fresh forensic report — and the last-verified date is updated only after the team has re-checked every linked source. Records that have not been re-verified in 12 months are flagged for review. The archive does not silently edit the factual record; substantive changes are logged in the correction history.

What the data cannot establish
  • The archive cannot establish the full operational footprint of any spyware product. Deployment records are, by design, not public; the archive records what has been documented, not what may exist undocumented.
  • The archive cannot attribute an operator to a government beyond what a primary source (a court, a forensic lab, or a sanctions designation) has established. Inference about state sponsorship is labelled as this archive's analysis, not as fact.
  • The archive cannot confirm victim identities where the reporting source has anonymised them. Anonymised victims are referenced by the descriptor used by the original source.
  • The archive does not reproduce exploit code or operational technical detail that could enable replication. Technical findings are summarised at the level published in the cited source.
Correction history

Every record maintains a visible correction history. A correction is logged whenever a factual statement is changed after publication — the date and the nature of the change. A record's evidence status can be revised downward (e.g. Verified to Disputed) when a contesting primary source emerges, and upward when a primary source resolves a prior dispute. The original claim is preserved in the correction entry so the record's evolution is auditable.

Legal Notice

Authorized Use Only — Lawful Monitoring Required

SpyPhone hardware-modified devices are sold exclusively to vetted corporate, investigative, and compliance professionals for lawful monitoring of devices the purchaser is legally authorized to monitor. Use requires legal authority under the applicable jurisdiction. We do not sell for stalking, unlawful interception, or surveillance without consent where required by law. Every request is reviewed before procurement, and all sales are conditional on acceptance of our Legal Notice.