What We Track vs What We Don’t
SealMetrics is built on one foundational principle:
If tracking a metric could compromise user privacy, we do not track it — even if regulations allow it.
This document details everything SealMetrics does and does not track, why, and how this enables full GDPR/ePrivacy compliance without requiring user consent.
What We DO Track
The Four-Variable System (Isolated Hits)
SealMetrics processes each page view (“hit”) independently using only four non-identifying data points:
1. Timestamp
- Purpose: time-based analysis and trend insights
- Privacy: cannot identify an individual
2. User Agent (Not Stored)
- Used for: browser/device category detection
- Not stored: complete user agent strings are discarded
- Result: anonymous device classification
3. Current URL
- Page path
- Page popularity
- Anonymous content performance
4. Referral URL
- Anonymous attribution
- Campaign performance
- Traffic source identification
What This Allows Us to Measure
1. Page Analytics
- Pageviews (aggregated)
- Top pages
- Anonymous navigation patterns
2. Traffic Analytics
- Entrances (anonymous hits)
- Traffic volume trends
- Marketing channel performance
3. Engagement Behavior (Custom Events)
- Click events
- Scroll depth
- Form interactions
- Video plays
- Downloads
ALL aggregated — no user-level behavior.
4. Navigation Patterns
- Entry pages
- Exit pages
- Internal search (anonymous; via events)
5. Campaign & Marketing Analytics
- UTM campaign tracking
- Referrer attribution
- Search traffic
- Social media traffic
- Revenue attribution (aggregated)
6. Conversion Tracking
- Goal completions
- E-commerce events
- Lead generation
- Micro-conversions
- Channel-level revenue attribution
7. Anonymous Device Data
- Browser category
- OS category
- Desktop / mobile / tablet
- Screen-size buckets
- Language
8. Geographic Data
- Country (derived from time zone)
❌ Region / City — not collected
9. Business Intelligence Metrics
- Conversion rate
- Average order value
- ROAS
- Funnel performance
What We DO NOT Track
No Personal Data
❌ IP addresses
❌ User IDs
❌ Emails
❌ Phone numbers
❌ Names
❌ Persistent identifiers
❌ Exact user agent strings
No Behavioral Identification
❌ User journeys
❌ Session reconstruction
❌ Returning users
❌ Individual preferences
❌ Personal browsing behavior
No Cross-Site Tracking
❌ Third-party cookies
❌ Advertising identifiers
❌ Cross-domain identification
❌ Social media identifiers
No Sensitive Personal Data
❌ Health
❌ Financial
❌ Political
❌ Religious
❌ Demographic profiling
No Device-Level Identifiers
❌ Device IDs
❌ MAC addresses
❌ Hardware fingerprints
❌ Advertising IDs
No Tracking Technologies
❌ Cookies
❌ LocalStorage
❌ SessionStorage
❌ Fingerprinting
❌ Terminal code
❌ Web beacons
No Private Communications or Content
❌ Email contents
❌ Chat messages
❌ Form personal data (only event counts)
❌ Uploaded files
❌ Social media posts
❌ Documents
Compliance Framework
GDPR
- European company
- Servers in Dublin
- No personal data
- Isolated hit processing
- Avoids all identifiers
ePrivacy Directive
- No terminal code
- No personal data
- No user-level tracking
- Consent not required
CCPA / PECR / Global Compliance
- No personal information
- Anonymous by design
- Future-proof data architecture
How We Decide What to Track
Before tracking any metric, we evaluate:
- Privacy Risk: Could this identify someone?
- Business Need: Is this essential?
- Legal Compliance: GDPR, ePrivacy, CCPA, PECR
- Future Proofing: Will it remain compliant?
- User Expectation: Would users expect this?
SealMetrics always chooses the more restrictive option.
Summary: Privacy-First Analytics, Without Compromising Insights
SealMetrics proves that advanced web analytics does not require personal data.
You get:
- 100% traffic measurement
- Full attribution clarity
- Accurate ROAS
- Reliable e-commerce insights
- Complete privacy protection
Our promise:
Every metric we show is compliant, anonymous, and future-proof.
Privacy and analytics no longer conflict — they reinforce each other.