Governance

How we operate, who funds us, and what you can hold us to.

We work in domains — censorship measurement, election monitoring, defense communications — where independence and method are part of the product. This page documents the parts that a journalist, funder, partner, or user is entitled to know up front.

Independence

AI Analytics is operator-led and self-directed. We choose our targets, we choose our collaborators, and we publish what we've verified — regardless of who is asking. We do not accept work that conflicts with the open-data mission of Voidly. We do not place stories. We do not accept editorial input from funders, partners, or contracted customers on the censorship dataset.

The Swarm SDK serves a separate audience (vetted government and defense partners under a proprietary license). Revenue from that work funds the open-data work. The two workstreams have separate codebases, separate operators, and a documented firewall on data sharing.

Funding model

  • Self-funded operations baseline. Server, probe, and storage costs are covered by founder capital and Swarm SDK licensing.
  • No grant-conditional work. Where research grants are accepted, the dataset and methodology remain open and uncoupled from the funder's policy preferences.
  • No advertising, no surveillance monetization. The site does not run trackers, ad networks, or session-replay tools.

Ethics & method

  • Verifiable claims. Every public number cites a source — a live counter at voidly.ai, a GitHub README, or the linked writing post.
  • Cross-source verification. Censorship incidents are promoted to "verified" only after correlation against at least one independent project (OONI, CensoredPlanet, or IODA).
  • Anonymity by default for operators. Individual contributors don't publish under their own names. The work is the credibility signal.
  • No participation in offensive operations against civilian infrastructure, journalists, or human-rights defenders.

Data handling

  • Voidly measurement data. Probe results are published in aggregate under CC BY 4.0. No personally identifying information is collected from probe operators or end users.
  • Site analytics. No first-party analytics. No cookies set by application code. Cloudflare error reporting (NEL) is enabled at the edge for service health; no behavioral tracking.
  • Inquiry data. Email content is retained only as long as needed to respond. PGP-encrypted messages are decrypted on a single air-gapped device and not relayed.
  • Warrant canary. 0 warrants received as of last publication.

Conflict of interest

We disclose potential conflicts proactively. Where a writing post discusses a vendor or platform with which we have a commercial relationship, that relationship is stated at the top of the post. Where a probe is hosted by a sponsor (e.g., a research lab donating edge capacity), the sponsor is named on the methodology page.

Response SLAs

General inquiries
24–48 hours
Security disclosures
24 hours · acknowledgment
Press / journalist verification
24 hours business · 48h weekend
Government partner queries
Same business day

Security disclosure flow

  1. Encrypt your report with the PGP key at /pgp.asc (fingerprint listed at /contact).
  2. Email info@ai-analytics.org with a clear subject line and reproducible steps.
  3. Acknowledgment within 24 hours. Triage and remediation timeline within 5 business days.
  4. Coordinated disclosure preferred. We will credit reporters in the security acknowledgments page on request.
  5. Full policy at /.well-known/security.txt (RFC 9116).

This document is reviewed at least annually. Material changes are noted on this page and in the site's git history. Last reviewed: 2026-04-25.