ComplianceCheckup

Is Sprinklr GDPR Compliant?

Sprinklr privacy and compliance overview. Last scanned: 2 months ago.

Sprinklr scored 45/100 (grade F), indicating significant privacy issues. Key issues found: 2 tracking requests detected before consent. Tracking requests detected but no consent banner found. This is an automated technical assessment, not a legal compliance certification.

F

45/100

Privacy and compliance score

Scanned May 14, 2026 in fetch mode.

Pre-consent tracking

0/23

2 tracking requests detected before consent.

Cookie consent banner

0/12

Tracking requests detected but no consent banner found.

Security headers

0/10

4 security headers missing: Strict-Transport-Security (max-age >= 31536000), Content-Security-Policy, X-Content-Type-Options: nosniff, X-Frame-Options (or CSP frame-ancestors).

CCPA / CPRA disclosures

6/8

CCPA/CPRA partial: "Do Not Sell or Share" link detected, CCPA/CPRA language in privacy policy. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance.

Accessibility (WCAG 2.x AA)

7/15

Accessibility scan unavailable in fetch mode.

COPPA signal

5/5

No COPPA language detected.

Privacy policy

10/10

Privacy policy found, substantial, recently updated, and covers user rights.

DPA and sub-processor list

7/7

DPA reference and sub-processor list both found.

AI training stance

5/5

AI training opt-out disclosure found in privacy policy.

Hosting region disclosure

5/5

Data hosting region disclosed in privacy policy.

How does Sprinklr compare on privacy?

#37 of 38
in Social / Marketing
#794 of 904
across all tools
Top 88%
overall percentile
61/100
Social / Marketing average (this tool: 45/100)

Top-ranked Social / Marketing tools:

See all 38 Social / Marketing tools ranked →

Does Sprinklr self-report SOC 2, HIPAA, or PCI compliance?

The following is based on Sprinklr's public documentation. ComplianceCheckup has not independently audited these claims.

StandardStatus
SOC 2Type II certified
HIPAANot publicly documented for Sprinklr
PCI DSSNot publicly documented for Sprinklr
GDPRSee scan results above
CCPASee scan results above

Frequently asked questions about Sprinklr compliance

Is Sprinklr GDPR compliant?

Sprinklr received a privacy grade of F (45/100) in our automated scan. 2 tracking requests detected before consent. Tracking requests detected but no consent banner found. For a complete GDPR assessment, consult a qualified privacy professional.

Does Sprinklr offer a Data Processing Agreement (DPA)?

Yes. Sprinklr provides a DPA linked in the Legal documents section above. Review it carefully and sign before transferring personal data.

Is Sprinklr SOC 2 certified?

Sprinklr holds a SOC 2 Type II certification.

What pre-consent tracking did we find on Sprinklr?

2 tracking requests detected before consent. Pre-consent tracking means scripts or cookies run before users accept or decline the cookie banner, which may violate GDPR Article 5(1)(a). ComplianceCheckup detected this via an automated headless browser scan.

What are Sprinklr's biggest privacy risks?

Based on our automated scan, the top areas of concern are: Pre-consent tracking, Cookie consent banner, CCPA / CPRA disclosures. 2 tracking requests detected before consent. These findings are automated and may not capture all risks.

How does Sprinklr handle CCPA?

CCPA/CPRA partial: "Do Not Sell or Share" link detected, 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.