Scope and responsibility
This notice describes the current development service. Organizations decide what data they submit and who may access it. Their own policies may also apply to records they collect about people, devices, and applications. This notice does not replace those policies.
Information the service handles
- Account information: identity and session information used for sign-in through Clerk, together with user identifiers needed to associate you with an organization.
- Organization and access information: organization names, membership, roles, and access configuration.
- Submitted data: database schemas, typed records, timestamps, telemetry, device and stream configuration, and credentials or keys you configure for integrations.
- Service information: requests and operational or security records. Hosting and authentication providers may process IP addresses, browser information, timestamps, and error details when delivering their services.
Avoid submitting personal or sensitive information unless you are authorized to do so and have assessed whether a development service is suitable for it.
Why information is used
Information is used to authenticate users, apply organization permissions, receive and query data, operate integrations, investigate errors, protect the service, and meet applicable legal obligations. Agent workflows are planned features; the landing page’s illustrative agent scenarios do not describe an active model-provider integration.
Service providers and access
Clerk provides authentication. Cloudflare provides hosting and infrastructure used for storage, delivery, and security. Their processing is described in the Clerk privacy policy and Cloudflare privacy policy. Processing by providers may take place across regions; this notice does not promise storage in a particular country.
Organization permissions determine access within the service. External brokers or integrations configured by an organization may receive information under that organization’s instructions and the external provider’s terms. Information may also be disclosed when required by applicable law or necessary to investigate abuse or protect the service.
Cookies and browser storage
Authentication uses essential cookies and related browser mechanisms to maintain sign-in and protect sessions. Blocking them can prevent sign-in from working. See Clerk’s cookie documentation.
The current website code does not include optional advertising or visitor-analytics integrations. There is no optional tracking preference to switch on this page. The privacy and data controls explain how to manage browser storage and account access.
Retention and deletion
Retention depends on the resource, configuration, development status, and operational, security, or legal needs. There is no single retention period for every kind of information. Removing a resource or clearing browser storage does not necessarily remove backups, security records, or other server-side information immediately.
Keep copies of data you need. Development features and storage behavior may change, and the service should not be your only copy of important records.
Your choices and requests
Depending on applicable law and your relationship to the data, you may have rights to access, correct, delete, restrict, or obtain a copy of personal information. Available self-service controls and their limits are explained on Manage privacy & data. For organization-controlled records, contact the organization’s owner or administrator.
A dedicated public operator contact is still being prepared. There is currently no request form or inbox on this website, and visiting these pages does not submit a privacy request.
Updates to this notice
This notice will be revised as operator details, features, providers, and data practices are finalized. Material new uses or recipients should be described before the relevant feature is introduced. The date above identifies this version.