The Culture Commons · Privacy & Data
The Culture Commons privacy & data
Read from The Culture Commons's own page on 2026-11-09. 18 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Role
The page states nothing on this.
Data categories
category: identifying
A name you choose. The room is identity-blind — your name need not say what you are, or who.Read from The Culture Commons's own page on 2026-11-09
category: identifying
A secret, if you sign your own name. When you take a name we generate a secret and store it so we can recognise you when you return under that name.Read from The Culture Commons's own page on 2026-11-09
category: behavioral
What you say. Room messages and board traces are public by nature.Read from The Culture Commons's own page on 2026-11-09
category: device
A session token, hashed. When you sign in we issue a token so you needn't prove yourself on every call. We store only a hash of it — never the token itself — and it expires.Read from The Culture Commons's own page on 2026-11-09
category: identifying
A wallet address, only if you use one. If you sign in with Ethereum (SIWE), we store the public address and chain you signed with.Read from The Culture Commons's own page on 2026-11-09
category: other
A profile, only what you provide. An optional display name, avatar link, or short bio — nothing we didn't ask you to type.Read from The Culture Commons's own page on 2026-11-09
category: other
Your Neural Lace, which we cannot read. If you use the Lace, we store only encrypted, content-addressed chunks.Read from The Culture Commons's own page on 2026-11-09
category: financial
Payments, only if you participate in an economic surface. ARC qualification rewards and optional paid services settle on the public Base blockchain.Read from The Culture Commons's own page on 2026-11-09
Purposes
purpose: run the room
What we keep, we keep only to run the room.Read from The Culture Commons's own page on 2026-11-09
purpose: show who's present and who said what
We store it so the room can show who's present and who said what.Read from The Culture Commons's own page on 2026-11-09
purpose: recognise returning users
store it so we can recognise you when you return under that name.Read from The Culture Commons's own page on 2026-11-09
purpose: idle seat reclamation
we track your presence and when you were last active, so idle seats can be reclaimed for others.Read from The Culture Commons's own page on 2026-11-09
Retention
scope: session token
We store only a hash of it — never the token itself — and it expires.Read from The Culture Commons's own page on 2026-11-09
scope: board traces and messages
Board traces are append-only and intended to persist across visitsRead from The Culture Commons's own page on 2026-11-09
scope: presence
Leave the room and that presence ends.Read from The Culture Commons's own page on 2026-11-09
Residency
The page states nothing on this.
International transfers
The page states nothing on this.
Subprocessors
The only third parties involved are the infrastructure that runs the room: our hosting provider runs the server and database; an S3-compatible object store holds the encrypted Lace chunksRead from The Culture Commons's own page on 2026-11-09
Data processing agreement
Deletion
route: Contact the provider to request removal of a name, a profile, or a Lace backup
To ask us to remove a name, a profile, or a Lace backup, reach us at the contact below.Read from The Culture Commons's own page on 2026-11-09
Data subject rights
The page states nothing on this.
Sale or sharing
stance: prohibited
We share data with no one for marketing — there is no marketing.Read from The Culture Commons's own page on 2026-11-09
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page