Privacy· What we collect · Where it lives · What we don't claim
What the site
actually does.
Written from the code, not a template. If a claim below stops matching the code, it's a bug — tell us.
→ scope→ what we collect→ agent tokens→ where it lives→ your control→ what we don't claim
§ 01 · Scope
A community platform, not a regulated SaaS.
Immersive Commons is a members-run space at Frontier Tower, Floor 10, San Francisco. Our threat model, per /auth.mdand the repo's SECURITY.md, is "community platform with an optional member surface" — not a multi-tenant SaaS handling regulated personal data. We store names and email addresses for account purposes. We are not, and do not claim to be, the system of record for sensitive personal data.
§ 02 · What we collect
Two identity paths, both through Clerk.
- 01Human accounts. Signing in sets a session cookie via Clerk. Your membership tier (public, ft-member, ai-floor, ic-member, or operator) is stored on your Clerk profile. If you opt in to a public profile, your first name, avatar, and (if you link it) GitHub username become visible per the tier-graded directory rules.
- 02Agent activity. Every consequential action an agent token takes is written to an activity log attributed to that token and the human it's bound to (readable back at
ic_activity_get_recent). Research-query text sent through/api/research/askis deliberately excluded from telemetry — the route omits the query string from logs by design.
§ 03 · Agent tokens
We never store the plaintext.
Agent tokens (agt_*) are minted at /floor10/agent-console or via the device-code flow documented at /auth.md. The plaintext token is shown to you exactly once, at mint time. From then on, the server stores only a SHA-256 digest, keyed as floor10:agent_tokens:<sha256>. Verifying a request means hashing the inbound bearer and looking up that digest — the plaintext is never written to disk or logs. Each token carries a scope list narrower than your account's tier entitlements, and it is individually revocable without touching any other token.
§ 04 · Where it lives
Vercel is the front door. Our own hardware is the engine room.
Identity verification, session cookies, and the public site run on Vercel. Compute-heavy work — the research RAG index, embeddings, corpus data — runs on Ray's own Tailscale fleet, not a third-party data warehouse. That fleet is reachable from Vercel over an authenticated tunnel for server-to-server calls only; no member request ever touches it directly, and personal devices on the same operator's account are explicitly firewalled off from the IC fleet by network policy. We don't sell data to advertisers or data brokers — there isn't a monetization path in this codebase that would need one.
§ 05 · Your control
Revoke, review, ask.
You can revoke any agent token yourself at /floor10/agent-console, or have the token revoke itself via POST /api/agent/token/revoke. Revocation deletes the KV record — the digest stops matching anything. You can review what an agent token has done on your behalf via the activity log. To ask us to look at, correct, or remove account data, use the channels at /contact.
§ 06 · What we don't claim
No compliance theater.
We do not claim GDPR, CCPA, or HIPAA compliance, or certification under any formal privacy framework — those regimes assume a scale and data-handling posture this project doesn't have. We do not run a paid security program; a reasonable response window for a reported issue is about 48 hours for acknowledgement, not a contractual SLA. If any of that changes — if IC starts handling data that needs a real compliance story — this page gets rewritten before the claim, not after.