---
title: "Is GoHighLevel HIPAA compliant? A telehealth CRM guide"
description: "GoHighLevel is not HIPAA compliant by default. What its $297 add-on and HubSpot's BAA cover, A2P texting rules, and the CRM setup that keeps charts out."
canonical: "https://cuvo.co/blog/gohighlevel-hipaa-telehealth-crm"
last-updated: "Nov 15, 2026"
keywords: ["hipaa compliant crm", "is gohighlevel hipaa compliant", "go high level hipaa compliance", "gohighlevel hipaa", "is hubspot hipaa compliant", "hipaa compliant texting", "hipaa compliant sms", "telehealth crm"]
---
# Is GoHighLevel HIPAA compliant? A telehealth CRM guide

By Priya Raman, Director of Partner Growth. Published Nov 15, 2026. Growth.

GoHighLevel and HubSpot can both sign a business associate agreement, but neither is HIPAA compliant out of the box, and neither is the place for a telehealth patient's chart. This guide sets out what each vendor's own documentation says as of November 15, 2026, when a marketing list becomes protected health information, how texting and tracking pixels fit the rules, and the split that keeps lifecycle marketing running without moving clinical data. The verdict: run the clinic on Cuvo Health, which keeps the chart under a BAA signed on every plan and syncs patients, orders and revenue events to GoHighLevel or HubSpot on Grow and Enterprise.

Cuvo Health is the clinic platform to put behind GoHighLevel or HubSpot, because the chart stays on Cuvo's HIPAA-compliant infrastructure under a business associate agreement signed on every plan, while native sync on Grow and Enterprise sends the CRM patients, orders and revenue events. GoHighLevel is not HIPAA compliant by default: HighLevel sells an account-wide HIPAA add-on at $297 a month that adds a signed BAA, encryption of ePHI, audit logging and MFA enforcement, and it cannot be cancelled once enabled, as of November 15, 2026. HubSpot supports HIPAA only on Enterprise editions, after a Super Admin turns on Sensitive Data and accepts HubSpot's BAA. Either tool can sit in a compliant stack. Neither replaces the clinic system of record, and every CRM that receives patient data from the practice needs its own BAA.

**Key takeaways**
- The pick: Cuvo Health: the chart stays on Cuvo under a BAA signed on every plan, with GoHighLevel, HubSpot and customer.io sync on Grow and Enterprise
- GoHighLevel: Not HIPAA compliant by default. The HIPAA add-on is $297 a month, account-wide and permanent once enabled, as of November 15, 2026
- HubSpot: HIPAA support on Enterprise editions only, after Sensitive Data is turned on and the BAA accepted; SMS is not on its covered-feature list
- The rule: Any CRM that receives patient data from the practice or its platform needs a BAA and should get only the minimum necessary
- Texting: Register A2P 10DLC, get written consent for marketing texts, honor opt-outs within ten business days, keep medication names and offers out of SMS

**Who this is for**
- Agencies and media buyers: Operators who build funnels in GoHighLevel and are adding a prescription program for a client
- Brands on HubSpot: Teams whose sales and marketing already run in HubSpot and need patient events without patient charts
- Brands switching platforms: Operators moving a patient list and its automations off a platform that boxed them in
- Clinicians with a marketing partner: Nurse practitioners and physicians whose partner runs the ads and the follow-up

**GoHighLevel, HubSpot, a generic CRM and Cuvo's clinic tools, as of November 15, 2026**

