Privacy

Effective date: current live policy.

1. What we read

SwarmWarn connects with read-only credentials to your repo, your schema metadata, and your deployment surface. We read code, declared schema, route manifests, build artifacts, and platform constraints. We do not read database rows.

2. What we don't read

• Customer PII inside your database tables
• Production logs unless explicitly opt-in
• Anything outside the scope of the connected token

3. What we write

By default: nothing. SwarmWarn is read-only. Any write action — including opening a PR for a fix plan — requires explicit human-in-the-loop authorization.

4. Where data lives

Readouts and verdict objects are stored in your tenant on Supabase / Postgres. Retention follows your plan tier. Evidence chains are signed and tamper-evident.

5. Subprocessors

• Cloudflare (compute / edge)
• Supabase (database)
• AWS (database / object storage where applicable)
• OpenRouter / MiMo (model explanation layer, with provider resilience)
• Stripe (billing — pending live)

6. Your rights

You can export your readouts, revoke our read-only access at any time, and request deletion of your tenant data. Contact assist@swarmwarn.com.

7. Contact

Security and privacy questions: assist@swarmwarn.com. General privacy: assist@swarmwarn.com.