HIPAA mode
HIPAA mode moves a workspace's AI into your own cloud account: your AWS account, your Google Cloud project, or both. This page says what runs where. It also lists what is not covered yet.
The short version#
- AI runs only in your AWS or Google Cloud account. Every AI request goes to Amazon Bedrock through a role you create in AWS, or to Google Vertex AI through a service account you give a role in your Google Cloud project. You can connect one cloud or both.
- Everything else stays where it is today. Your records and chat history are in Coeffection's database.
- Some items are still open. They are listed under Open items. Read them before you decide what to store in the workspace.
What runs where#
This table covers what HIPAA mode changes or touches. It is not a full list of every service Coeffection uses.
| What | Where it runs | Notes |
|---|---|---|
| AI requests | Amazon Bedrock in your AWS account, or Google Vertex AI in your Google Cloud project | Grace, the daily brief, the field service brief, lead research and the AI step of Clay contact discovery. You connect one cloud or both. You pick the region and the models. You pay AWS and Google Cloud directly. |
| Anthropic, OpenAI and the Gemini API | Off | Their keys, model lists and tests are refused while HIPAA mode is on. Saved keys are hidden and left untouched. Nothing falls back to them if Amazon Bedrock or Google Vertex AI fails. |
| Lead research | Google Vertex AI, with no live web search | Runs when Google Vertex AI is connected. The answer comes from the AI model alone, and the result carries the note “No live web search in HIPAA mode. This research comes from the AI model only.” With only Amazon Bedrock connected, lead research is off. |
| Live web search, and enrichment that writes to records | Off until verified | Web research is off in HIPAA mode. No model call is made and no tokens are used. They stay off until Coeffection verifies web search: Web Grounding for Enterprise on Google Vertex AI, or web search on Amazon Bedrock. |
| Chat history and CRM data | Coeffection's database: PostgreSQL on DigitalOcean | Stored by Coeffection, not in your AWS or Google Cloud account. A BAA with DigitalOcean is an open item. |
| Email sent by Coeffection | Amazon SES | Sign-in codes and notifications that Coeffection sends itself. |
| Error reports | Sentry | For errors in AI code, Coeffection removes request bodies, local variables and cookies before the report is sent. Errors elsewhere in the app are not yet stripped of patient data. Sentry is an open item. |
| Clay | Clay, a third party | There is no BAA with Clay. Do not send patient data to Clay. Only the AI step of Clay contact discovery runs in your cloud account. |
How HIPAA mode is turned on#
- HIPAA mode is turned on by Coeffection on request. Contact us to discuss your requirements. You can't turn it on yourself.
- You connect Amazon Bedrock, Google Vertex AI, or both. The Amazon Bedrock setup guide and the Google Vertex AI setup guide have the steps. You need at least one. Until you connect one, AI features show “Connect Amazon Bedrock or Google Vertex AI to use AI”.
Coeffection can turn HIPAA mode off again. AI then returns to direct providers. Data from the HIPAA period stays where it is.
AI in your cloud: Amazon Bedrock and Google Vertex AI#
- Every AI feature goes through Amazon Bedrock, using the access role you create in your AWS account, or through Google Vertex AI, using a service account you give a role in your Google Cloud project.
- You can connect one cloud or both. With both, each task starts on the cloud that suits it, and you can pick a model on either cloud for a task. The Google Vertex AI setup guide has the table of where each task starts.
- You choose the region on each cloud, and the model for each task. Amazon Bedrock runs in one of the supported US regions. Google Vertex AI starts on Google's global endpoint, where Google may process a request in any location. Choose a US region there if you need requests processed in the United States.
- If a cloud can't answer, the feature says so. Coeffection does not send the request to the other cloud, or to another provider, instead.
- Gemini models run only through Google Vertex AI, in your own Google Cloud project. The Gemini API, which uses a Google API key, stays off.
- You pay AWS and Google Cloud directly. Coeffection still counts tokens so your usage caps keep working.
Web research#
What lead research does depends on which cloud you connect.
- With Google Vertex AI connected, Lead Inbox AI research runs without live web search. It comes from the AI model alone and shows no sources. The result carries the note “No live web search in HIPAA mode. This research comes from the AI model only.”
- With only Amazon Bedrock connected, it is off. The Lead Inbox AI research button says “Web research is off in HIPAA mode.” It makes no model call and spends no tokens.
Live web search itself stays off until Coeffection verifies it. On Google Vertex AI, Coeffection has to confirm that Web Grounding for Enterprise is on Google Cloud's list of products covered by its BAA. On Amazon Bedrock, web search has to work, and the text of each search has to stay inside AWS and not go to a third-party search provider. If a check fails, live web search stays off. Features that write enrichment into your records stay off until then too. Coeffection never falls back to the Gemini API or Anthropic web search.
Clay#
Clay is a third-party service. There is no BAA with Clay. In HIPAA mode only the AI step of Clay contact discovery moves into your cloud account. What Clay itself receives and returns does not run in your AWS or Google Cloud account.
Open items#
These are not finished. Coeffection lists them here so you can decide with the full picture.
- DigitalOcean BAA. Your chat history and CRM data are stored in Coeffection's PostgreSQL database on DigitalOcean. A BAA with DigitalOcean is not in place yet.
- Sentry. Coeffection needs either a Sentry Business plan with a BAA, or to strip patient data from every event. Neither is done yet.
- Web research. Live web search is off until it is verified: Web Grounding for Enterprise on Google Vertex AI, or web search on Amazon Bedrock. Lead research on Google Vertex AI runs without it.
What stays with you#
- HIPAA mode does not replace your own BAA with AWS or Google Cloud, your risk assessment or your policies. You sign each BAA yourself, and each cloud decides which of its services the BAA covers.
- It does not change your other integrations. Before you connect another service to a workspace that holds patient data, check that you have a BAA with that service.
- You decide what goes in the workspace. Talk to Coeffection if you are not sure.