| Tool | BAA available | What it should hold | Texting | Role separation |
| --- | --- | --- | --- | --- |
| **Cuvo Health (clinic platform tools)** | **Signed on every plan** | **The system of record: intake answers, charts, prescriptions, orders and patient messages** | **Refill, shipping and check-in texts on every plan; SMS sequences with opt-out handling and iMessage on Grow and Enterprise** | **Role-based access on Grow and Enterprise; audit logging on Grow, Enterprise and Cuvo Prescribe; two-factor sign-in on every console account** |
| **GoHighLevel** | With the HIPAA add-on, $297 a month, account-wide; not compliant by default | Leads, funnels and campaign contacts; clinic data only on a HIPAA-enabled sub-account, never the chart | SMS after A2P 10DLC brand and campaign registration; SMS and MMS are among the objects the add-on lists as able to store PHI | User permissions; the add-on enables audit logging and MFA enforcement |
| **HubSpot** | Enterprise editions only, after a Super Admin turns on Sensitive Data and accepts the BAA | Contacts and deals; PHI only in properties flagged as PHI and used in covered features | SMS is not among the features HubSpot lists as covered for sensitive data | Super Admin controls Sensitive Data settings; access settings per sensitive property |
| **Generic CRM without a BAA** | None | Leads the brand collected itself, with no patient status, orders or health answers | Account and promotional texts under its own registration, with no health information | Whatever the tool offers, with no HIPAA safeguards to rely on |

> **Our recommendation** Run the clinic on Cuvo Health and keep GoHighLevel or HubSpot for what they do well: landing pages, lead capture, pipelines and campaigns. Cuvo holds the intake, the chart and the prescription under a BAA signed on every plan, and Grow, at $2,500 a month after a $15,000 setup, syncs patients, orders and revenue events to GoHighLevel, HubSpot or customer.io. Before any clinic data reaches the CRM, put that account on the vendor's HIPAA terms. A brand without an agency or a CRM can run lifecycle messaging inside Cuvo on Grow and skip the extra tool. Brands still choosing a clinic platform can read Cuvo's [white label telehealth platforms ranked](/blog/best-white-label-telehealth-platforms).

> **Map your CRM to the clinic on one call** Bring your GoHighLevel or HubSpot setup. Cuvo shows which events sync, on which plan, and what stays in the chart. [Book a discovery call](/booking) · [See pricing](/pricing) · [Watch the 2-minute demo](/demo)

## 01. Is GoHighLevel HIPAA compliant?

Not by default, and HighLevel says so itself. Go High Level HIPAA compliance is a paid add-on: the company's help center article on HIPAA compliance, last modified November 10, 2026, states that HighLevel accounts are not HIPAA compliant by default and offers an optional, account-wide HIPAA package at US$297 a month, billed at the agency level and open to agencies on any plan. HighLevel's pricing page lists the same $297 add-on and includes HIPAA compliance in its Enterprise plan, as of November 15, 2026. The package enables encryption of ePHI, a business associate agreement, audit logging and MFA enforcement.

Read the terms before buying. The package cannot be cancelled, refunded, removed or downgraded once enabled. The BAA is signed inside the account, under Settings, Compliance, and HIPAA is then switched on for each sub-account in its Advanced Settings, with no way to switch it back. The article lists the objects that can store PHI under the package: contacts, notes, custom fields, SMS and MMS, voice recordings, email bodies and attachments, form and survey submissions, calendars and invoices.

The article does not say which channels or features sit outside the BAA, so ask HighLevel in writing before patient data touches social inboxes, WhatsApp or AI features. It frames the roles plainly: the practice is the covered entity, HighLevel and the agency are business associates, and an agency that gives its client practice its own BAA must itself comply with HIPAA. On Cuvo the chart never has to enter GoHighLevel; the [two-way GoHighLevel sync](/integrations) moves the lifecycle data a funnel needs.

## 02. Is HubSpot HIPAA compliant, and on which plans?

HubSpot supports HIPAA on Enterprise editions only. Its knowledge base article on storing sensitive data, updated September 21, 2026, lists the Enterprise editions of Marketing, Sales, Service, Data, Content, Smart CRM and Revenue Hub. A Super Admin turns the feature on under Settings, Security, Sensitive Data, selects Health/Medical Data and the box confirming the company is a HIPAA covered entity or business associate, and accepts the Sensitive Data Terms and the Business Associate Agreement.

The customer then has work to do. Every property that will hold PHI is created as a sensitive property with the PHI box checked, a setting that cannot be changed later, and sensitive properties do not work in personalization tokens, sandboxes, chatbots or playbooks. HubSpot's terms apply its BAA only to services HubSpot has authorized for PHI, and its product catalog names those services, including properties, imports, the object APIs, notes, calls, one-to-one emails, forms, integrations, lists and workflows. SMS and marketing email are not on that list, as of November 15, 2026.

