Loading...

Methodology

How we research VPN products

A transparent process that separates our documented checks from independent audits, public benchmarks, user reports, and provider claims.

THE PRINCIPLE

We label the evidence behind every claim

VPNVertex does not present desk research as hands-on testing. When we run a check ourselves, we record the date, device, operating system, app version, protocol, settings, and test conditions. If those details are missing, the article relies on attributed external evidence.

Our evidence rule

No article is marked “Hands-on tested by VPNVertex” until its evidence file passes our publication checklist.

THE PROCESS

From claim to verdict

1

Define the use case

Privacy, streaming, travel, gaming, and business needs are scored against different priorities.

2

Record our checks

When hands-on evidence is available, we keep the device, software version, settings, baseline, conditions, raw results, and original screenshots.

3

Collect primary evidence

We review official documentation, pricing, policies, transparency reports, and attributed audits.

4

Cross-check the record

Independent benchmarks and recurring user reports are compared for consistency, recency, and stated conditions.

5

Apply the rubric

Security, privacy, performance, usability, streaming, value, and transparency are weighted for the use case.

6

Recheck and disclose

Prices, claims, conflicts, affiliate status, and important limitations are checked before publication.

SOURCE HIERARCHY

What carries the most weight

A

Direct and primary

Dated VPNVertex test records when available, attributed audits, court records, official policies, and technical documentation.

B

Independent

Established test labs and reviewers with clear methods and conditions.

C

Observed patterns

Aggregated user reports, weighed by recency, relevance, and sample size.

D

Provider claims

Useful for specifications, but never sufficient alone for a verdict.

LIMITS

What we do, and what we do not

We do

  • Label our tests with their date, device, software version, settings, and conditions
  • Keep raw measurements and original screenshots
  • Separate our checks from independent benchmarks
  • Verify current pricing and renewal language

We do not

  • Claim tests we did not perform
  • Use provider-supplied images as proof of our tests
  • Guarantee anonymity or universal streaming access
  • Hide material affiliate relationships

CORRECTIONS

Challenge our work

Found a sourcing problem or an outdated claim? Send the page URL, the specific sentence, and your supporting source. We aim to review substantive corrections within five business days.

Submit a correction