Closed beta · run Worlds on your machineBrowse worlds →

Closed beta

Privacy during the beta

Notice version 2026-10-14

This notice covers closed beta applications, connector and custom-world requests, earlier beta signups and optional aggregate reporting. Worlds runs tests and stores customer data and evidence on your infrastructure. Releases with usage reporting disclose the choice during onboarding.

Commercial accounts and payment

When commercial accounts are configured, AWS Cognito handles login and Sparta's AWS service stores organization membership, evaluation terms, billing identifiers and access dates. Stripe processes payment details and invoices through its hosted Checkout and Customer Portal. Sparta's commercial service does not receive card numbers. Billing contacts and invoice records are separate from the customer records used inside your local test worlds.

An account, subscription or license refresh does not enable aggregate reporting or private evidence uploads. Your organization owner manages billing. Contact Sparta to ask about account access, billing records or deletion; payment and invoice records may need to be retained for the applicable business obligations.

What signup collects

For access applications, we require your full name, work email, agent purpose and preferred product tier. We also record the submission time and identifier, requested connector when relevant, and the referring page. Connector and custom-world requests collect your work email, requested system, agent actions and any setup details you choose to provide. Earlier public beta signups may also include company, design-partner interest, notice version and campaign information.

Do not include credentials, customer records or other confidential data in the use-case field. A successful application confirms receipt for review; it does not grant access or create a subscription. Approved applicants receive setup details separately.

How we use and store it

Sparta uses this information to provide beta access, understand requested workflows, answer questions and follow up about your beta use. Selecting design-partner interest invites a conversation about that program. Signup does not subscribe you to a newsletter.

The website and capture endpoint run on Vercel. Signup records are stored in a private Google Sheet through Google Apps Script and are available to the Sparta team handling the beta. These providers process data as part of operating those services; hosting logs may include technical request information such as an IP address.

This website does not load optional website analytics. Applications send the details you enter to Sparta for beta review. Hosting logs may contain technical request information; your local Worlds runs are separate from website activity.

Optional usage and outcome reporting

New onboarding selects aggregate reporting with an opt-out. Existing installations remain off until you choose; unknown CLI and CI installations remain off until configured. Declining reporting does not limit tests or require an account.

With reporting enabled, Sparta receives random installation and project IDs, an optional opaque team ID, product version, registered feature and connector names, bounded usage counts, duration buckets and aggregate test outcomes. We do not upload prompts, replies, code, commands, paths, repository URLs, customer records, credentials, raw requests, diffs, money amounts or evidence.

Use Usage reporting settings or worlds telemetry disable to stop the relevant reporting. WORLDS_TELEMETRY=0 and DO_NOT_TRACK=1 hard disable runtime reporting. See the reporting policy.

Retention and your choices

Application and connector-request records do not expire automatically. We retain them for beta follow-up, support and design-partner conversations until you request deletion or we no longer need them. Provider operational logs follow the provider's retention settings.

Email arya@usesparta.co to request access, correction or deletion of your application or connector-request information, or to stop follow-up contact.

Your local data and external services

Your agent may contact its model provider. Source-account imports contact the selected provider, and optional model-assisted drafting or grading sends the content you choose to its configured model service. Review these connections separately from website signup.

Share only reviewed reports and de-identified inputs. Keep credentials, identity maps and private local evidence out of public files.