Visitor Tracking Transparency
Effective date: September 23, 2026
Most sites tell you they use "cookies and analytics" and leave it at that. We'd rather show you. This page is a plain-language companion to our Privacy Policy (which is the legally binding document) — it exists so you can see, in real terms, exactly what gets logged when you visit, why, and for how long.
The panel above is generated fresh from your current request — nothing is fabricated or delayed. The IP/location/device row is standard web-server behavior and appears regardless of your cookie-banner choice, since it doesn't depend on a cookie at all. The "campaign attribution" row only appears if you actually arrived via a tracked ad/campaign link at some point — it's not affected by your cookie choice either, since UTM/gclid parameters are read from the URL, not from a consent-gated tag.
What we log on every visit, and why
| Data point | Why we collect it | Consent required? |
|---|---|---|
| IP address & approximate (city-level) location | Standard for any web server; also used to auto-match returning job applicants and to block abusive IPs | No — strictly necessary |
| Device, OS, browser | So we know which platforms our real visitors use, and to render pages correctly | No — strictly necessary |
| Pages visited, referrer, timestamps | Basic traffic analytics — which content works, where visitors come from | No — strictly necessary |
ws_vid — persistent visitor ID (2-year cookie) | Lets us tell a returning browser apart from a brand-new one, without relying on third-party cookies | No — strictly necessary |
ws_sid — session ID (30-minute sliding cookie) | Groups your page views from one visit into a single session, instead of disconnected events | No — strictly necessary |
UTM parameters & Google gclid | Only present if you clicked a tracked ad/campaign link — tells us which campaign to credit | No — this is first-party attribution, not advertising itself |
| Google Analytics / Ads, Meta Pixel | Aggregate performance analytics and ad conversion measurement | Yes — only after you accept our cookie banner |
Security logging — separate from marketing analytics
We also keep a security event log, entirely separate from the traffic data above, used only to protect the site: failed admin-login attempts, IP addresses we've blocked for abusive behavior, repeated requests to nonexistent pages (a sign of automated scanning), and rate-limit trips. This is about defending the site against bots and bad actors — it is not used to profile or advertise to individual visitors. Full detail is in Section 9 of our Privacy Policy.
How long we keep it
Raw traffic and security logs are automatically and permanently deleted after 12 months by a scheduled process — we don't manually curate what gets purged. Form submissions (contact/job inquiries) are kept longer, only for as long as needed to respond to you and pursue any resulting relationship. Full detail in Section 8 of our Privacy Policy.
What we don't do
- We never sell your personal information.
- We don't fingerprint you beyond the first-party cookie described above.
- We don't share your data with anyone outside the specific service providers listed in our Privacy Policy.
One thing we won't overclaim: our Google Tag Manager container loads on every page to manage our tags, and the analytics/advertising tags inside it are configured to wait for your cookie-banner acceptance before activating. That configuration lives in Google's dashboard, outside this website's own code, so we can tell you how it's set up but can't show you live proof of it the way we can for the first-party data above. If that distinction matters to you, your browser's own tracker/cookie blocking is the more absolute control.
Your controls
Use the cookie banner shown on your first visit to accept or decline non-essential tracking, clear your browser's cookies/local storage at any time to reset your visitor ID, or contact us at info@webspecia.in to request a copy or deletion of your data. Full rights (including GDPR and CCPA specifics) are in Section 10 of our Privacy Policy.