Cookie and Landing Analytics Notice
Current Posture
Blackglass uses first-party operational, funnel, and aggregate interaction-map signals to operate the site, prevent abuse, preserve draft/order continuity, understand product interest, and see where visitors click or get stuck. The landing path does not use third-party advertising trackers or third-party session replay.
What May Be Stored
- First-party identifiers for draft continuity, rate limiting, abuse prevention, and landing analytics.
- Campaign and funnel context such as UTM values, referrer host only, landing path, CTA location, and product interaction events.
- Aggregate usage and heatmap samples such as route views, viewport buckets, section exposure, scroll milestones, stable button/section keys, and percentage click bins.
- Submitted form state, checkout state, Client Hub commerce checks, and product interaction events needed to operate the buyer flow.
- Basic technical request metadata in server logs for security and reliability.
Usage analytics do not store form values, DOM text, CSS selector paths, buyer email
addresses, contact rows, full referrer paths, Client Hub tokens, raw IP addresses in the
heatmap table, or third-party tracker identifiers. Add ?analytics=off to the
landing URL to disable browser-side analytics identifiers in that browser.
Retention
Raw landing and usage analytics are retained for a limited operational period, 90 days by default, and may later be kept only as aggregated counters. Order, invoice, payment, support, and audit records follow the Privacy Notice and applicable business-record requirements.