Source
Consent & visitor tracking — found from sitemap — Crazy Egg
Checked for Crazy Egg on 13 Oct 2026
- Page
- https://support.crazyegg.com/knowledge-base/crazy-egg-privacy-data-practices/
- Checked
- 13 Oct 2026, 09:41 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:2871dd008a75b885ad8e6b9634528ef63ed1f6365bc79c078672dd05c7a17403
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
GDPR Report an error
“Crazy Egg is GDPR compliant. We also comply with industry-specific privacy policies (Health Care and Financial) standards.”
-
Ip anonymization Report an error
“IP addresses of visitors are always anonymized before being stored. We set the last octet of IPv4 addresses to 0 to ensure the full IP address is never written to disk.”
-
No pii in snapshots Report an error
“we do not collect any other Personal Identifiable Information (PII) in our Snapshots or AB Testing features, and all IP addresses are anonymized”
-
Uuid identifier Report an error
“Site visitors are assigned a unique user identifier, UUID, so Crazy Egg can keep track of returning visitors without relying on personal information, such as the IP address.”
-
Employee training Report an error
“All employees receive security and privacy training at the time of hire and quarterly security and/or privacy awareness training.”
-
Employee nda Report an error
“All employees sign a Non-Disclosure Agreement and are restricted to accessing only the data required to complete their work.”
-
Employee 2FA Report an error
“Crazy Egg requires using single sign-on, strong passwords, and/or 2-factor authentication for all employees to access production servers for the Crazy Egg Service.”
-
Access logging Report an error
“Employee access to production systems that contain your data is logged and audited.”
-
Incident response plan Report an error
“We have an Incident Response Plan designed to promptly and systematically respond to possible security and availability incidents. The incident response plan is tested and refined regularly.”
-
Password hashing Report an error
“End-user account passwords are hashed with a random salt using industry-standard techniques (we currently use BCrypt).”
-
Session management Report an error
“All sessions are logged out upon quitting the browser. When signing out of the Crazy Egg Service, the system is designed to delete the session cookie from the client and invalidate the session identifier on Crazy Egg servers.”
-
Access logs scope Report an error
“Logs are kept at all account levels for the following key changes that end users make within the account: Account: Sign-in / Sign-out Tracking changes: Creating, Deleting, Start/Pause and Updating Updating Settings”
-
Tls encryption Report an error
“All communications from your end users and visitors with the Crazy Egg Service are encrypted using industry-standard communication encryption technology. Crazy Egg currently uses Transport Layer Security (TLS), with regular updates to cipher suites and configurations.”
-
Siem Report an error
“Crazy Egg uses a Security Incident Event Management (SIEM) system and other security monitoring tools on the production servers hosting the Crazy Egg Service.”
-
Penetration testing Report an error
“Third-party application security assessments and penetration tests are performed annually”
-
Owasp Report an error
“Crazy Egg designs, reviews, and tests the software for the Crazy Egg Service using applicable OWASP standards.”
-
Code reviews Report an error
“Automated source code analysis designed to find common defects Peer review of all code before being pushed to production Manual source code analysis on security-sensitive areas of code”
-
Sdlc Report an error
“Crazy Egg designs, reviews, and tests the software for the Crazy Egg Service using applicable OWASP standards.”
-
Data replication Report an error
“To help ensure availability in a disaster, we replicate data across multiple data centers.”
-
Backups Report an error
“We perform daily, weekly, and monthly backups of data stored on the Crazy Egg Service, which are tested regularly.”
-
Backup retention Report an error
“Full database backups are taken daily, stored on Amazon Cloud Storage (AWS S3), and kept as an electronic copy for three days.”
-
Vpc isolation Report an error
“Our application and database servers run inside an Amazon VPC, Virtual Private Cloud. The database containing visitor and usage data is only accessible from the application servers, and no outside sources can connect to the database.”
-
Customer data collected Report an error
“This data collection includes the customer name, email address for account access, payment information, and website (domains) entered by the customer.”
-
User roles Report an error
“User roles specify different levels of permissions that you can use to manage the users on your Crazy Egg Service account. You can invite users to your account without giving all team members the same levels of permission.”
-
Authentication Report an error
“Crazy Egg requires authentication for access to all application pages on the Crazy Egg Service, except for those intended to be public. Crazy Egg currently uses TLS-encrypted POST requests to transmit authentication credentials to the Crazy Egg Service.”
-
Company Report an error
“© Crazy Egg, Inc. 2026”
8 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The CRO Consultant Consent & visitor tracking
- The CRO Consultant European sovereignty
- The Data Protection Officer Consent & visitor tracking
- The Data Protection Officer European sovereignty
- The E-Commerce Manager Consent & visitor tracking
- The E-Commerce Manager European sovereignty
- The Growth Lead Consent & visitor tracking
- The Growth Lead European sovereignty
- The Product Engineer Consent & visitor tracking
- The Product Engineer European sovereignty
- The Skeptic Consent & visitor tracking
- The Skeptic European sovereignty