How We Test

Last updated: July 20, 2026

VeilNorth reviews are designed to explain what a product does, what it does not do, and who may benefit from it. Testing methods vary by product category, but the principles below remain consistent.

What we examine

• Privacy: data collection, account requirements, default settings, tracking, retention, jurisdiction, and policy clarity.
• Security: encryption design, authentication, update practices, known limitations, audit history, and incident response where documented.
• Usability: installation, everyday workflows, accessibility, support, and how clearly the product explains important choices.
• Performance: practical speed, reliability, resource use, and compatibility where relevant.
• Transparency: ownership, documentation, open-source availability, independent audits, and communication about changes.
• Value: price, free-tier limits, refund terms, feature restrictions, and credible alternatives.

Testing approach

Where feasible, we install and use the product on supported platforms, inspect settings and network-facing behaviour, compare published claims with documentation, and reproduce important user workflows. We distinguish direct observation from vendor claims and from third-party findings.

Ratings

Ratings summarise a product at the time of review. They are editorial judgments, not mathematical guarantees. A product can score highly overall while remaining unsuitable for high-risk users or a specialised threat model.

Limitations

VeilNorth is not a penetration-testing laboratory. Unless an article explicitly says otherwise, a review should not be interpreted as a full security audit. Products, prices, policies, and ownership can change after publication.

Commercial relationships

Affiliate availability is not a testing criterion. We may review products that do not pay commissions and criticise products with which a commercial relationship exists.