Privacy evidence and jurisdiction

Read the scope behind a no-logs claim.

Ask what data category, product, operator and period the evidence concerns. A policy, court filing and commissioned assessment answer different questions; a country group or corporate association is not a safety score.

Worked example: an audit is cited beside a billing question

You see a no-logs assessment and wonder whether it also examines account or payment records. Start with the actual scope rather than treating the assessor’s name as a blanket approval.

1. Identify the product and environment in the source. The Securitum Proton VPN 2025 report examines production VPN-server no-logs controls.
2. Read exclusions: that report excludes account/accounting systems, CI/CD, formal source review and binary analysis. An exclusion is a boundary on the finding, not proof that an excluded system failed.
3. Check provider policy statements for account/billing data separately. When reading a legal event, distinguish what was requested, what was supplied and whether the source is a company account or an inspected court filing.
4. Use operator, owner and infrastructure locations as separate context. Keep related-product events and historical ownership changes tied to their actual scope.

The useful result: Your conclusion is narrow enough to match the evidence. Unknown account, system or legal details stay unknown instead of becoming a privacy badge.

Proton VPN

Proton is a documented example here, not a recommendation for every task or a claim of endorsement. Image sources.

Check the fit.

• Which exact product and entity does this record concern?
• Which retained-data categories were examined or disclosed?
• What is explicitly excluded or still unestablished?

Keep the limits in view.

• An assessment samples a defined environment at a point in time. It does not guarantee every later system or all company products.
• No curated case file does not establish a clean history. A complaint is not a judicial certification of every assertion.
• StealthVPN organizes published evidence; we have not performed independent VPN security tests or a comprehensive legal/docket investigation.

Take the next useful step.

Read the underlying guidance.

• Securitum: Proton VPN assessment, scope and exclusions pp. 2–4 (opens in a new tab)
• Our investigation method

These paths organize source-based explanations. We have not carried out the example’s purchase, playback, connection or security tests. Our commercial directory has limited affiliate-program-based coverage. How this site is funded.