RingMind is built to keep as little sensitive information as it needs, and to put a person in charge of what assistants can use.
Integration tokens
- Tokens and keys you give RingMind for integrations are stored encrypted.
- They're never shown again after you save them, to anyone, including you. To change one, enter a new one.
- MCP server API keys are stored with our voice provider and can't be read back.
- Workspace data downloads never include integration credentials.
Tool calls and approvals
- Tool call logs keep only which tool ran, when and whether it worked — not what callers said.
- Approval requests keep the caller's details only until an owner or admin decides, then erase them. Only owners and admins can see them.
Knowledge
Imported web pages and documents are used only after you approve them, so nothing reaches callers without a person checking it. See Reviewing and approving.
Payments
Card details are entered on Stripe's pages and never reach RingMind.
What assistants won't collect
Every assistant refuses card numbers, bank details, passwords and government ID numbers. See What assistants won't do.
Access inside your workspace
Roles decide who can see and change what, and each workspace's data is kept separate from every other workspace's. See Who can do what.