Privacy

What the product is

swarmvia lets you share MCP servers, PostgreSQL or MySQL databases, and HTTPS APIs with agents without sharing the credential. The dashboard at swarmvia.com is the source of truth for organizations, sources, keys, and billing. Callers reach a source on *.swarmvia.cloud.

What we store in the dashboard

When you create an account we keep your name, email, and a hashed password or passkey, or a link to the Google or Microsoft account you sign in with. Organizations hold source config, key labels, invitations, and billing state. You can delete an organization or your account from the dashboard.

We do not store managed upstream credentials in the dashboard. Not even a hash.

Signing in with Google or Microsoft

When you sign in with one of these providers, it sends us your name, email address, whether it has verified that address, and an ID for your account with that provider. We ask for nothing else: no contacts, files, calendar or mail, and we never see your password with that provider.

We use this only to create your account, sign you in, and, if your organization turns on domain auto-join, check whether your verified email is on one of its domains. We do not use it for advertising and we do not sell it.

Disconnect a provider under Settings → Security, or revoke swarmvia's access from your Google or Microsoft account settings. Deleting your account removes the link.

Upstream credentials

You can give a source an origin secret so callers never hold it. The secret is encrypted at the edge and decrypted only inside an isolated sandbox when swarmvia reaches your origin. Callers authenticate with an access key. They never receive the origin secret.

The same applies to an MCP server's credential. When you connect a third-party MCP server, the OAuth tokens or API token swarmvia holds for it are encrypted the same way, are never shown to you again, and are deleted when the source is deleted.

Rotate a credential from Credentials and every attached source picks up the new secret.

Access logs and metrics

We log source traffic. Every request through a source produces an access log entry, including admits and rejects. Nothing consumes a slot silently.

A typical HTTP entry includes timestamp, method, path and query (truncated), host, content type, length, status, outcome, timing, occupancy, caller IP, referer host, a truncated user-agent, Cloudflare colo / country / ASN, and the label of the access key that authenticated the caller. You can attach a short tag with X-Swarmvia-Tags.

We do not record HTTP request or response bodies, credentials, raw keys, or full header sets.

Database sources also log the SQL statement (truncated), row counts, and whether the result was capped. A statement the database refused is logged too. That is how you can see who ran what.

Logs live in a short window on the source, then ship to Cloudflare R2. Retention follows the plan: Free 1 day, Starter 30 days, Team 90 days, Business 1 year. Custom plans can keep them longer. Search and download them from the Logs tab. Metrics roll up hourly from the same entries.

Billing

Paid plans go through Stripe. Stripe sees the card. We keep the subscription and usage we need to bill you.

Cookies

The dashboard uses a session cookie so you stay signed in, and a cookie that remembers how you last signed in on that browser (password, passkey, Google or Microsoft) so the sign-in page can point you to it. We do not set advertising cookies. When product analytics is turned on, PostHog sets a first-party analytics cookie on every page, including the public ones, to count page views and feature use.

Who else sees data

These are the providers this product actually uses:

• Laravel Cloud hosts the dashboard
• Cloudflare runs the proxy on a global edge network and stores access logs (R2)
• Stripe handles checkout and subscriptions
• PostHog provides product analytics (page views and feature use, linked to your account once you sign in)

We do not have a signed DPA or a longer subprocessor list yet. If a vendor review needs one, email us and we will say where things stand.

Questions and deletion

Email [email protected]. You can also delete organizations and your account yourself. Deleting an organization removes its sources and sealed credentials for that org. Deleting your account removes your personal organization the same way; delete any other organizations you own first.

Changes

This is early access. We will update this page when the product changes how it handles data. See also the Terms.