Workspace-scoped by default
Every query, dashboard view, and MCP response is from the perspective of the workspace whose credentials authenticated the request. The MCP API key (hbtw_ws_...) is workspace-scoped, never user-scoped. The workspace is determined by the key itself and is never passed as a parameter. There is no way for a query to reach across workspaces.
Inside a workspace, your own company’s domain is excluded by default from company-level aggregation results. This prevents your own employees from skewing account-level analytics.
Privacy-first
Each workspace sees only its own data. heyBTW never exposes one workspace’s CRM, attendees, or pipeline to another workspace. Cross-company signals (for example, Stripe and Chargebee both have an account mapped as a customer) are surfaced only when both workspaces have opted into a collaboration. No collaboration, no signal.No collaboration, no data
heyBTW learns from co-marketing activity that flows through the platform. It does not scrape external relationship data, infer signals from channels it does not connect to, or build a shadow profile of accounts your team has not engaged with. The Context Graph is something your team builds over time by running collaborations through heyBTW. It is not a third-party data product you query against.Two-path CRM architecture
Enterprises with strict CRM data residency or governance requirements can choose how heyBTW interacts with their CRM. Both paths are supported.Path A: Separate tools behind your agent
Connect the heyBTW MCP and your CRM MCP (HubSpot MCP, Salesforce MCP, or your own internal tooling) as independent tools behind the same agent. The agent reasons over both, but no CRM data ever flows into heyBTW. Best for enterprises with data residency requirements, security teams that want to prevent vendor-side joins of CRM and event data, or teams already running an MCP-based agent stack. Trade-off: the agent does the join at query time, so heyBTW cannot pre-compute enriched results that depend on CRM context.Path B: CRM connected inside heyBTW
Connect HubSpot, Salesforce, or Attio directly inside heyBTW. heyBTW reads contact, company, deal, and meeting data, joins it with event and partner data, and returns enriched results pre-joined. Best for teams that want the full Context Graph, including invite lists scored against pipeline, attribution to specific deals, and partner relationship surfacing tied to CRM accounts. Trade-off: CRM data is processed by heyBTW. Standard scopes apply: read by default, write only for the fields you explicitly enable. Full integration details are in CRM. You can switch paths at any time. Disconnecting the CRM inside heyBTW removes the synced data on the heyBTW side.Trust Center
For heyBTW’s security posture, subprocessors, and compliance documentation, see the Trust Center.Related
- MCP Tools: API key generation, scoping, and tool reference.
- CRM: HubSpot, Salesforce, and Attio integration details.
- Context Graph Coordinates: how relationships, attribution, and outcomes compose.