Local Network stores its data on the AT Protocol, not in a private database. Public profiles are ordinary atproto records; everything private uses atproto spaces, the protocol's permissioned-data extension. The app keeps a local index for fast search, and it can rebuild that index from the network.
+Local Network stores its data on the AT Protocol, not in a private database. Public profiles are ordinary atproto records. Everything else sits in atproto spaces, the protocol's permissioned-data extension, and each space's read policy decides who can read it. The app keeps a local index for fast search, and it can rebuild that index from the network.
A project is a DJ act: a solo DJ, a b2b duo, a group, or a whole collective. Published projects are computer.localnetwork.project records in the Local Network root account's public repo. Only the root account writes them, after an admin adds a project or a moderator approves a request, so nobody can change a profile without review.
Anyone with an atproto account can list a new project, claim one an admin added, or propose changes to a project they manage. Each request is written into your own repo, inside the root account's private moderation space. Only staff can read that space. Decisions are recorded by the root account in the same space.
+Anyone with an atproto account can list a new project, claim one an admin added, or propose changes to a project they manage. Each request is written into your own repo, inside the root account's moderation space, which only staff can read. Decisions are recorded by the root account in the same space.
A press kit's public part is a record in Local Network's repo that anyone can read. The rest sits in a space under Local Network's account that only the project's managers, Local Network, and the people they let in can read. Asking to see it shares your handle and any message you write with the project's managers. Each person let in gets a record in that space saying so, which any of the managers can have deleted to take access away. Drafts of a press kit sit in each manager's repo in a space only the project's current managers can read.
When someone let in opens a press kit on this site, its project's managers see who and when. Local Network keeps that receipt for {data.retentionDays} days, and any of the managers can delete it sooner. The audit log keeps a record that the press kit was viewed, but not by whom.
-Booking threads are readable only by the promoter and the project's managers. Your planner is readable only by you.
+Each act, party and venue has a space under Local Network's account with who's in it, their roles, invites and requests to join, and whether it's listed in the directory. Only its people are members of the space, and staff see it through this site.
+Each booking thread is a space under Local Network's account whose only members are the promoter and the project's managers. Local Network indexes the thread so the site can show it to them. Your planner is readable only by you.
We keep a search index derived from the records above, OAuth tokens needed to act on your behalf (encrypted at rest by your host's disk encryption), hashed browser session tokens, and an outbox of audit entries waiting to be written. Signing out revokes our OAuth session.
Your inbox lives only on our server. Each item says what happened and where (a new inquiry or message in one of your booking threads, say) but not what anyone wrote. Read items are deleted after 90 days and unread ones after 180.