GetVocal · Trust Center

Getvocal Trust Center

Trust center

GetVocal maintains a public trust center documenting SOC 2, ISO 27001, and HIPAA compliance.

CompanyArtificial IntelligenceVoice AIConversational AICustomer ExperienceAI AgentsContact CenterAgent GovernanceMCPagent-native
Trust center: https://trust.getvocal.ai/

Certifications & Compliance

SOC 2ISO 27001HIPAA

Source

Trust Center

Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://www.getvocal.ai/llms.txt
url: https://trust.getvocal.ai/
certifications:
- SOC 2
- ISO 27001
- HIPAA
compliance:
- GDPR
- EU AI Act
notes: >-
  A public Trust Center is hosted at trust.getvocal.ai (a client-rendered SPA,
  so its document list could not be scraped verbatim). The certification and
  compliance postures above are stated by the provider in their published
  /llms.txt: "GDPR and EU AI Act aligned; ISO 27001, SOC 2 and HIPAA postures
  available." Deployment options: on-premises, self-hosted, EU-hosted or hybrid.
evidence:
- source: https://www.getvocal.ai/llms.txt
  keywords: [iso 27001, soc 2, hipaa, gdpr, eu ai act]
- source: https://trust.getvocal.ai/
  keywords: [trust center]

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/getvocal-trust-center"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.