Terms of Service

Agreement

These terms govern your use of the Cerberus Anti-Cheat SDK, API, dashboard, and related services ("Cerberus" or "the Service"). By integrating the SDK or accessing the API, you agree to these terms. If you're integrating Cerberus on behalf of a game studio, you confirm you have authority to bind that organization.

Cerberus is currently in closed beta. These terms will be updated as we approach general availability.

SDK license

We grant you a non-exclusive, royalty-free, revocable license to:

• Integrate the Cerberus SDK into your game or application
• Distribute the SDK runtime components (static library, driver) as part of your game's installation
• Use the REST API and webhook system to manage detections programmatically
• Access detection data through the partner dashboard

The license is permissive for integration purposes. You don't need to open-source your game, attribute Cerberus in your UI (though we appreciate it), or pay royalties on the free tier. Paid tier terms are specified in your partner agreement.

What you can't do

• Reverse engineer, decompile, or disassemble the SDK, driver, or detection algorithms
• Redistribute the SDK as a standalone product or include it in competing anti-cheat solutions
• Modify the kernel driver binary or attempt to bypass its code-signing verification
• Use the SDK to collect data about players beyond what's necessary for cheat detection

Acceptable use

Cerberus is designed for protecting competitive multiplayer games. You agree to:

• Use Cerberus only for cheat detection and game integrity purposes
• Not weaponize detection data against players for reasons unrelated to cheating
• Implement a ban appeal process for your players (we provide the API -- you provide the player-facing flow)
• Not use Cerberus to monitor players outside of active game sessions
• Comply with applicable privacy laws in your jurisdiction when handling detection results

Detection accuracy disclaimers

Specifically:

• Detection is not guaranteed. New or sophisticated cheats may evade detection temporarily. We continuously update our models and signatures, but there is no claim of 100% detection coverage.
• False positives can occur. Unusual hardware configurations, accessibility software, or certain system tools may occasionally trigger false flags. Detections below 95% confidence are sent to manual review, not auto-banned.
• Confidence scores are probabilistic. A 0.98 confidence score means we are 98% certain, not 100%. We recommend game studios use auto-ban only for high-confidence detections and review lower-confidence flags manually.

We provide detection data and confidence scores. The decision to ban a player is ultimately yours. Cerberus offers tools and recommendations, but game studios are responsible for their enforcement policies.

Ban appeal process

We take false positives seriously. The appeal process works as follows:

1. Players submit an appeal through your game's support channel (or directly via the API at POST /api/v2/bans/{id}/appeal)
2. Our threat analyst team reviews the full detection evidence package
3. Reviews are completed within the SLA for your tier (4 hours for Cerberus tier, 24 hours for Aegis tier, 72 hours for Argus tier)
4. If the ban is overturned, all associated detection data is flagged as a false positive and used to improve our models

Game studios can also overturn bans independently through the partner dashboard or API without going through our review process.

Warranty disclaimer

Cerberus is provided "AS-IS" during the beta period. We make no warranties, express or implied, including but not limited to:

• Fitness for a particular purpose
• Uninterrupted or error-free operation
• Compatibility with all hardware configurations
• Accuracy or completeness of detection results
• That the kernel driver will not cause system instability on edge-case hardware

We're building in public and iterating fast. The beta label is honest -- things may break, APIs may change, and detection accuracy will improve over time. We'll communicate breaking changes through the changelog with reasonable notice.

Limitation of liability

To the maximum extent permitted by law, the Cerberus team is not liable for:

• Damages arising from false positive detections or incorrect bans
• Revenue loss due to service outages or detection failures
• Player community backlash resulting from anti-cheat enforcement decisions
• System instability caused by driver conflicts on unsupported hardware
• Indirect, incidental, or consequential damages of any kind

Our total liability for any claim related to the Service is limited to the amount you paid us in the 12 months preceding the claim (or $0 if you're on the free Argus tier).

Intellectual property

Our IP: The Cerberus SDK, driver, detection algorithms, AI models, API, and dashboard are our intellectual property. Your license to use them is governed by the SDK License section above.

Your IP: Your game, code, assets, and player data remain yours. Integrating Cerberus does not grant us any rights to your intellectual property.

Detection data: Detection events generated by Cerberus are jointly useful -- you have full access to query, export, and delete detection data for your game. We retain anonymized, aggregated detection statistics (no game-specific data) to improve our models.

Data ownership

You own your player relationships and any identity mapping you maintain. We own the detection intelligence (models, signatures, heuristics). Detection event data is accessible to both parties during the retention period. See our Privacy Policy for full details on data handling.

Termination

Either party can terminate this agreement at any time:

• You can stop using Cerberus by removing the SDK from your game and revoking your API key through the dashboard. We'll delete your detection data according to our standard retention schedule (or immediately upon request).
• We may suspend or terminate your access if you violate these terms, use Cerberus for purposes other than game integrity, or if we determine your integration poses a security risk.

On termination, your license to use the SDK ends immediately. Any bans already issued through your integration remain your responsibility to manage.

Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to conflict of law principles. Any disputes will be resolved through binding arbitration under the rules of the American Arbitration Association, conducted in English. You agree to attempt informal resolution by contacting us before initiating arbitration.

Changes to these terms

We may update these terms as Cerberus evolves. Material changes will be communicated to partner studios via email and posted on our changelog at least 30 days before taking effect. Continued use of Cerberus after changes take effect constitutes acceptance of the updated terms.

Contact

Questions about these terms? Reach out:

General: hello@arsenalrx.dev

Privacy-specific: privacy@arsenalrx.dev