Privacy policy

Operator and contact

Swarm is operated by Darragh Buckley 1812. Swarm connects selected account tools to agents.

For support, privacy questions, or deletion requests, contact darragh.buckley1812@gmail.com.

If you contact support, we receive your address and message. We use this information to handle your request.

Support correspondence is stored separately in the support mailbox. You can request its deletion through the same address.

Account and connection data

Swarm uses Supabase for authentication. GitHub sign-in supplies account information, such as your email address and GitHub profile information.

The authentication service stores account identifiers, authentication records, and session information. Existing email accounts can also sign in.

Swarm stores connection names, service account labels, ownership identifiers, settings, tool descriptions, and enabled tool permissions.

Custom server connections also store the server address, discovered tool schemas, and any saved authentication credential.

Swarm encrypts saved service credentials. Access tokens permit service requests. Refresh tokens can obtain replacement access tokens after expiry.

Organization features store names, member identifiers, invitation records, selected tool shares, and audit records of organization changes.

Browser storage

Your browser stores the Swarm sign-in session and remembered agent key identifiers.

Temporary browser storage holds pending invitations, authorization proof, and Gmail approval identifiers. The current preview does not store Gmail search queries or results in browser storage.

Raw agent keys appear when created. Swarm does not save raw agent keys in browser storage.

You can copy a key or save an agent configuration file. You control copies that you save or give to agents.

Sign out on shared devices. Browser controls can remove stored website data.

Gmail data and search

Google grants Swarm read access to Gmail messages and settings. Swarm uses this access for its mailbox search feature.

Swarm sends your search query to Google. It returns message IDs, thread IDs, and the Subject, From, and Date headers.

The current tool does not fetch message bodies or attachments. It does not modify mail.

Swarm reads your Gmail address to identify the connected account. It stores that address as the account label.

Gmail authorization is separate from Swarm account sign-in. You can cancel Google's authorization screen.

Gmail connections currently use Google's Testing status. Only approved test users can connect. Test authorization can expire after seven days.

Each Gmail search requires approval on the signed-in Swarm website. Agent keys cannot approve searches.

The review shows the mailbox, exact query, result limit, and requesting key fingerprint. A fingerprint is a short identifier for the key.

Approval permits one attempt for that request and key. It expires ten minutes after the request starts.

A changed query, connection, result limit, or key needs another approval. A failed attempt also needs another approval.

You can deny a search instead. Before approval, the server does not search Gmail or refresh its Gmail token.

The approval page requires confirmation of permitted agent data use. This confirmation does not verify the agent provider's identity or practices.

Other tools

GitHub tools return pull request numbers, titles, links, and states from selected public repositories.

Slack search returns message text, times, links, and channel names available to the connected account.

Linear tools return issue identifiers, titles, links, and states.

These native tools read data. Custom server tools can have other effects, including changes to data.

A custom server receives the selected tool arguments through Swarm. Swarm returns its results to the requesting agent.

The custom server's data handling depends on the server you connect.

Recipients and organization sharing

Supabase hosts Swarm's gateway, database, and authentication service. The database is hosted in the United States.

GitHub Pages hosts the website. Google, GitHub, Slack, Linear, and selected custom servers process their respective connection requests.

Swarm sends tool results to the requesting agent. Anyone holding your agent key can request tools available to that key.

If you share a tool with an organization, members' agents can request it through their own keys.

Sharing Gmail tool access permits mailbox searches. It does not restrict access to selected messages.

Swarm's connection-management API does not provide your saved service credentials to organization members.

Swarm does not identify or verify the agent provider from an agent key. Provider storage, human access, and training settings can differ.

Use Gmail only with an agent whose data handling meets Google's applicable rules. Do not provide Gmail access for prohibited uses.

Removing access in Swarm does not erase results already received by an agent. Contact that provider about its copies.

Google data-use commitments

Swarm commits to follow the Google API Services User Data Policy, including its Limited Use requirements.

