35 docs tagged with "gdpr"

How the Digital Omnibus simplifies AI compliance and clarifies GDPR-AI intersection

CNIL self-assessment for Sealmetrics analytics - how it maps to the French consent exemption requirements. Self-assessed, not certified.

Cookieless analytics measures visitors without consent banners: how it works, why cookie-based tools lose the visitors who reject or ignore the cookie banner, and how to set it up.

How Sealmetrics is designed to meet GDPR, ePrivacy, and CNIL requirements (self-assessed, not certified): bot filtering, legal analysis, and a legal FAQ for consentless, cookieless analytics.

Why, on our self-assessment, Sealmetrics needs no consent banner for its own analytics (Germany is an open question) — no cookies, nothing stored on the device, a session identifier that rotates daily, and what exactly is recorded on each hit.

Where Sealmetrics stores your data and how long it's retained. EU-based infrastructure with clear retention policies.

How data subject access requests work with Sealmetrics — why visitor requests cannot be linked to any record, and how account-holder rights are handled.

When a session ID triggers the ePrivacy consent requirement and when it does not, and how Sealmetrics builds its session identifier: an in-browser device-characteristics hash, never stored on the device, re-keyed daily on the server.

Official position of European data protection authorities on the Digital Omnibus proposal - concerns, support, and recommendations

Complete guide to the EU Digital Omnibus Regulation (COM(2025) 837) simplifying GDPR, ePrivacy, and data legislation

Detailed analysis of GDPR changes: personal data definition, pseudonymization, AI training, breach notifications

How cookieless analytics comply with GDPR requirements and provide better data without consent banners

How the ePrivacy consent rule and the GDPR apply to a session identifier that rotates daily, the legitimate-interest basis, and when a session ID does or does not require consent.

How Sealmetrics attributes traffic and conversions without User-IDs, cookies or cross-session tracking — last-click attribution read from the URL on every hit.

The architecture behind Seal AI: EU-only inference on Scaleway Paris, zero retention, no training on your data, and why no data is ever transferred to the United States.

How Sealmetrics filters bot traffic with layered, privacy-safe defenses — and why its ephemeral, in-memory use of IPs fits a platform designed to comply with the GDPR and ePrivacy.

How Sealmetrics detects visitor country from the browser timezone instead of IP addresses — GDPR-friendly geo data with no IP address stored or looked up.

The concrete protections behind Sealmetrics — no cookies, no persistent identifiers, no stored IP addresses, EU-only storage and short retention.

Key dates and milestones for the EU Digital Omnibus: proposal publication, committee assignments, feedback periods, and the expected GDPR change timeline.

Self-assessment of how Sealmetrics' privacy-first, isolated-hit architecture is designed to meet GDPR, ePrivacy, CCPA and PECR requirements. Not a certification.

Nothing stored on the device, no data that identifies anyone, a session identifier that rotates daily. Self-assessments against CNIL, UK PECR, TDDDG, Garante and FADP criteria, plus the DPA.

How Sealmetrics maps to the seven Privacy by Design principles — with the concrete architectural choice behind each one.

Official documentation for Sealmetrics, the consentless web analytics platform that measures traffic without cookies and, by its own assessment, without consent banners, storing nothing that identifies anyone.

Fathom hashes IP and user agent daily and stores anonymised data in the US after EU processing. Sealmetrics never hashes the IP and keeps all data in Dublin.

GA4 needs cookies and consent, so it loses the visitors who reject or ignore the cookie banner. Sealmetrics measures without cookies or IP storage, hosted in Dublin; no banner, by our self-assessment.

Matomo is GPL-licensed and self-hostable, but its cookieless mode hashes the visitor's IP. Sealmetrics doesn't store the IP or build its identifier from it, and keeps analytics data in Dublin.

Piwik PRO pairs analytics with a consent manager and an anonymous mode hashed from the IP. Sealmetrics needs no consent layer (self-assessed), stores no IP and keeps analytics data only in Dublin.

Plausible identifies visitors with a daily hash of IP and user agent; Sealmetrics never derives an identifier from the IP. Both cookieless, both EU-hosted.

Both skip cookies and IPs, say no consent banner is needed and derive country from the timezone. Simple Analytics keeps it minimal; Sealmetrics adds attribution, e-commerce and AI.

How Sealmetrics measures without identifying anyone — a small set of non-identifying fields, nothing stored on the device, EU-only storage in Dublin — with the index of every privacy and security page.

How the Digital Omnibus extends small business protections to companies with up to 749 employees

Sealmetrics subprocessors are listed in Annex 3 of the DPA at sealmetrics.com/dpa — the authoritative list; change notifications by email on request.

Learn exactly what data Sealmetrics collects, what it does not collect, and how privacy is enforced technically.

What consentless analytics is, the small set of non-identifying fields Sealmetrics records, and why storing nothing on the device and nothing that identifies anyone means, on our self-assessment, no consent banner is required (in Germany an open question).

Sealmetrics needs no consent banner because it stores nothing on the visitor's device and no data that identifies anyone, and fits the audience-measurement exemption — the short version, as our self-assessment.