On Cuvo, HubSpot receives patients, orders and revenue events through the native integration on Grow and Enterprise, so a team that keeps HubSpot for sales and marketing works from clinic data without holding intake answers.

## 03. When does a CRM list become protected health information?

When it carries health information the practice or its platform created or received. HIPAA's definition at 45 CFR 160.103 covers information, including demographic information, created or received by a health care provider that relates to a person's health, the care they receive or payment for that care, and that identifies them. A lead list the brand collected on its own landing page usually falls outside it; the same contact tagged as a patient, with an intake status, an order or a refill date sent from the clinic, falls inside. Cuvo's guide to [HIPAA business associate agreements](/blog/hipaa-business-associate-agreement-telehealth-brand) covers the vendor-by-vendor version.

Three rules then apply to the CRM and to whoever sends it data:

- Business associate agreement: a covered entity may let a vendor create, receive, maintain or transmit PHI only with satisfactory assurance, documented in a written contract that meets 45 CFR 164.504(e), and a business associate must get the same from its subcontractors (45 CFR 164.502(e)). A CRM that receives clinic data is one of those vendors.
- Marketing authorization: using or disclosing PHI for marketing requires the patient's written authorization (45 CFR 164.508(a)(3)), except for face-to-face communications and promotional gifts of nominal value. The definition at 164.501 leaves out refill reminders about a drug currently prescribed, where any payment is reasonably related to the cost of sending, and communications describing the covered entity's own health-related products or services, unless a third party pays for them.
- Minimum necessary: covered entities and business associates must make reasonable efforts to limit PHI to the minimum necessary for the purpose of each use, disclosure or request (45 CFR 164.502(b)).

In practice, a refill reminder or a message about the practice's own program usually sits outside the marketing definition, while a list shared to promote a third party's product, or anything a third party pays to send, needs authorization. The CRM should receive the fields that run the campaign and nothing more, and the brand's own surfaces can still fall under the [FTC's health privacy and advertising rules](/blog/ftc-rules-for-telehealth-subscriptions-and-health-ads). This is general information, not legal advice.

## 04. What does HHS say about tracking pixels after the 2024 ruling?

The HHS Office for Civil Rights bulletin on online tracking technologies still stands, minus one part. On June 20, 2024, in American Hospital Association v. Becerra, the Northern District of Texas vacated the guidance to the extent it said HIPAA obligations are triggered when a technology connects an IP address with a visit to an unauthenticated public page about specific health conditions or providers. The notice at the top of the bulletin says HHS is evaluating its next steps, as of November 15, 2026.

The rest of the bulletin remains HHS's published position. Tracking on login-protected pages, such as a patient portal or a telehealth platform, generally has access to PHI. A tracking vendor that receives PHI is a business associate and needs a BAA. Cookie banners are not a valid HIPAA authorization. Tracking on an unauthenticated page where someone schedules care or enters symptoms may collect PHI, because what the person types is identifiable health information.

On Cuvo, the console's Integrations page connects the brand's Google Analytics 4 property, its Meta pixel and Conversions API token, and its own Google Tag Manager container. Browser tags load only on the storefront home page and the intake funnels, never on the patient portal, sign-in, password reset or visit links. The container receives four events, generate_lead, begin_checkout, purchase and funnel_step, carrying opaque ids, amounts and, on leads and purchases, SHA-256 hashes of email and phone for Enhanced Conversions; no event carries a treatment, medication, product or funnel name, the page path or raw contact details.

Cuvo's servers also report to GA4 and Meta the conversions no browser sees: the sale once the charge is captured after clinician approval, renewals, and refunds (to GA4 only), with amounts, order ids, browser identifiers and hashed contact details, and nothing about what the patient is treated for. UTM tags and ad click ids are saved to the patient record at intake and at checkout. Whether a given event counts as PHI for a given brand is a question for its counsel, and the brand chooses what to switch on. One setting sits with the brand: name funnel links after a campaign rather than a medication or condition, because tags in its own container can read the page address. Ad platform data limits are in Cuvo's guide to [LegitScript for Meta and Google ads](/blog/legitscript-certification-for-meta-and-google-ads).

