Data access, privacy, and support
This page answers the questions people ask before connecting an AI assistant to Vaam: what can it see, what can it change, and who else sees the data.
What the assistant can access
Section titled “What the assistant can access”When you connect an assistant, it acts as you. By default it works with your own data — sequences, prospects, video recordings, stats, tasks, and your AI outreach profile. If you are part of a team, it can also read and change data that belongs to your team, the same way you can in the Vaam app.
See what your assistant can do for the full list of what it can read.
What the assistant can change
Section titled “What the assistant can change”Some requests cause the assistant to make a change in Vaam, not just look something up — for example, pausing a sequence, adding or fixing a prospect, or stopping outreach to someone. Vaam only makes a change when the assistant asks for one. Whether the assistant asks first depends on the assistant and how you use it.
Your assistant provider (for example, Claude or ChatGPT) shows you which of these it treats as sensitive and asks you to confirm before it acts, based on how each tool is labeled.
If you connect with a scoped API key instead of logging in directly, the key only allows the specific actions you granted it when you created the key.
Who else sees this data
Section titled “Who else sees this data”Vaam does not send your data to Claude, ChatGPT, or any other assistant on its own. The data only reaches your assistant because you chose to connect it, and only in response to the specific question or action you asked for — the same way it would if you opened the Vaam app yourself and copied the answer into a chat.
Your assistant provider (Anthropic for Claude, OpenAI for ChatGPT) processes what the assistant reads or sends on your behalf, under that provider’s own privacy policy. See the Privacy Policy section on AI assistants for Vaam’s position on this.
For Vaam’s other data processors (hosting, authentication, error monitoring, payments), see Sub-processors.
Staying in control
Section titled “Staying in control”- Disconnect anytime. Remove the connector from your assistant’s settings, or revoke a scoped API key from Settings → API in Vaam. Revoking an API key stops access immediately. Removing a connector blocks it from signing in again right away, but a security token it already holds can stay valid for up to an hour before it expires on its own.
- Scope what a key can do. When you create an API key, grant only the read or write permissions the integration needs.
- Review what changed. Actions taken through the assistant show up the same way as actions taken in the Vaam app — in your sequence and prospect history.
Support
Section titled “Support”Questions about the MCP server, a connected assistant, or anything it did on your behalf: email support@vaam.io.
For Vaam’s full data handling commitments, see the Privacy Policy and Terms of Service.