Is Incident.io GDPR Compliant?
Incident.io privacy and compliance overview. Last scanned: 1 months ago.
Incident.io scored 41/100 (grade F), indicating significant privacy issues. Key issues found: 1 tracking request detected before consent. Tracking requests detected but no consent banner found. This is an automated technical assessment, not a legal compliance certification.
41/100
Privacy and compliance score
Scanned June 1, 2026 in fetch mode.
Pre-consent tracking
0/231 tracking request detected before consent.
Cookie consent banner
0/12Tracking requests detected but no consent banner found.
CCPA / CPRA disclosures
0/8No CCPA/CPRA opt-out signals detected. CCPA/CPRA compliance requires more than disclosures. This score reflects observable signals only, not legal compliance.
Privacy policy
6/10Privacy policy found but may be incomplete or outdated.
DPA and sub-processor list
3/7No DPA or sub-processor list found.
Accessibility (WCAG 2.x AA)
7/15Accessibility scan unavailable in fetch mode.
Hosting region disclosure
5/5No data hosting region disclosure found.
COPPA signal
5/5No COPPA language detected.
Security headers
10/10All four security headers present.
AI training stance
5/5AI training opt-out disclosure found in privacy policy.
How does Incident.io compare on privacy?
Top-ranked Dev Tools tools:
See all 59 Dev Tools tools ranked →Does Incident.io self-report SOC 2, HIPAA, or PCI compliance?
The following is based on Incident.io's public documentation. ComplianceCheckup has not independently audited these claims.
Frequently asked questions about Incident.io compliance
Is Incident.io GDPR compliant?
Incident.io received a privacy grade of F (41/100) in our automated scan. 1 tracking request detected before consent. Tracking requests detected but no consent banner found. For a complete GDPR assessment, consult a qualified privacy professional.
Does Incident.io offer a Data Processing Agreement (DPA)?
Yes. Incident.io provides a DPA linked in the Legal documents section above. Review it carefully and sign before transferring personal data.
Is Incident.io SOC 2 certified?
Incident.io holds a SOC 2 Type II certification.
What pre-consent tracking did we find on Incident.io?
1 tracking request 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 Incident.io's biggest privacy risks?
Based on our automated scan, the top areas of concern are: Pre-consent tracking, Cookie consent banner, CCPA / CPRA disclosures. 1 tracking request detected before consent. These findings are automated and may not capture all risks.
How does Incident.io handle CCPA?
No CCPA/CPRA opt-out signals detected. 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.