What SwarmSpace collects, what it does not collect, and how data is handled when plugins execute. Last updated April 2026.
SwarmSpace is a plugin marketplace for personal AI agents — a discovery, trust, and execution layer between AI agents and third-party capability providers. Most users interact with SwarmSpace indirectly, through LUMARA or another AI companion, rather than directly. This policy explains data handling across both surfaces.
We collect the minimum necessary to operate the platform. The categories below cover everything.
| Category | What we collect |
|---|---|
| Account data | Email address, authentication method (email/password, Google, or GitHub OAuth), account creation timestamp, subscription tier. |
| Usage data | Plugin slug and call timestamp, credits consumed per call, daily call count (reset midnight UTC), tier-level quota tracking. We log that a call happened — not what was said. |
| Developer data | Submitted manifest fields (name, description, endpoint URL, trust tier, pricing, tags), submission timestamp and review status, developer UID linked to your account. |
| API keys | Each account is issued an ss_ prefixed API key on signup. Keys are stored as a lookup reference, not in plaintext alongside your account document. Regeneration is atomic — the old key is invalidated in the same operation that creates the new one. |
Three things happen at execution time that are directly relevant to your privacy.
privacy_data_required). LUMARA extracts only those fields client-side. The plugin sandbox receives nothing else through the supported path. This is enforced structurally at the V8 sandbox boundary, not by policy. See the PRISM documentation for full detail.fetch, the credential is attached transparently.network_domains). All other destinations are blocked at the platform layer.SwarmSpace hosts the index and trust layer. Plugin execution calls the developer's endpoint. SwarmSpace does not audit third-party APIs or certify their upstream data handling. The Developer Agreement each plugin developer accepts covers data handling obligations, prompt injection liability, and third-party API terms compliance.
If a plugin receives user context (declared via privacy_data_required), that context is subject to the developer's own privacy practices in addition to the constraints SwarmSpace enforces structurally. Review a plugin's manifest and Swarm page before authorizing it for sensitive use cases.
SwarmSpace uses Firebase Auth for authentication. Firestore stores account and usage data. Cloudflare Workers handle plugin execution with V8 isolate sandboxing. Stripe handles payment processing under Stripe's own privacy and security policies. We do not store payment card details. For the full security architecture, see the Security & Trust Architecture page.
Material changes will be noted at the top of this document with an updated date. Continued use of SwarmSpace after a material change constitutes acceptance of the revised policy.