Privacy & Security
Built-in privacy features and PII filtering to protect user data
Automatically filters personally identifiable information like emails, phone numbers, SSNs, and credit card numbers from URLs and form data.
Respects the Do Not Track (DNT) browser setting. When enabled, EventDash will not track users who have DNT enabled.
EventDash stores an anonymous session ID in localStorage (not cookies). Device characteristics such as browser, OS, screen, timezone, and language are used to keep sessions stable. This is not used to identify a person.
EventDash automatically filters the following types of PII from URLs and form data:
- Email addresses
- Phone numbers
- Social Security Numbers (SSN)
- Credit card numbers
- Common sensitive URL parameters
Example:
// Original URL
https://example.com/login?email=user@example.com&token=abc123
// Filtered URL (sent to EventDash)
https://example.com/login?email=[FILTERED]&token=[FILTERED]When a user has Do Not Track enabled in their browser, EventDash will automatically stop tracking. This is enabled by default but can be disabled:
<script
defer
data-api-key="YOUR_API_KEY"
src="https://www.eventda.sh/tracker.js"
></script>
<!-- Opt out of DNT (not recommended) -->
<script
defer
data-api-key="YOUR_API_KEY"
data-respect-do-not-track="false"
src="https://www.eventda.sh/tracker.js"
></script>EventDash uses anonymous session IDs stored in localStorage (not cookies). A device fingerprint is built from:
- Browser type and version
- Operating system
- Screen resolution
- Timezone
- Language settings
- Canvas and WebGL rendering hashes (not used to identify a person)
This information is combined to keep sessions stable. It is not linked to a login or used to identify an individual.
EventDash is designed with GDPR compliance in mind:
- No personal data collection by default
- Anonymous session tracking
- Automatic PII filtering
- Do Not Track support
- No cookies required
- Data minimization principles