Plain notice. No theater.
What this site measures, why entrance traffic is recorded, and how to opt out of aggregate analytics.
Who this is for
What we measure on the site
When someone opens a page on idigdata.com, we record one first-party entrance (the door-knock) for operating this practice: path, time, referrer, basic device/browser signals, optional UTM / click-id parameters (also kept in a short first-party attribution cookie), and coarse host location (country / region / city). Application Layer and Agentic Layer are live pages, same as Home and Contact. We store a keyed HMAC of the visitor IP - not the raw address - plus a small allowlisted set of request metadata (for example accept-language and fetch-site). We do not keep precise latitude/longitude or full proxy header dumps.
We also use Vercel Analytics for aggregate, privacy-oriented visit counts. You can opt out of that analytics layer from the site notice or the control below.
Cookies we set
- Session door cookies - short-lived markers so we do not double-count the same entrance window.
- Attribution cookie - remembers UTM / gclid from a campaign landing for about 30 days so later pages in the same browser still attribute correctly.
- Analytics preference - remembers if you opted out of Vercel Analytics.
- Internal / fleet markers - only if this practice deliberately marks a browser so operator and automation traffic can be filtered from buyer traffic.
Contact form
Who processes data
Retention and requests
Analytics opt-out
Prefer no Vercel Analytics from this browser? Use the site notice, or turn it off here. First-party entrance telemetry for operating the practice still runs; this control only stops the Vercel Analytics layer.
Last updated August 13, 2026.