Is Shopify HIPAA Compliant? BAA and PHI Explained

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

Is Shopify HIPAA Compliant? BAA and PHI Explained

Kevin Henry

HIPAA

April 27, 2025

5 minutes read
Share this article
Is Shopify HIPAA Compliant? BAA and PHI Explained

Overview of HIPAA Compliance Requirements

HIPAA regulates how Covered Entities and Business Associates handle Protected Health Information (PHI), including electronic PHI (ePHI). You must control who can access data, limit what is collected, and document how information flows across systems and vendors.

The HIPAA Security Rule requires administrative, physical, and technical safeguards. In practice, you implement role-based access, encryption in transit and at rest, audit logging, incident response, and workforce training. A signed Business Associate Agreement (BAA) with each vendor that creates, receives, maintains, or transmits PHI is essential.

Strong Data Encryption Standards, secure authentication, and continuous monitoring reduce breach risk. Complement HIPAA with a Risk Management Framework that identifies threats, rates likelihood and impact, and guides mitigation, plus ongoing Compliance Auditing to verify controls are operating effectively.

Shopify’s Business Associate Agreement Policy

Shopify’s core commerce platform is not designed to handle PHI, and it does not generally offer a Business Associate Agreement. Without a BAA, Shopify should not be used to create, receive, maintain, or transmit PHI under HIPAA.

Even if a platform uses encryption and modern security practices, HIPAA hinges on legal and operational assurances. In the absence of a BAA and HIPAA-specific commitments, your Acceptable Use Policy and staff training should explicitly prohibit entering or storing PHI anywhere in Shopify, including products, customer records, order notes, tags, metafields, files, and support tickets.

Handling PHI Outside Shopify

Keep PHI out of the storefront and admin

Design your storefront so customers never submit PHI through Shopify-hosted pages. Avoid collecting symptoms, diagnoses, prescriptions, or treatment details in carts, forms, live chat, reviews, or post-purchase surveys. Do not place PHI in URLs, UTM parameters, or scripts.

Use secure channels for clinical or sensitive data

Route any clinical questions, medical documents, or refill details to a HIPAA-compliant portal, messaging system, or EHR-integrated form that signs a BAA. Share only non-PHI in Shopify, such as product availability, pricing, or shipping status. Reference orders by tokenized IDs rather than patient identifiers.

Minimize data and de-identify

Apply the minimum necessary standard: collect only what you need to fulfill an order and keep clinical context out of Shopify. Where possible, de-identify data or use pseudonymous tokens that point to PHI stored in a compliant system you control.

Integrating Third-Party HIPAA-Compliant Solutions

Architect integrations to keep PHI segregated

Embed HIPAA-compliant forms, chat, or scheduling via secure iframes or subdomains that bypass Shopify’s servers. Ensure the third party signs a BAA and meets the HIPAA Security Rule, including strong Data Encryption Standards and robust access controls.

Use tokens, not payloads

Pass only non-sensitive references from the storefront to backend systems. Store PHI in a compliant database or EHR; keep Shopify limited to catalog, payments, and logistics. Scrub webhooks, analytics, and logs so they never carry PHI.

Vet vendors and verify controls

Perform vendor risk assessments, review BAAs, and demand evidence of Compliance Auditing such as penetration tests and control reports. Confirm encryption practices, key management, retention, and incident response before go-live, and reassess annually.

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment

Risks of Non-Compliance on Shopify

Entering PHI into Shopify creates regulatory exposure, including civil penalties, breach notifications, and potential contractual repercussions with payers or partners. State privacy laws can add liabilities beyond HIPAA, raising both legal and reputational risks.

Operationally, PHI may propagate into caches, backups, search indexes, analytics pixels, CDNs, server logs, and third-party apps. Once dispersed, containment and forensics become complex and costly. Lack of a BAA also limits cooperation and assurances during incident response.

Alternative E-Commerce Platforms for HIPAA

If you must process PHI in commerce workflows, evaluate platforms or architectures that provide a BAA and HIPAA-focused controls. Options include healthcare-specific payment portals, patient commerce features within EHR ecosystems, or a headless storefront backed by HIPAA-eligible cloud services where you control data storage and access.

Assess each alternative against the HIPAA Security Rule, Data Encryption Standards, audit logging depth, access governance, and vendor support for Compliance Auditing. Ensure clear data boundaries so your storefront never exposes PHI to non-BAA systems.

Best Practices for HIPAA Compliance in E-Commerce

Build a defensible program

  • Map data flows end to end; classify PHI vs. non-PHI and remove PHI from Shopify touchpoints.
  • Adopt a Risk Management Framework to assess threats, prioritize controls, and track remediation.
  • Implement encryption in transit and at rest, with strong key management and least-privilege access.
  • Enforce an Acceptable Use Policy that bans PHI entry into non-BAA systems and trains staff accordingly.
  • Harden analytics and marketing tools; disable pixels and tags on pages that could reveal health information.
  • Conduct periodic Compliance Auditing, tabletop incident drills, and vendor reassessments.
  • Define retention and deletion for all systems, ensuring PHI is purged from non-compliant locations.

Conclusion

Shopify is a powerful retail platform, but without a Business Associate Agreement it should not handle Protected Health Information. Keep PHI in HIPAA-compliant systems, integrate through secure, segregated channels, and anchor your program in a clear Risk Management Framework with ongoing Compliance Auditing.

FAQs

Does Shopify sign a Business Associate Agreement for HIPAA compliance?

No. Shopify does not generally offer a Business Associate Agreement, so it should not be used to create, receive, maintain, or transmit PHI.

Can PHI be stored securely on Shopify’s platform?

No. Without a BAA and HIPAA-specific safeguards, PHI must not be stored or processed on Shopify. Keep all PHI in HIPAA-compliant systems that contractually and technically support the HIPAA Security Rule.

What steps can businesses take to ensure HIPAA compliance when using Shopify?

Prohibit PHI entry in Shopify via an Acceptable Use Policy, segregate clinical data into BAA-backed tools, tokenize references, harden analytics, and perform Compliance Auditing. Use a Risk Management Framework to validate controls and document decisions.

Are there HIPAA-compliant alternatives to Shopify available?

Yes. Consider healthcare-specific payment portals, EHR-integrated commerce features, or custom headless stores built on HIPAA-eligible cloud services that will sign a BAA and meet Data Encryption Standards and audit requirements.

Share this article

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment

Related Articles