Scope and consent

Your team gets the report. The player agrees first.

See what the report says and what the player agrees to, in one place.

Where MYTHOS stops

What it does and what it doesn’t.

It doesn’t scan without consent. But if the program detects tampering or a crash, it can send a short notice before consent. The notice identifies the PC and its accounts, and the privacy draft explains this.
Doesn’t kick or ban anyone.
Doesn’t show the player the result.
Doesn’t decide what to do for you.

The player’s consent

Before the scan, the player sees an agreement that says what is collected and who it is shared with. Without Accept, no scan runs.

MYTHOS Sample interface with demo data

Examples of what the scan looks at

Manual check and report

Manual check compared with a MYTHOS report
	Manual check	MYTHOS report
Scope	The check covers only where the staff member happens to look.	The same checks run for every player, who sees the agreement before the scan.
Record	What’s seen ends up scattered across chat, screenshots and memory.	Findings stay in one report, with their time and context.
Team	The review rests on how the person who ran the check tells it.	The report stays in the dashboard, and the review rests on the same record.
Limits	What wasn’t checked, or can’t be shown, usually goes unwritten.	Context findings say they aren’t evidence of cheating on their own.

Next step

Let’s talk about how MYTHOS could fit your team’s review process.

Player consent is required, and your team decides on any sanction.