> **See the tracking setup before you run ads** A discovery call walks through the Tag Manager container, the server-side events and which ones your counsel wants switched on. [Book a discovery call](/booking) · [See integrations](/integrations) · [Watch the 2-minute demo](/demo)

## 05. HIPAA compliant texting and SMS: what the rules require

HIPAA compliant texting has two parts: what the message says, and which registered account sends it. Whichever account sends a text carries its registration. A2P 10DLC is the carrier registration framework for business texts sent to US recipients from standard local numbers. HighLevel's help center describes its two parts, a brand that says who is sending and a campaign that says what is being sent, with carriers and their registration partners making the final decision. Health brands meet stricter rules than most:

- Prescription content: Twilio's list of forbidden message categories for the US and Canada bars promotional messaging for drugs that cannot be sold over the counter, even when the sender is a licensed professional, and Twilio rejects 10DLC campaigns that promote prescription medications with no option to resubmit. Its rejection notice adds that refill reminders from a licensed pharmacy to existing patients may be permissible under a different use case.
- Consent: CTIA's Messaging Principles and Best Practices (May 2023) expect consent for any business text and express written consent for marketing texts, and say an opt-in applies only to the sender and campaigns it was collected for. The FCC's rule at 47 CFR 64.1200 requires prior express written consent for telemarketing calls and texts sent with an autodialer, with an exception for health care messages sent by or for a HIPAA covered entity or business associate.
- Opt-out: under the same FCC rule a person can revoke consent by any reasonable means, including replying stop, quit, end, revoke, opt out, cancel or unsubscribe, and the request must be honored within a reasonable time not to exceed ten business days. CTIA adds one final confirmation text, with nothing sent after it.
- What goes in the text: HHS lets providers message patients electronically with reasonable safeguards and, for unencrypted email, points to limiting the amount or type of information sent. For HIPAA compliant SMS the practical reading is a text that says something is ready and leaves the details to the secure portal.

For a telehealth brand, promotional texts about a prescription program are barred on carrier routes, so lifecycle texts read as account and care notices without medication names or offers. If GoHighLevel and the clinic both text the same patient, each sender needs its own registration and its own consent record. On Cuvo, refill, shipping and check-in texts go out under the brand's name on every plan, SMS sequences on Grow and Enterprise have opt-out handling built in, iMessage runs through Apple Messages for Business on Grow and Enterprise, and files attached to a text conversation appear in the patient portal rather than in the text. The console lists Twilio and GoHighLevel among the apps a clinic connects itself, so settle on the discovery call which account sends each patient text.

## 06. What should the CRM hold, and what stays in the clinic?

The clinic system of record holds the chart; the CRM holds the events that run lifecycle marketing. That split answers both the business associate rule and the minimum necessary standard, and it keeps the marketing team in the tools it already knows. It is also how the [white label telehealth model](/blog/what-is-a-white-label-telehealth-platform) is built. On Cuvo, intake answers, charts and prescriptions stay on Cuvo's HIPAA-compliant infrastructure. The brand owns the patient relationship, the customer list and every business record, all exportable at any time, and medical charts belong to the treating professional corporation and its licensed clinicians, as HIPAA and state law require.

**The minimum each lifecycle event should send to a CRM**

| Lifecycle event | What the CRM receives | What stays in the clinic system |
| --- | --- | --- |
| **Lead created** | Name, email, phone, the consent record and the campaign source | Nothing clinical exists yet |
| **Intake started or submitted** | A stage: started or submitted | Every intake answer, identity check and consent document |
| **Provider decision** | A stage: approved, or closed with no reason given | The clinician's review, the reason and the chart note |
| **Order placed** | Order id, amount and subscription status | Medication, dose and the pharmacy record |
| **Refill due** | The date the next check-in opens | The refill authorization and any dose change |
| **Cancelled or lapsed** | Status and date, for win-back timing | Any clinical reason for stopping |

