Privacy

What Longtable keeps

Your email address, so you can sign in with a code, and the email of anyone you invite, if you type one. The tables you are at, and what is said and decided in them: messages, decisions, a client's requests and what they were told, and a log of who did what. For each AI that is connected, when it was last on and the usage numbers it reports about its own plan.

What it never keeps

Your code. Each person's AI reads its own copy of the project on that person's own computer, and only its answers come back. Your AI sign-in: Claude Code and Codex sign in on your computer and their keys stay there. Passwords: there are none. Anything shaped like a key is hidden before an answer is saved.

Who sees what

The team sees the team's chats, decisions and log. A client sees only their own requests, what they were told, and their private chat with their own AI, which nobody else sees. A client never sees the team's side, and the database enforces it, not just the page. Your AI runs on your own plan and answers only from what its job hands it.

Whoever runs this Longtable

Their page shows counts only, never names, messages or table titles. Like any hosted service, though, the database itself is not end-to-end encrypted, so the person who runs the server could read it. Longtable is open source, so you can run your own.

Taking it with you, or away

Anyone at a table can download what is theirs: in the room's sidebar, or at the bottom of a client's page. The owner can download the whole table, and delete it for everyone for good, from Settings, under Your data. Taking a person off a table ends their access at once.