EMBARGO PROTOCOL / NAC–D / STANDING LIMITS

Publication limits and coordinated disclosure

A defensive lab can cause offensive harm by oversharing. These are the standing limits, published before the evidence they govern so a later finding cannot quietly weaken them.

RELEASE SCREEN / PERMANENT EXCLUSIONS

EMBARGO

What never publishes

HOLD–01
Exact detection thresholds or parameter values with evasion value — findings group sensitive checks into families instead.
HOLD–02
Bypass recipes, evasion payloads, weaponizable fixtures, or cheat-client evaluations.
HOLD–03
Proprietary JARs, paid configurations, or anything the license does not permit redistributing.
HOLD–04
Player data of any kind: no UUIDs, IPs, chat, or moderation evidence — fixtures use synthetic identities.

Maintainer notice

A material regression or safety-relevant weakness in a maintained project goes to its maintainers before it goes on a page: private notice, reproduction manifest included, a reasonable embargo, and their response published verbatim (within length limits) beside the finding. Vendors are participants with correction rights, not targets.

PRIVATE CONTACT ROUTE / DOMAIN EMAIL

Send sensitive reports privately

Send a concise description and a safe reproduction outline tocontact@noanticheat.com. Do not attach credentials, private player data, proprietary artifacts, or weaponizable material to ordinary email. The public page records a disclosure only after the safety and maintainer-notice conditions above are satisfied.