Web Analytics Compliance Overview for HitKeep

Ce contenu n’est pas encore disponible dans votre langue.

HitKeep can support a strong privacy and compliance posture. It does not make a deployment automatically compliant just because you install it.

The right way to read the compliance docs is:

HitKeep can reduce your compliance surface
HitKeep exposes controls that support common obligations
you still need the right lawful basis, notices, contracts, and request-handling workflows

That matters especially for:

Short Answer

Regime	Does HitKeep help?	Main caveat
GDPR	Yes, materially	You still need lawful basis, transparency, retention, contracts, and transfer analysis
PECR / ePrivacy	Yes, partly	HitKeep is cookie-free by default, but the tracker uses `sessionStorage` for an opaque session ID and timestamp, so device-storage rules may still apply
CCPA / CPRA	Yes, partly	You still need notices, request methods, and opt-out handling where sale/share rules apply

The current product gives you several controls that matter for privacy programs:

Self-hosting or managed cloud: run HitKeep on your own infrastructure or in HitKeep Cloud in the EU or US
No analytics cookies by default: the public tracker does not set browser cookies for analytics
Public tracker uses limited sessionStorage: hk.js stores a short-lived opaque session ID and timestamp in browser sessionStorage
No durable browser retry queue: failed delivery retries stay in JavaScript memory and are capped to a tiny queue
Do Not Track respected by default: browsers sending DNT: 1 are skipped unless you explicitly override that behavior with data-collect-dnt="true"
No third-party frontend assets: dashboard assets and the tracker are served from your own origin
No phone-home telemetry: no external analytics vendor call is required for core product operation
Data export and portability: site and user takeout in open formats
Retention controls: per-site retention and Parquet archiving
Deletion primitives: admins can delete users and sites; tenant-scoped analytics data is removed with the site lifecycle
Security controls: HTTP-only auth cookies, TOTP, passkeys, rate limiting, trusted proxies, and same-origin serving

The most important compliance question is not:

“Is HitKeep compliant?”

It is:

“How does HitKeep change the technical and contractual risk profile of our analytics deployment?”

For most teams, the practical advantages are:

The practical caveat is also clear:

GDPR: data minimization, lawful basis, retention, international transfers, and cloud hosting
PECR / ePrivacy: cookies, sessionStorage, consent analysis, and dashboard cookies
CCPA / CPRA: notice, rights, service-provider positioning, and consumer request handling

If you use HitKeep Cloud, add these extra checks to your compliance review:

choose the correct region at signup
ensure your privacy notice describes the hosted service relationship
review the Privacy Policy (Cloud)
review the Terms of Service (Cloud)
confirm your own subprocessor, transfer, and retention requirements are satisfied