PUBLIC BETA

Privacy during the public beta

Notice version 2026-09-28

This notice describes the beta website and signup. The Worlds runtime and dashboard run on your infrastructure and do not send runtime telemetry or local test history to Sparta.

What signup collects

We require an email address and a short description of your use case. Company and design-partner interest are optional. We also record the submission time and identifier, notice version, requested connector when relevant, and the referring page or campaign information supplied with the form.

Do not include credentials, customer records or other confidential data in the use-case field. A successful signup places a local browser marker that remembers access to installation guides. The marker contains only the completion time and notice version, expires after six months, and contains no email address or use-case text. Clearing browser storage removes it; unavailable storage keeps completion only for the current visit.

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.

We use Vercel Web Analytics for aggregate website activity. We do not send your email, use-case text, company, private files or credentials as analytics event properties, and website analytics does not observe your local Worlds runs.

Retention and your choices

Signup 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 signup information, or to stop follow-up contact. You can decline design-partner conversations without losing access to an installed package.

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. Configured webhook destinations and package downloads also use the network. 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. If you ask us for support, review any evidence before sending it.