A stage tied to a named person can still be PHI once the clinic sends it, so the CRM that receives these events needs a BAA; the list limits exposure, it does not take the CRM out of HIPAA. Campaigns keyed to these stages should promote the brand's own program, never a third party's product, unless counsel has cleared an authorization. On Cuvo, the native sync on Grow and Enterprise carries patients, orders and revenue events, and signed webhooks deliver consult, order, shipment and payment events, 32 event types in all, so an engineer can pass a CRM exactly the fields counsel approves.

## 07. Can marketing staff be kept away from medical data?

Yes, and the cleanest way is to keep them out of the clinic console entirely. Marketers and agencies work in the CRM and the ad platforms on the events above; the people who answer patients and manage orders work in the console. On Cuvo's Grow and Enterprise plans, role-based access control gives every teammate a role: Admin for everything, including members, API keys and billing; Manager for day-to-day work plus refunds, billing and integrations; Staff for patients, orders and messages; and Viewer, read-only. Cuvo's own guidance is to pick the lowest role that lets someone do the job.

Other controls back the roles. Audit logging on Grow, Enterprise and Cuvo Prescribe records every access and change to patient data. Two-factor authentication is required on every console account, SAML single sign-on comes on every plan, only Admins and Managers open the Integrations page, and only Admins create API keys. The reviewing clinician keeps the clinical chart, so medications cannot be edited from the console. Patient messages split at the source as well. A patient picks a topic before writing; order, billing and account topics go to the brand's team, while side effects, dosing, refills and lab results go to a thread the treating clinician answers.

## 08. How do GoHighLevel and HubSpot connect to Cuvo?

