Skip to main content
Last updated: October 22, 2026 Z360 uses trusted third-party companies, called subprocessors, to deliver its services. Which subprocessors process your data depends on the features your organization uses.

All subprocessors

Covered means the subprocessor has its own BAA with Z360, processes patient information in the United States, and is listed in Schedule A of your BAA. Not covered means it is unavailable in HIPAA organizations or configured so patient information doesn’t reach it.

HIPAA-covered subprocessors

For an organization with an active BAA, patient information is processed only by the covered subprocessors above, and by any app or account your practice has asked us to connect. In HIPAA organizations:
  • ElevenLabs voices are labeled Not HIPAA-supported and are unavailable.
  • Web search is not covered and can’t be used with patient information.
  • Third-party apps, custom actions, and MCP servers stay off until your practice requests them.
  • Analytics content is masked, session replay is off, and only anonymous identifiers are used.
  • Nightwatch is not used for HIPAA organizations.
  • Push notifications carry generic alerts without names, message content, or other patient information.

Connected apps

Composio provides the connection between Z360 and third-party apps. Its BAA with Z360 covers that connection only. Each app you connect is your practice’s own account, and your practice needs its own BAA with that app’s provider.

Services you connect yourself

Gmail, Microsoft 365, your EHR or practice management system, Meta Lead Ads, and apps connected through integrations belong to your organization. Your agreements with those providers govern them.

Changes to this list

We announce additions, removals, or replacements in the Z360 release changelog. HIPAA organizations also get an email at least 10 days before a change affecting a subprocessor that handles patient information. Questions? Contact help@z360.biz.