Is Medusa.js GDPR Compliant?
Medusa.js privacy and compliance overview. Last scanned: 1 months ago.
Medusa.js scored 74/100 (grade C), with 2 passing signal(s) and 4 area(s) needing attention. Top area to address: CCPA/CPRA partial: CCPA/CPRA language in privacy policy. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance. This is an automated technical assessment, not a legal compliance certification.
74/100
Privacy and compliance score
Scanned June 12, 2026 in fetch mode.
Security headers
3/103 security headers missing: Content-Security-Policy, X-Content-Type-Options: nosniff, X-Frame-Options (or CSP frame-ancestors).
CCPA / CPRA disclosures
3/8CCPA/CPRA partial: CCPA/CPRA language in privacy policy. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance.
Privacy policy
8/10Privacy policy found but may be incomplete or outdated.
DPA and sub-processor list
3/7Sub-processor list found, but no DPA reference detected.
Cookie consent banner
12/12No tracking detected: consent banner not required.
Accessibility (WCAG 2.x AA)
7/15Accessibility scan unavailable in fetch mode.
AI training stance
5/5No AI training disclosure found.
COPPA signal
5/5No COPPA language detected.
Pre-consent tracking
23/23No third-party trackers detected before consent.
Hosting region disclosure
5/5Data hosting region disclosed in privacy policy.
How does Medusa.js compare on privacy?
Top-ranked E-commerce tools:
See all 41 E-commerce tools ranked →Does Medusa.js self-report SOC 2, HIPAA, or PCI compliance?
The following is based on Medusa.js's public documentation. ComplianceCheckup has not independently audited these claims.
Frequently asked questions about Medusa.js compliance
Is Medusa.js GDPR compliant?
Medusa.js received a privacy grade of C (74/100) in our automated scan. 3 security headers missing: Content-Security-Policy, X-Content-Type-Options: nosniff, X-Frame-Options (or CSP frame-ancestors). For a complete GDPR assessment, consult a qualified privacy professional.
Does Medusa.js offer a Data Processing Agreement (DPA)?
No DPA link was found in our directory for Medusa.js. Check their legal or trust center page, or contact their sales team to request a DPA under GDPR Article 28.
Is Medusa.js SOC 2 certified?
No SOC 2 certification was found in our directory for Medusa.js. Check their trust center or security page for current status.
What are Medusa.js's biggest privacy risks?
Based on our automated scan, the top areas of concern are: CCPA / CPRA disclosures, Security headers, Privacy policy. CCPA/CPRA partial: CCPA/CPRA language in privacy policy. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance. These findings are automated and may not capture all risks.
How does Medusa.js handle CCPA?
CCPA/CPRA partial: CCPA/CPRA language in privacy policy. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance. CCPA requires businesses handling California residents' data to disclose data practices, honor opt-out requests, and support the Global Privacy Control (GPC) signal. Our scan checks for GPC support and CCPA-relevant cookie disclosures.
Not legal advice. The scan grade is an automated technical assessment and does not constitute legal or compliance advice. Self-reported claims have not been independently verified. Results may contain false positives or miss issues that cannot be detected programmatically. Consult a qualified attorney or compliance professional for your specific situation.