SAFETY POLICY / EFFECTIVE JULY 15, 2026
Protect the player. Preserve the evidence.
These rules govern real Patchloop accounts, builds, playtests, release rooms, reports, and enforcement. Patchloop is a focused playtest service, not an unrestricted download board.
Patchloop enforces approved access classes, public HTTPS destination checks, direct-binary rejection, scoped messages, and rate limits. Signed-in rooms include private report, leave, and block controls; Settings preserves report and block history without erasing the underlying case record.
OUR COMMITMENTS
Build and link safety
Creators must accurately describe the immutable build, platform, access method, expected playtime, account or install requirements, permissions, and content warnings. A changed host, URL, build version, or signing identity requires a new reviewable build record.
Access is limited to approved browser builds, canonical managed-beta links, and vetted platform pages. External distribution reduces ad-hoc risk, but it is never described as a malware guarantee.
- Patchloop does not host arbitrary executables, APKs, DMGs, ZIPs, or raw release assets.
- No shortened links, raw IP hosts, credential harvesting, deceptive redirects, or instructions to disable antivirus or OS protections.
- A downloadable mission must show its publisher, exact version, supported OS, size, requested permissions, and uninstall steps before reservation.
- Suspected malware or phishing should be reported from the relevant release room so the build and message context stay attached.
Reporting and urgent risk
Signed-in participants can submit a private report from a shared release room, leave that room, or block the collaborator. These actions preserve the report detail and relevant thread and build identifiers while stopping future access where appropriate.
Patchloop is not an emergency service. If anyone is in immediate danger, contact local emergency services first.
- Report categories include malware or phishing; broken or misleading builds; harassment; privacy leaks; fake play or collusion; unlabelled content; copyright; and confidential-build leaks.
- Blocking prevents future matching and communication without a reputation penalty while authorized participants retain their own permanent work history.
Enforcement and review
An authorized steward can move a report through reviewing to a documented resolution, quarantine an affected immutable build, or suspend an account. Suspension immediately revokes browser and realtime sessions; reinstatement is a separate audited decision and requires a fresh Discord sign-in.
Safety records preserve the evidence category, operator action, substantive note, actor, target, and sequence without exposing private report detail to unrelated users.
- Negative feedback and respectful disagreement are never safety violations.
- Creators cannot reduce or withhold the quoted Signal reward because a report is critical or not actionable.
Eligibility and contact
Patchloop accounts are for adults age 18 and older.
Use the report, leave, and block controls inside the relevant release room. Include the mission, room, message, or build identifier whenever possible so the record can be reviewed in context.