Cookies & Analytics Notice
Think4Ei runs a first-party behavioral analytics pipeline on think4ei.com. This page describes exactly what it captures, what it deliberately does not capture, and how it's governed — in plain language, grounded in the actual code that runs it.
We don't use third-party ad cookies
think4ei.com does not load third-party advertising trackers, ad-tech pixels, or cross-site retargeting cookies (no Google Analytics ad-signals, Facebook Pixel, or similar). Our analytics is first-party and built in-house.
What local storage we use
Instead of a traditional third-party cookie, the site stores two small identifiers in your browser's local storage and session storage:
| Identifier | Purpose | Lifetime |
|---|---|---|
| Visitor ID | A random, client-generated id — not a name, email, or real-world identifier — used to group activity from the same browser across visits. | Persists in local storage until you clear site data |
| Session ID | A random id scoping activity to one browsing session. | Cleared when the browser session ends |
What we capture
- Page views, click events, and scroll-depth milestones (25/50/75/100%).
- Session duration and time spent on each page.
- Referrer and UTM campaign parameters.
- Device, browser, operating system, and viewport/screen size.
- The path of pages visited during a session.
- Form-field engagement: whether you focused, left, or abandoned a field, and whether it had a value — never the value itself.
What we deliberately never capture
- Typed field values — your name, email, phone number, or message text as you type it, is never recorded by the analytics pipeline. (If you separately submit a contact form or chat message, that content is handled as account/support data under our Privacy Policy, not as analytics.)
- Raw IP address — only a salted SHA-256 hash of your IP is stored, specifically so it cannot later be reversed to re-identify you, even in aggregate.
How this data is governed
Raw analytics events are recorded locally first, then — once a browsing session goes idle — a session-level aggregate summary is sealed and quality-checked through the same internal data-governance pipeline the rest of the platform uses for ingested data (a merkle-seal step for integrity, followed by an automated quality gate). This happens at the session-summary level, not per individual click, both to bound cost and because a single sealed summary is a more meaningful unit than a lone click event.
Your choices
- You can clear your browser's local storage for think4ei.com at any time to reset your anonymous visitor identifier and start fresh.
- Most browsers let you block local storage/site data entirely in privacy settings; the site will continue to function, though session-based features like signup flows may behave differently.
- Because we don't use ad-network cookies, there's no ad-preferences opt-out needed here — there isn't one to opt out of.
Retention
Sealed session-summary analytics records are retained on a rolling basis for product-research and improvement purposes, consistent with our Privacy Policy. We periodically review retained analytics data as part of normal data-governance practice.
Questions
Email support@think4ei.com with any question about this pipeline — we're glad to explain further, since this is exactly the kind of thing a lot of sites don't document honestly.