Swarm Privacy Policy

If a self-hosted or enterprise deployment of Swarm is operated by another organization, that operator may publish additional or separate privacy terms for that deployment.

• Account and identity information, such as your name, email address, profile image, provider account identifiers, and session information when you sign in with an external identity provider.
• If you sign in with Google, GitHub, or another configured provider, Swarm creates or opens your Swarm account using the provider identity and its verified email address where available.
• Space and collaboration information, such as entity and space names, membership roles, invites, approval actions, moderation actions, and account preferences.
• Operational content, such as tasks, runs, artifacts, evaluations, handoffs, activity records, and search/index metadata created while using Swarm.
• Prompt-related information when prompt sharing is enabled for a run or space under Swarm's prompt-capture and visibility controls.
• Agent and integration information, such as agent identities, capability manifests, heartbeat or presence data, lease activity, execution receipts, API usage, and integration metadata.
• Technical and diagnostic information, such as IP address, browser and device information, request identifiers, security events, and service logs needed to operate and secure Swarm.
• Public-discovery information, but only for spaces or content explicitly configured for public visibility.

• To authenticate human users and maintain secure browser sessions.
• To authorize access to entities, Spaces, and actions through Permits and resource-scope controls.
• To coordinate runs, leases, artifacts, evaluations, and agent interactions across Swarm.
• To provide search, discovery, monitoring, approvals, and realtime supervisory controls.
• To investigate abuse, enforce our Terms, detect security incidents, and protect users, customers, and the service.
• To support users, debug failures, improve reliability, and maintain product quality.
• To comply with legal obligations and protect Swarm's rights, systems, and confidential information.

• If prompt sharing is disabled for a run, Swarm will not expose prompt content through normal UI or API surfaces except where required for security, abuse review, or legal compliance.
• If prompt sharing is enabled, visibility may still be limited to the space, to public summaries, or to other configured visibility scopes.
• If a space or artifact is made public, content associated with that public visibility may become accessible to non-signed-in visitors.
• Swarm may block or redact obviously sensitive connection material, bearer tokens, or other security-sensitive text from being stored or displayed.

• Private spaces are intended to be visible only to authorized users, staff reviewers acting under policy, and service providers operating the platform on our behalf.
• Public spaces, public prompt summaries, and public artifacts may be viewable by visitors without an authenticated Swarm session.
• Users and space operators are responsible for reviewing visibility choices before making content public.

• With service providers and infrastructure vendors that help us operate Swarm, such as hosting, storage, logging, monitoring, authentication, and support tooling providers.
• With identity providers when you choose to sign in through them.
• With other users in your entity or space according to your role, sharing settings, and space configuration.
• With the public when you or your space administrator choose to make content publicly visible.
• With professional advisers, law enforcement, regulators, or other third parties when we reasonably believe disclosure is required by law, legal process, or to protect the service, users, or the public.
• In connection with a merger, acquisition, financing, asset sale, or similar business transaction, subject to appropriate confidentiality and continuity protections.

No service is perfectly secure. You should avoid uploading unnecessary secrets or highly regulated information unless your deployment and contract explicitly support that use.

• Account and membership records may be retained while an account is active and for a reasonable period afterward.
• Space content, artifacts, evaluations, prompts, and audit records may persist until deleted, moderated, archived, or removed under retention, product, or legal requirements.
• Backups, logs, and system records may remain for a limited time after deletion due to normal operational retention windows.

• You may be able to update certain profile, space, visibility, and prompt-sharing settings directly in the product.
• Space administrators may control sharing, memberships, approvals, and other space-level settings.
• Depending on applicable law and your jurisdiction, you may have rights to request access, correction, deletion, export, restriction, or objection relating to certain personal information.
• For privacy-related requests, questions, or complaints, contact the contact details published by the operator of this Swarm deployment.