ComplianceCheckup

Is Less Annoying CRM GDPR Compliant?

Less Annoying CRM privacy and compliance overview. Last scanned: 1 months ago.

Less Annoying CRM scored 46/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

46/100

Privacy and compliance score

Scanned June 5, 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.

CCPA / CPRA disclosures

3/8

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.

Security headers

8/10

1 security header missing: X-Content-Type-Options: nosniff.

DPA and sub-processor list

3/7

No DPA or sub-processor list found.

Accessibility (WCAG 2.x AA)

7/15

Accessibility scan unavailable in fetch mode.

AI training stance

5/5

No AI training disclosure found.

COPPA signal

5/5

No COPPA language detected.

Privacy policy

10/10

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

Hosting region disclosure

5/5

Data hosting region disclosed in privacy policy.

How does Less Annoying CRM compare on privacy?

#35 of 43
in CRM
#767 of 904
across all tools
Top 85%
overall percentile
57/100
CRM average (this tool: 46/100)

Top-ranked CRM tools:

See all 43 CRM tools ranked →

Does Less Annoying CRM self-report SOC 2, HIPAA, or PCI compliance?

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

StandardStatus
SOC 2Not publicly documented for Less Annoying CRM
HIPAANot publicly documented for Less Annoying CRM
PCI DSSNot publicly documented for Less Annoying CRM
GDPRSee scan results above
CCPASee scan results above

Frequently asked questions about Less Annoying CRM compliance

Is Less Annoying CRM GDPR compliant?

Less Annoying CRM received a privacy grade of F (46/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 Less Annoying CRM offer a Data Processing Agreement (DPA)?

No DPA link was found in our directory for Less Annoying CRM. Check their legal or trust center page, or contact their sales team to request a DPA under GDPR Article 28.

Is Less Annoying CRM SOC 2 certified?

No SOC 2 certification was found in our directory for Less Annoying CRM. Check their trust center or security page for current status.

What pre-consent tracking did we find on Less Annoying CRM?

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 Less Annoying CRM'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 Less Annoying CRM 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.