Organizations, invitations and leaving
How people join a company, what happens to their trons when they leave, how a company is deleted, and how to take your data.
Privacy proxy for the whole company
Organization → Settings → Privacy proxy. Owners and admins set the company default for the privacy proxy (proxy_default, on or off: a tron left off follows it), can enforce it on every company tron (proxy_forced: the trons cannot switch it off), keep a list of names to protect that adds to each tron's own, and set an image proxy for the company, optionally used by every tron instead of their own (image_redactor_forced). Every change goes in the Activity registry, without the names or the address. API: GET and PUT /org/privacy, POST /org/privacy/image-redactor/key, POST /org/privacy/image-redactor/probe. See /docs/privacy-proxy.
Joining is always by invitation
An owner or admin invites somebody from Organization → People (or with the org_add_member MCP tool). Whether the address already has a Vibetron account or not, an email goes out with a link valid for 7 days; the person joins only if they open it and accept, signed in with that address (without an account, signing in creates one). They can decline from the same page. An invitation can be resent (a new link: the old one stops working) or withdrawn. Nobody is ever added without saying yes.
What joining changes
Your personal trons stay yours: nothing moves to the company. While you are a member the company's plan applies to you, and you cannot delete your account by yourself. A personal plan you had bought is put aside and comes back when you leave.
Leaving: copies are frozen for 30 days
When somebody leaves (or is removed), the company trons they held — the copies they were given and the ones they made — are stopped and FROZEN for 30 days: read-only, no chats, no deploys, no edits, shown with a «Frozen until …» chip. An owner or admin can unfreeze one from Assigned trons (it goes back to the person if they are a member again, otherwise to whoever unfreezes it). After 30 days a frozen tron is destroyed.
The bin: 3 days
A tron you delete goes to the bin for 3 days, and can be restored from there; then it is destroyed with its container and files. Taking a copy back from somebody without keeping it sends it to the bin as well.
Deleting the organization
Only the owner, from Organization → Settings → Ownership, typing the exact name of the company; refused while a turn or a deploy is running. The company's trons (including the copies its members worked on, encrypted with the company's key), libraries, shared keys, invitations and activity are deleted. Every member keeps their account and personal trons, goes back to their previous personal plan or to Free, and gets an email.
Taking your data
Settings → Your data → Export everything downloads one zip: your account in JSON, every personal tron as a complete package (memories, workspace files, library documents), your own libraries, your tron builder conversations, the names of your references (never their values), your usage as CSV, and a manifest with every file's SHA-256.
How long things are kept
Application events 90 days, the operator's administration log 365 days, tron builder conversations 180 days without activity. Chat history and usage records have no automatic expiry. The full table is in the Privacy Policy.