Through native integrations on Grow, at $2,500 a month after a $15,000 setup, and on Enterprise. Cuvo syncs both ways with GoHighLevel, so agency-built funnels and follow-ups run on live clinic data; streams patients, orders and revenue events into HubSpot for sales and marketing teams; and sends clinic events to customer.io for lifecycle campaigns. Launch, at $997 a month after a $9,800 setup, does not include CRM sync. Every plan charges $25 per completed consult with no revenue share, month to month after setup, as published on [Cuvo's pricing page](/pricing).

Any other CRM, or a custom flow, connects through the Cuvo Integrations API on Grow, Enterprise and Cuvo Prescribe: a published OpenAPI 3.1 contract with 65 operations, HMAC-signed webhooks with 32 versioned event types and redelivery, and an MCP server with 46 tools for AI agents. Test keys reach a sandbox first, and live keys open once the integration accepts Cuvo's business associate agreement. The [telehealth API page](/telehealth-api) lists the endpoints.

A typical agency setup keeps the top of the funnel in GoHighLevel: ad landers, lead capture, pipelines and sales follow-up. Intake, provider review, prescribing and refills run on Cuvo, and the two-way sync streams patients, orders and revenue events back into GoHighLevel so the next campaign knows who converted. If those events land in a GoHighLevel sub-account, that sub-account belongs on HighLevel's HIPAA add-on with its BAA signed.

## 09. Do you still need a separate CRM next to Cuvo?

Often not. The console covers the core of a patient CRM: a Leads list of people who have not yet converted, patient records with journey stages from forms through review and approval, a shared inbox where portal messages and texts land grouped by patient with assignment, tags and internal notes, and the brand's own discount codes. On Grow and Enterprise, the no-code journey builder sends email, SMS and iMessage sequences targeted by treatment status, order history and any attribute the brand chooses, including onboarding nudges for people who signed up but have not placed a first order. Cuvo lays out the [retention tools by plan](/retention).

AI fits the same pattern. Cuvo's MCP server connects an AI assistant to the clinic's data and workflows under the same scopes and audit log as the API, and topic routing keeps medical questions with clinicians; Cuvo's guide to [where AI stops in patient messaging](/blog/patient-inbox-clinical-escalation) draws the line. The CRM decision comes down to six cases:

- Keep GoHighLevel or HubSpot when an agency already runs the ad landers, pipelines and sales follow-up there, and connect it through Grow's native sync.
- Keep it when the brand sells products or services outside the prescription program and one list serves both.
- Keep it when a sales team works partner or wholesale deals that never touch a patient.
- Skip it when the marketing is patient lifecycle messaging: onboarding, refill reminders and win-back run on Grow from the system that holds the refill.
- Skip it when the team is small and nobody would maintain a second tool and a second BAA.
- Use the API when engineers want a CRM outside the native list or a custom flow between systems.

**Best for**
- Agency running funnels in GoHighLevel: Cuvo Grow: two-way GoHighLevel sync, with the chart kept on Cuvo
- Brand whose team lives in HubSpot: Cuvo Grow: patients, orders and revenue events streamed into HubSpot
- Brand with no CRM yet: Cuvo Grow: leads, journey stages and email, SMS and iMessage sequences inside the console
- Team with engineers and a custom stack: Cuvo Grow or Cuvo Prescribe: the API, signed webhooks and the MCP server
- Operator with several brands: Cuvo Enterprise: unlimited brands on one account and custom-built integrations
- Clinician with a marketing partner: Cuvo Health: the partner runs campaigns from the CRM while patient data stays in the clinic system

## How to choose a HIPAA compliant CRM for telehealth

Get these answers in writing from the clinic platform and from every CRM vendor before patient data moves:

1. Does each tool that will receive patient data sign a BAA, and on which plan?
2. Which features and channels does that BAA cover?
3. Which fields and events will the clinic send to the CRM, and who approved the list?
4. Which account sends each patient text, under whose A2P 10DLC brand and campaign, and where is consent recorded?
5. Which pages load tracking tags, and what do the conversion events carry?
6. Which roles can open clinical data, and is every access logged?
7. Can every record export, and who owns the patient relationship and the customer list?

Cuvo answers this list on its discovery call and publishes most of it: a BAA on every plan, native GoHighLevel, HubSpot and customer.io sync on Grow and Enterprise, tracking tags kept off the patient portal, role-based access on Grow and Enterprise, audit logging on Grow, Enterprise and Cuvo Prescribe, and full export at any time.

> **Connect your CRM without moving the chart** Cuvo maps your GoHighLevel or HubSpot setup to the events, the plan and the BAA that fit, at published pricing. [Book a discovery call](/booking) · [See integrations](/integrations) · [Watch the 2-minute demo](/demo)

## Frequently asked questions

**Q: Is GoHighLevel HIPAA compliant?**

A: Not by default. HighLevel sells an account-wide HIPAA add-on at $297 a month, billed at the agency level, that adds a signed BAA, encryption of ePHI, audit logging and MFA enforcement, and it cannot be cancelled once enabled, as of November 15, 2026. On Cuvo, the chart stays on Cuvo's HIPAA-compliant infrastructure, and GoHighLevel receives the lifecycle data its funnels need through two-way sync on Grow and Enterprise.

**Q: Is HubSpot HIPAA compliant?**

A: HubSpot supports HIPAA on Enterprise editions only, after a Super Admin turns on Sensitive Data, confirms the company is a covered entity or business associate and accepts HubSpot's BAA, and each PHI property must be flagged when it is created. SMS and marketing email are not among the features HubSpot lists as covered for sensitive data, as of November 15, 2026. On Cuvo, HubSpot receives patients, orders and revenue events on Grow and Enterprise, without the chart.

**Q: What is the best HIPAA compliant CRM for a telehealth brand?**

A: Cuvo Health, paired with the CRM the team already uses. Cuvo keeps the intake, chart and prescriptions under a BAA signed on every plan and syncs patients, orders and revenue events to GoHighLevel, HubSpot or customer.io on Grow and Enterprise. A CRM is the wrong place for the chart whichever BAA it signs, and a brand without a CRM can run leads, journeys and patient messaging inside Cuvo on Grow.

**Q: GoHighLevel integration: how does that work?**

A: Cuvo syncs both ways with GoHighLevel on Grow, at $2,500 a month after a $15,000 setup, and on Enterprise, so agency-built funnels and follow-ups run on live clinic data. GoHighLevel keeps the landing pages, lead capture and pipelines, and Cuvo runs intake, provider review, prescribing and refills. A GoHighLevel sub-account that receives clinic data should run on HighLevel's HIPAA add-on with its BAA signed.

**Q: Do I still need GoHighLevel if the platform has funnels and messaging built in?**

A: Not always. On Cuvo Grow the console holds leads and patient journey stages, a shared inbox, discount codes, and email, SMS and iMessage sequences targeted by treatment status and order history, so a brand without an agency can run lifecycle marketing without a second tool. Keep GoHighLevel when an agency already runs ad landers, pipelines and sales follow-up there, and connect it through Cuvo's native sync.

**Q: How is A2P texting handled when we connect HighLevel?**

A: Each account that sends texts needs its own A2P 10DLC brand and campaign registration and its own consent record, because an opt-in collected for one sender does not carry to another. Carrier rules bar promotional texts for prescription drugs, so lifecycle texts should read as account and care notices with no medication names. On Cuvo, refill, shipping and check-in texts go out on every plan and SMS sequences on Grow and Enterprise handle opt-outs; confirm on the discovery call which account sends each patient text.

**Q: Is texting patients HIPAA compliant?**

A: It can be, when the text carries no clinical detail and the sender holds consent. HHS lets providers message patients electronically with reasonable safeguards, carrier rules bar promotional texts for prescription drugs, and the FCC requires an opt-out to be honored within ten business days, as of November 15, 2026. HIPAA compliant texting therefore means a notice that something is ready, with the details in the secure portal. On Cuvo, refill, shipping and check-in texts go out under the brand's name on every plan.

**Q: Can marketing staff be kept away from medical data?**

A: Yes. On Cuvo's Grow and Enterprise plans, role-based access control gives each teammate the lowest role that fits (Admin, Manager, Staff or Viewer), audit logging records every access to patient data, and two-factor sign-in is required on every console account. The simplest separation keeps marketers in the CRM, which receives lifecycle events, and out of the clinic console.

**Q: How do you track ad conversion events and send them back to Meta?**

A: On Cuvo, the brand connects its Meta pixel and Conversions API token, its GA4 property and its own Google Tag Manager container, and browser tags load only on the home page and intake funnels, never the patient portal. Cuvo's servers send lead, checkout, approved sale and renewal events to Meta with amounts, order ids and hashed contact details, and no treatment, medication or intake answers. The brand's counsel decides which events to switch on.

**Read next**
- [Telehealth marketing: how brands get patients](/blog/telehealth-marketing-how-brands-get-patients): Channels, budget arithmetic and how to vet an agency
- [Telehealth affiliate programs: rules and setup](/blog/telehealth-affiliate-programs): Referral laws, FTC rules and a launch checklist
- [White label telehealth for agencies and resellers](/solutions/agencies): One brand or a full book of client brands
- [Integrations](/integrations): HubSpot, GoHighLevel and customer.io sync, the API and webhooks, by plan
- [Patient retention and refill journeys](/retention): Email, SMS and iMessage journeys and opt-out handling
- [HIPAA business associate agreements for telehealth brands](/blog/hipaa-business-associate-agreement-telehealth-brand): Which vendors need one, and what it must say
- [LegitScript for Meta and Google ads](/blog/legitscript-certification-for-meta-and-google-ads): Ad accounts, pixel limits and what certified ads may say
- [HIPAA-compliant patient messaging](/blog/patient-inbox-clinical-escalation): Who answers, what escalates, and where AI stops
- [Who owns the patients and data in white label telehealth?](/blog/who-owns-the-patients-and-data-on-a-white-label-telehealth-platform): Patients, records, charts, cards and export
- [Telehealth API](/telehealth-api): OpenAPI 3.1 contract, signed webhooks, sandbox and MCP
- [Pricing](/pricing): CRM sync, API, role-based access and the BAA, by plan

**Sources**
- [HIPAA Compliance in HighLevel](https://help.gohighlevel.com/support/solutions/articles/48000983084-hipaa-compliance-with-highlevel): HighLevel help center, modified November 10, 2026: not compliant by default, $297 a month, BAA, sub-account enablement, objects that can store PHI
- [HighLevel pricing](https://www.gohighlevel.com/pricing): HIPAA compliance add-on at $297 a month; included in the Enterprise plan, read November 15, 2026
- [US phone number registrations (A2P 10DLC)](https://help.gohighlevel.com/support/solutions/articles/155000002380-what-is-a2p-10-dlc-brand-and-campaign-registration): HighLevel help center, modified September 4, 2026: brand and campaign registration
- [Store sensitive data in HubSpot](https://knowledge.hubspot.com/account-security/store-sensitive-data): HubSpot knowledge base, updated September 21, 2026: Enterprise editions, Super Admin, HIPAA and BAA settings, limits
- [Sensitive Data Additional Terms](https://legal.hubspot.com/sensitive-data-terms): HubSpot, last modified April 14, 2026: covered services and the BAA annex
- [HubSpot Products and Services Catalog](https://legal.hubspot.com/hubspot-product-and-services-catalog): Sensitive Data Covered Services list, read November 15, 2026
- [45 CFR 160.103: definitions](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103): Individually identifiable health information, protected health information, business associate (eCFR)
- [45 CFR 164.501: definitions](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.501): The definition of marketing and its exclusions (eCFR)
- [45 CFR 164.502: uses and disclosures](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.502): Minimum necessary (b) and disclosures to business associates (e) (eCFR)
- [45 CFR 164.504: business associate contracts](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.504): Required contract terms, paragraph (e) (eCFR)
- [45 CFR 164.508: authorization required](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.508): Authorization for marketing, paragraph (a)(3) (eCFR)
- [Use of online tracking technologies by HIPAA covered entities and business associates](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html): HHS Office for Civil Rights bulletin, with the notice on Am. Hosp. Ass'n v. Becerra (N.D. Tex. June 20, 2024)
- [HIPAA FAQ: e-mail with patients](https://www.hhs.gov/hipaa/for-professionals/faq/570/does-hipaa-permit-health-care-providers-to-use-email-to-discuss-health-issues-with-patients/index.html): HHS: reasonable safeguards, limiting information in unencrypted messages
- [Forbidden message categories in the US and Canada](https://help.twilio.com/articles/360045004974-Forbidden-message-categories-for-SMS-and-MMS-in-the-US-and-Canada): Twilio: promotional messaging for prescription drugs forbidden
- [Error 30941: prescription drug or controlled substance content](https://www.twilio.com/docs/api/errors/30941): Twilio, modified October 27, 2026: 10DLC campaign rejection, no resubmission
- [Messaging Principles and Best Practices](https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf): CTIA, May 2023: consent levels, opt-out handling, non-transferable opt-ins
- [47 CFR 64.1200: delivery restrictions](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200): FCC TCPA rule: written consent for telemarketing, revocation within ten business days (eCFR)

*General information only: This guide is general information for brand owners, agencies and operators, not legal advice. Vendor plans, prices and terms restate HighLevel's and HubSpot's own pages as of November 15, 2026 and can change; confirm them with each vendor in writing. Regulatory statements restate the HIPAA Privacy Rule, the FCC's TCPA rule, HHS guidance and carrier messaging guidelines as published on November 15, 2026, and whether a given data flow is protected health information depends on facts the brand's counsel should review. Every clinical decision rests with the treating licensed provider. Cuvo makes no representation about revenue or patient volume.*

**Terms in this guide**
- [Protected health information (PHI)](/glossary/protected-health-information)
- [Covered entity (HIPAA)](/glossary/covered-entity)
- [Business associate agreement (BAA)](/glossary/business-associate-agreement)
- [Professional corporation (PC) and PLLC](/glossary/professional-corporation)
- [LegitScript certification](/glossary/legitscript-certification)
- [Revenue share (telehealth platforms)](/glossary/telehealth-platform-revenue-share)

Canonical page: https://cuvo.co/blog/gohighlevel-hipaa-telehealth-crm
