Transparency Report
See for
yourself.
How we operate, what we collect, and what we don’t.
The data boundary.
The collection disclosures in the published report. Read the full privacy policy for product scope and exceptions.
Data Collected
- Connection success/failure rates
- Route performance metrics
- Node health telemetry
- Censorship event detection
- Country-level statistics (aggregate)
Data NOT Collected
- Browsing history
- DNS queries (per-user)
- Real IP addresses (post-connection)
- Personally identifiable information via VPN or probes
- Card, bank, or billing-identity data (no card processor; the machine-facing voidpay rail records only self-generated wallet DIDs and public on-chain transaction hashes)
Note: Optional accounts (not required) may store an email address or wallet address you provide. No PII is collected through VPN connections or probe measurements.
The privacy policy also discloses an abuse-log exception for requests that trigger abuse heuristics. These statements do not mean every app contributes measurement data.
Published Data
Evidence you
can inspect.
Explore the underlying records, formats and methods.
- Country censorship scores and risk tiers
- Verified incident reports with evidence chains
- Platform and ISP blocking metrics (aggregated)
- Historical archive (10 years, 130+ countries)
- ML model performance metrics
Licensing and scope
The published report states: “All censorship intelligence is published as open data under CC BY 4.0.”
Use the data hub’s source and licensing details to distinguish Voidly’s original outputs from upstream materials with their own terms. A report in the dataset is not automatically a confirmed censorship finding.
A number needs a source.
Keep published snapshots, counters and current service checks distinct.
Reported figures / Sources and datesInspect the numbers
Network Stats
Data as of March 2026
The published report carries that date. Its fixed uptime and latency figures are reproduced below as report values, not a current service check. Counters and model snapshots have separate sources.
- Nodes
- Read the network source ↗The original configured node figure remains in the original report; it is not a live fleet count.
- Reported coverage
- Global (Europe, Americas, Asia, Oceania)Published report description; not a new coverage measurement.
- Reported uptime
- 99.8% (30d rolling)Original report value. Its “Data as of March 2026” label supplies no measurement source. Check current services.
- Reported average latency
- 47msOriginal report value under the March 2026 label; not verified as current.
- Countries monitored
- 130Bundled country-index coverage; not the number of countries contributing to every dataset.
- Network measurements
- 38,779,164Site counter: bundled OONI measurements plus available API updates. A corpus total, not a live-service check.
- Incident records
- UnavailableWaiting for a source response. Missing or invalid counts remain unavailable. The original report calls this total “Verified Incidents”; it also includes suspected and disruption records.
- Citable censorship records
- UnavailableThe source’s separate citable-censorship field; missing or inconsistent values remain unavailable. Inspect incident statistics.
- Censorship classifier
- 0.71 F1 (internal eval)LOCO mean across 127 countries — 0.63 on the 61 countries with n≥30. The 0.87 figure often quoted is the MEDIAN, inflated by 46 small-sample countries scoring a perfect 1.0. Snapshot generated 2026-09-25T21:43:25.326Z. Model source.
- Shutdown forecast
- 0.88 AUC (internal eval)LOCO median on the training holdout; live rolling-30d precision is 0.05 and /v1/sentinel/accuracy flags the model DEGRADED. Read the evaluation and dates.
Open Source / Published tools
Read the work.
Published tools, probe software, and specifications at: github.com/voidly-ai
Review published tools and methodology. Verify claims against our open data.
Privacy requires transparency. Trust requires verification.
Published code can have different license terms. Check the repository and Terms of Service.
Contact
- Security issues
- security@voidly.ai
- Privacy concerns
- privacy@voidly.ai
- General inquiries
- hello@voidly.ai