Privacy and control: what Rango records, and who decides

A meeting agent hears real conversations, so the controls around it should be stated as plainly as the features. Here they are.

It is never hidden

Rango joins as a named participant, visible in the participant list, and posts an arrival message that says how to talk to it. There is no stealth mode and will not be one. Everyone in the room can see the room includes an agent — the same standard you would hold a human notetaker to.

The invite is the permission

Rango is in a meeting because someone put it there: pasted the link or added its address to the invite. Remove it from the invite, or dismiss it from the call, and it is gone. It does not attend anything it was not explicitly brought to.

Memory is a switch, not a default you fight

Workspace settings contain one plainly-worded switch: remember what we talk about. On, the agent builds its knowledge base from your meetings. Off, every meeting stands alone — it still joins and still writes the summary, but carries nothing forward and reads nothing back. Turning memory off deletes nothing (the page says so at the moment you toggle it, because that is the moment you wonder); deleting is its own action.

Deletion is deliberate and real

Clearing the knowledge base is a separate, typed-confirmation action that removes every page. Meetings, transcripts and summaries also expire on your plan's retention schedule — a week on free, three months on Starter, a year on Pro — rather than accumulating forever by default.

Workspaces are isolated where it counts

Your workspace's data is separated from every other workspace at the database level — row-level security enforced by the database itself — rather than by application code remembering to filter. It is the difference between a door and a sign that says please do not enter.

The posture in one sentence

Visible in the room, invited or absent, memory by choice, deletion for real, and isolation enforced below the application: that is the deal, and every piece of it is inspectable in your own workspace settings.