Swarm also commits to follow the Google Workspace data policy.

Swarm will use Google data only for the disclosed mailbox search feature. Swarm will not sell Google data.

Swarm will not use Google data for advertising, credit decisions, or general model training.

Transfers are restricted to permitted features with user consent, security needs, legal requirements, or an eligible business transfer with prior consent.

Human access requires documented consent for specific data, a permitted security purpose, a legal requirement, or permitted aggregated and anonymized internal use.

Staff, contractors, agents, and successors must follow these restrictions. These commitments do not certify an agent provider's practices.

Google verification and checks of recipient practices remain incomplete. This policy does not announce public Gmail availability.

Retention and deletion limits

Swarm keeps active account and connection records until removal or replacement. The Gmail tool processes search results for each request.

The Gmail tool's application code does not write message headers or search results to the database.

Pending Gmail approvals store an encrypted query and result limit. Approval records also contain account, connection, key, and request identifiers.

The server clears encrypted query data after use or denial. Expired approvals cannot execute.

During later approval activity, Swarm clears expired query data that is available for cleanup. Locked records can require later activity.

Without later activity, expired encrypted query data can remain. Approval hashes, identifiers, and decision times have no automatic expiry.

Removing a connection deletes its Gmail approval records.

Removing a connection deletes its active credentials, pending user authorization records, and organization shares.

Earlier imported credential copies and account labels remain separate from active connections. Removing the active connection does not delete these historical copies.

Legacy authorization records can also remain after connection or account deletion. These records require separate operator handling.

Historical credential copies and the import marker have no automatic expiry. They require separate operator handling.

Team audit records retain identifiers after account, connection, or organization deletion. They have no automatic expiry.

Revoking an agent key prevents its future use. Its hash and revocation record remain until account deletion or separate operator handling.

Expired user authorization records cannot complete authorization. They can remain until later cleanup or connection removal.

For account or historical-data deletion, contact the privacy address. We will verify account control and check the relevant records.

We will report the deletion result and identify any known retained copies or retention reasons.

Account deletion removes active connections, agent keys, memberships, and owned organizations. Some historical and audit records need separate handling.

Hosting logs and backups

Hosting providers process technical information, such as IP addresses, request times, addresses requested, response status, and authentication events.

GitHub records website visitors' IP addresses for security purposes. See GitHub Pages data collection.

The inspected Swarm application source contains no advertising or analytics SDK. Hosting providers operate their own logging systems.

Swarm currently uses Supabase's Free plan. Its published limits list one day for API and database logs and one hour for Auth audit logs.

These plan limits do not prove deletion from every logging system or database. See Supabase's plan details.

The backup inspection on 16 October 2026 listed no available database backups. Point-in-time recovery was disabled.

That inspection does not establish whether historical or manual copies exist. Swarm does not promise a fixed deletion period for unknown copies.

Hosting logs, support correspondence, and historical copies require separate handling when relevant to a deletion request.

Your choices and access removal

1. To stop a tool, clear its selection and select Save tools.
2. To stop organization access, withdraw the tool share.
3. To remove an active connection, select Remove on its account card.
4. To stop an agent key, select Revoke key.
5. To revoke Google's grant, remove Swarm from your Google Account connections.
6. To request account or historical-data deletion, contact the privacy address.

Removing a connection in Swarm does not revoke the provider's authorization grant.

Do not include passwords, tokens, or mailbox content in a privacy request. We will request only information needed to verify account control.

You can ask about your data or request correction through the privacy address.

Access controls and security

Swarm checks connection ownership and shared tool permissions on its server. It checks Gmail access before Gmail requests.

Swarm encrypts saved service credentials and uses HTTPS for public connections.

Authorized operators can administer the hosting project and database. Human access to Google data must follow the restrictions above.

These controls do not establish a security certification or eliminate all security risks.

Policy changes

We will update this policy when Swarm's data handling changes. Material changes will be identified with the updated publication date.

New Google data uses will require updated disclosure and consent before those uses begin.