Acceptable Use Policy
This policy keeps the ProofKit network safe and usable. It applies to everyone using the service, alongside the Terms of Service. Node operators also set rules for their own nodes.
01 /Legitimate use
Using ProofKit to circumvent censorship, evade surveillance, and protect your privacy is a legitimate and encouraged use of the service.
02 /Prohibited use
You must not use ProofKit to:
- Produce, store, or distribute child sexual abuse material (CSAM).
- Support terrorism or violent extremism.
- Evade applicable sanctions or export controls.
- Launch attacks — hacking, DDoS, port scanning, malware, or command-and-control.
- Send spam, run phishing, or commit fraud.
- Distribute other people's personal data without authorization.
- Do anything illegal in your jurisdiction or the operator's jurisdiction.
03 /Node rules
Operators choose some rules for their own nodes, and the Marketplace shows them as badges:
- No P2P (Torrent Guard): the node blocks BitTorrent traffic and known tracker ports and domains. On these nodes the platform also ends a session that has uploaded more than 30 GB and much more than it downloaded (by default, more than one and a half times as much) or that passes the node’s per-session data limit, and you can’t reconnect to that node for an hour. Turn on the P2P Allowed filter in the Marketplace to see nodes without it.
- WARP: the node sends your outgoing TCP traffic (most web browsing) through Cloudflare WARP, so sites see a Cloudflare address rather than the node’s.
- Invited: a private node that only people the operator invited can use.
Torrent Guard’s traffic detection doesn’t apply to the olcRTC transport. More in the help article on Torrent Guard.
04 /Enforcement
If you break these rules we may end your sessions or suspend your account; operators may also lose nodes or part of their stake. Where legally required, we cooperate with lawful requests; what our records can and cannot show is described in the Privacy Policy. We aim to act proportionately.
05 /Reporting abuse
Email [email protected] with the IP address involved, the date and time (with time zone) and what happened. For copyright, see the DMCA Policy.
06 /Changes
We may update this policy; the “Last updated” date will change.