Skip to main content

🔒 Data Security

Ludus reads your project so it can act with context, and it is built so you stay in control of what it changes and what leaves your machine. This page covers what Ludus accesses, the controls you have, and the platform's compliance posture.

What Ludus accesses​

To work with context, Ludus reads your project: Blueprints, C++ code, data structures, sounds, documents in the Docs folder, and actors embedded in level files. It uses this to target the right asset and fit your existing conventions. See Chat, Context & Attachments and Project Documents for what is included and how to manage it.

Controls you have​

  • Approvals: sensitive actions pause for your approval before they run, with separate prompts for generation, imports, and project commits. Nothing touches the project until you allow it. See Approvals & Safety.
  • Staged changes: edits are staged and applied in a single commit step with a plain-English summary you approve.
  • Source control: on login, Ludus warns you if no Git or Perforce is detected, so you always have a way to review and revert changes. See Quick Start.

Compliance​

Ludus is independently certified to ISO/IEC 27001:2022 and SOC 2 Type 2, and is fully GDPR compliant.

Full isolation for studios​

Studios that require data sovereignty can deploy Ludus on a private cloud, where all processing and storage happen inside their own infrastructure and Ludus has no access to their project data, code, or assets. See the Enterprise Plan (Private Cloud).