Trust and Safety

Raksha Fair Play and Safety

Raksha is built around server authority, deterministic matches, protected bot execution, public moderation rules, and report paths for abuse.

Last Updated: May 6, 2026

Server-Authoritative Gameplay

Raksha clients show controls, guidance, board state, and public records, but they do not decide match outcomes. Authoritative match flow, duel resolution, ranked results, Watch eligibility, bot execution, and persistence-critical records are handled by Raksha server systems.

This matters because a player interface should never be able to rewrite movement legality, hidden match data, rating movement, bot results, or replay truth.

Deterministic Engine and Replay Fairness

Raksha duels and replayable match events are deterministic. The same authoritative inputs, seed, and action history should reproduce the same outcome for Watch and replay review.

Finished ranked replays are rebuilt from authoritative final battle state and recorded action history. Diagnostic records can help recovery, but they do not become gameplay authority.

Bot Sandboxing and Deterministic Bots

Programmable bots are stateless per turn and must make deterministic decisions from the provided game state. Bot execution must not use Math.random, time-based decisions, network APIs, filesystem access, external APIs, imports, browser globals, dynamic code execution, malware, credential capture, or attempts to bypass runtime restrictions.

When bot execution fails or a bot cannot produce a valid action, Raksha keeps deterministic fallback behavior so the match can remain bounded and reviewable.

Ranked Protections and Anti-Collusion

Ranked PvP and ranked Arena Duel are protected competitive surfaces. Raksha may apply matchmaking protections, rematch limits, ownership checks, integrity checks, and rating corrections at a high level to protect the ladder from manipulation.

Do not farm ratings through abusive coordination, collude to trade outcomes, exploit alternate accounts, intentionally corrupt matches, bypass matchmaking rules, or use automation to distort public ladders.

Player Conduct Rules

You must not use Raksha to:

cheat, exploit bugs, tamper with match data, or hide abuse;
harass, threaten, demean, or target other people;
impersonate another player, creator, brand, or operator;
submit malware, spam, scams, credential requests, or unsafe links;
bypass account, bot, sandbox, ranked, token, or moderation rules;
submit public bot/profile content that is hateful, abusive, sexual, infringing, or deceptive.

Public Bot and Profile Content Safety

Public usernames, bot names, bot lore, bot metadata, profile presentation, community submissions, and bug reports are user content. They must follow the user content rules and may be hidden, rejected, corrected, retired, or removed when needed for safety, fairness, moderation, or service integrity.

Public bot/profile pages are noindex by default while Raksha keeps moderation and content-depth requirements conservative.

Reporting Abuse

Report unsafe content, abuse, impersonation, harassment, suspected collusion, exploit reports, unsafe bot metadata, or attempts to bypass bot restrictions through the Contact page or by emailing raksha.game.studios@gmail.com.

Include a profile link, bot id, match id, replay link, screenshot, or reproduction steps when available.

Children and Age Guidance

Raksha is not intended to be directed to young children without guardian involvement. Review the Terms of Service and Privacy Policy for account, privacy, public content, and age guidance.