Written and maintained by CASRAI Editorial Board
Published · Last updated
On this page
General information about how HIPAA’s definitions apply to an online store platform. It is not legal or medical advice; a privacy officer or counsel decides how the rules apply to a specific business.
Short answer
Shopify does not publish a “HIPAA compliant” status for its platform, and its Acceptable Use Policy says that certain business activities are not supported, “such as uploading Protected Health Information subject to HIPAA” (checked 1 November 2026). HIPAA itself regulates covered entities and business associates, not software brands, so the useful question is whether your store handles protected health information (PHI) and whether the vendor holding it is bound by a business associate contract.
What HIPAA actually regulates
The definitions in 45 CFR 160.103 (checked 1 November 2026) name who the rules bind. A covered entity is a health plan, a health care clearinghouse, or a health care provider that transmits health information electronically in connection with a transaction covered by the HIPAA rules. A business associate is a person who, on behalf of a covered entity and other than as a member of its workforce, creates, receives, maintains or transmits PHI for covered functions. The definition also reaches a subcontractor that creates, receives, maintains or transmits PHI on behalf of a business associate.
It follows that “HIPAA compliant” is not a certification a platform can hold in the abstract. A related distinction is covered in HIPAA-aware vs HIPAA-compliant, and the role definitions are explained in who counts as a HIPAA covered entity.
What Shopify’s policy says about PHI
Shopify’s Acceptable Use Policy (checked 1 November 2026) states that merchants must “respect that certain business activities are not supported by our platform, such as uploading Protected Health Information subject to HIPAA.” That is the policy’s own wording; this page draws no conclusion beyond it about contracts Shopify may or may not sign in particular cases.
HIPAA and Shopify: reading the two texts together
Under 45 CFR 164.308(b)(1) (checked 1 November 2026), a covered entity may permit a business associate to create, receive, maintain or transmit electronic PHI on its behalf only if it obtains satisfactory assurances, in accordance with 164.314(a), that the business associate will appropriately safeguard the information. Paragraph (b)(2) applies the same rule between a business associate and its subcontractor. Under 45 CFR 164.502(e), a business associate may use or disclose PHI only as its business associate contract permits.
Put side by side: the regulation requires written assurances before a vendor holds electronic PHI for a covered entity, and the platform’s own policy lists uploading HIPAA-covered PHI as unsupported. A store that needs the platform to hold PHI therefore has no basis in these two texts to assume it may.
When a store has a HIPAA problem: a decision test
| Question | Why it matters (source) |
|---|---|
| Is the business a health plan, clearinghouse, or a provider that transmits standard electronic transactions? | If not, it is not a covered entity under 45 CFR 160.103. |
| Is the business handling PHI on behalf of a covered entity? | If so it may be a business associate under 45 CFR 160.103. |
| Will the platform create, receive, maintain or transmit that PHI? | A vendor doing so for a business associate fits the subcontractor limb of the definition. |
| Is there a business associate contract or satisfactory assurance in place? | Required before electronic PHI is entrusted to the vendor (45 CFR 164.308(b)). |
| Does the platform’s policy allow the data type? | Shopify’s Acceptable Use Policy lists uploading PHI subject to HIPAA as unsupported. |
Checklist before using any e-commerce platform for health data
- Write down exactly which data fields the store collects and whether any of them is PHI for a covered entity.
- Ask the vendor in writing whether it enters into business associate contracts for the service in question; keep the answer on file.
- Identify every subcontractor in the chain (apps, payment, email, analytics) that would touch the data, since the definition in 160.103 extends to subcontractors.
- Check the vendor’s current acceptable use and terms pages, which can change.
- Escalate classification questions to your privacy officer or counsel.
Common misunderstandings
- “Compliant platform” is not a thing HIPAA grants. The rules attach to covered entities and business associates; see also PII vs PHI for why ordinary personal data is not automatically PHI.
- A store is not automatically a covered entity. Under the 160.103 definition, covered entity status depends on being a plan, clearinghouse, or provider transmitting covered electronic transactions.
- A vendor’s feature page is not a contract. Satisfactory assurances under 164.308(b) are what the regulation asks for.
FAQ
Is Shopify HIPAA compliant?
Shopify’s Acceptable Use Policy lists uploading PHI subject to HIPAA as an activity its platform does not support. HIPAA binds covered entities and business associates, so compliance depends on how a given store and vendor are bound; see the decision test above.
Can I use Shopify for HIPAA-covered data?
The policy wording above says uploading PHI subject to HIPAA is unsupported, and 45 CFR 164.308(b) requires satisfactory assurances before a vendor holds electronic PHI for you. Ask your privacy officer or counsel before relying on any platform for PHI.
Does HIPAA apply to every Shopify store?
No. Under 45 CFR 160.103 it applies to covered entities and their business associates. For a related platform example, see is REDCap HIPAA compliant and the HIPAA and HIPAA Privacy Rule entries.
Sources
- Shopify, Acceptable Use Policy, https://www.shopify.com/legal/aup (checked 1 November 2026).
- 45 CFR 160.103 (definitions), https://www.law.cornell.edu/cfr/text/45/160.103 (checked 1 November 2026).
- 45 CFR 164.308(b), https://www.law.cornell.edu/cfr/text/45/164.308 (checked 1 November 2026).
- 45 CFR 164.502(e), https://www.law.cornell.edu/cfr/text/45/164.502 (checked 1 November 2026).







