Docs / Safety and Guardian

Safety and Guardian

Orca builds Minecraft content and runs real servers from plain English, so safety is wired into every step instead of bolted on at the end. The AI only ever acts on servers you own, every file it touches is scanned before and after it reaches the build, and every finished build is signed so the desktop app can prove it came from Orca. This page walks through each layer: Guardian for AI actions, moderation for published content, and the scanning that runs on uploads and builds.

Orca is built for ages 12 to 19, which shapes the defaults. The AI refuses destructive or abusive requests, published content is moderated, and the rules for what you can make and share are spelled out in plain language. For the short version, see the Safety overview; the full policies live in the Acceptable Use Policy and the Children's Privacy page.

Guardian: the AI stays on a leash

Guardian is the layer that governs what Ask Orca, the AI server admin, is allowed to do. It cannot wander onto servers that are not yours, and it will not run a command just because you asked in frustration.

Every action is checked against three rules:

  • Scoped: the AI only acts on servers you own. It cannot reach anyone else's server, world, or files.
  • Screened: each action is checked before it runs, so a request that would wipe a world or harm other players gets stopped.
  • Logged: every action the AI takes is recorded, so you can see exactly what it did and when.
  • Refuses on principle: Guardian declines destructive or abusive requests instead of trying to be clever about them.

Content moderation on everything published

When you publish a mod, plugin, addon, or pack to the public gallery, it passes through content moderation before it can be found and downloaded by other people. The same applies to creator profiles and the SEO pages generated for each creation.

Anyone who finds something that breaks the rules can report it from the creation's page. What is and is not allowed is set out in the Acceptable Use Policy, which covers both what you make and how you behave on shared servers.

Scanning before and after the build

Files are checked at two points: when they come in and when a build goes out. This is true whether you upload your own .jar, .zip, .mcaddon, or .mcpack to remix, or the AI writes a fresh mod from scratch.

On the way in and on the way out:

  • Upload scanning runs before any file reaches the AI: it checks for zip-bombs, path traversal, and malware, so a poisoned upload never gets a chance to run.
  • Every build is scanned for malware and remote-code-execution risks, so a finished .jar cannot smuggle in something dangerous.
  • Each finished file is cryptographically signed by Orca, and the desktop app refuses to launch unsigned files, so what you download is provably the file Orca built.

Built for ages 12 to 19

Orca is made for younger creators, and the defaults reflect that. Refusals, moderation, and scanning are all on by default, not opt-in.

The two policies worth reading are the Children's Privacy page, which explains what data is collected and how it is handled, and the Acceptable Use Policy, which sets the ground rules for making and sharing. The Safety overview ties the whole picture together in one place.

Ready to build?

Start free

Related