If your organization handles protected health information (PHI), you can sign a Business Associate Agreement (BAA) with Clarify. HIPAA has no certification; a BAA is the contract that lets you use Clarify with PHI. This article explains how a BAA works at Clarify and which features it does not cover.
How it works
Your account team arranges the BAA as part of your agreement with Clarify. Once it is signed, we mark your workspace on our side. You cannot change this setting yourself. Features that are not covered are blocked for your workspace where we are able to block them.
What a BAA covers
Every Clarify feature is covered except those listed below. New features, and features that rely on a vendor that has not signed a BAA with Clarify, are not covered until we tell you in writing. The exhibit in your signed BAA is the authoritative list. If this article and your BAA ever differ, the BAA controls.
Blocked in BAA workspaces
Public meeting links and meeting snippets - you cannot publish a meeting or a snippet to the web, and any public links created before your BAA was signed stop working.
Meeting summary emails to external participants - summaries are not sent to meeting participants who are not users in your workspace, and the setting cannot be turned on.
LinkedIn messaging - LinkedIn cannot be connected or used to send messages.
Not covered
These work in your workspace but are not covered by your BAA. Do not use them with PHI.
Notifications - the in-app inbox, notification and briefing emails, and mobile push notifications
Alpha and beta features
The legacy one-way HubSpot sync - the two-way HubSpot sync is covered
Connected third-party systems
Our BAA covers what Clarify does with your data, including syncing it to systems you connect, such as HubSpot or Stripe. It does not cover those systems themselves. You need your own BAA with each vendor you connect.
Questions
For any questions, please reach out to [email protected].