Closed beta · run Worlds on your machineBrowse worlds →
Docs menu · Security and data

Security and data

Worlds runs on your laptop, in your CI, or on a private server you control. Customer records, prompts, test results and evidence stay with you. Grading reads the world's own database, so no model has to see your data to score a run.

What reaches Sparta, and when

Activity What reaches Sparta
Unrecorded local and CI runs Nothing.
Recorded runs and AI drafting (billable) A billing record: opaque organization, operation and installation IDs, the activity type, bounded counts and durations, outcome and credit amounts. Never prompts, records, commands, paths, credentials, diffs or evidence.
Aggregate usage reporting (optional) Bounded counts and outcome categories, with random installation and project IDs. On by default for new projects. Turn it off with worlds telemetry disable, WORLDS_TELEMETRY=0 or DO_NOT_TRACK=1.
Account login and payment Organization membership and billing details. Stripe handles card details; Sparta never receives card numbers. Logging in or paying never turns on reporting or evidence uploads.
AI drafting and judging Details are being finalized; ask us before you turn either on.
Your agent Whatever your agent sends to its own model provider. Worlds strips account and billing credentials from the agent's environment.

Where it runs

On your laptop, in your CI, or on a private server you control. The dashboard and CLI use the same local runtime, and neither needs a Sparta account to run a world. Tests, records and evidence stay on your machines. See deployment for CI and servers.

Report a security issue

Email arya@usesparta.co with "Security" in the subject. Include the version you ran and the steps to reproduce.