Measure useful research without tracking people across the web.
VLSI Market uses consent-aware, first-party events to improve discovery, chart workflows, exports, retention, and reliability. After consent, it also loads Cloudflare Web Analytics for cookie-free page-visit and performance measurement. Analytics never become part of the factual market-data layer.
PLAIN-LANGUAGE BOUNDARIES
What is measured—and what is not
After consent
Double-hashed random browser and session identifiers; the browser identifier lasts up to 90 days
Coarse country code supplied at the edge; the raw IP address is not written to the event ledger
Normalized device, browser, operating-system, viewport, language, and timezone classes
Landing, exit, referrer domain, campaign, active time, and return-frequency bands
Raw user-agent strings or invasive device fingerprints
Email addresses, form bodies, private account content, or raw search queries
Bots, crawlers, uptime checks, and staff-marked internal traffic
External stock displays
Stock displays on the equity desk and newsroom are supplied by TradingView. A display connects only after you choose its Load TradingView button, then loads when visible and sends the connection information needed to serve it under TradingView’s privacy policy. VLSI Market does not send its analytics identifier or browser-local watchlist to TradingView, and does not copy displayed quotes into its own records.
Optional news images connect to the publisher only when you choose Show publisher image. The publisher receives the connection information needed to serve the image; the request sends no referrer. VLSI Market does not send its analytics identifier or browser-local watchlist with that request.
First-party analytics consent controls VLSI Market events. Withdrawing it does not block external displays or images that you choose to open.
YOUR CONTROLS
Consent, withdrawal, and deletion
Global Privacy Control and Do Not Track are respected where available. Withdrawal stops new first-party analytics events immediately. Deletion uses a retained hash for the current browser identifier and retries after a failed request; expired or cleared identifiers cannot be matched and instead age out. Event rows older than 400 days are removed when the next event is accepted, so 400 days is not a background hard-delete deadline.
Current setting: analytics disabled
Optional Google Analytics
Optional Google Analytics, received by Google LLC, stays off until you separately allow it. Declining sends no Google tag request, cookie, or denial ping. If allowed, VLSI explicitly sends only a page_view limited to a product code, a structural path stripped of query strings, fragments, and dynamic identifiers, a route-derived title, and a referrer reduced to direct, same-origin, or external. In operating the service, Google Analytics creates or processes a pseudonymous client identifier in a first-party cookie limited to this host, first-visit, session, and engagement metadata, and basic browser, device, and request information. The connection conveys an IP address to Google; Google says it uses the address to derive approximate location and discards it before logging or storage. VLSI does not explicitly send or set raw URLs, search terms, form or click content, free text, email, or user/account IDs. The analytics cookie lasts up to 90 days, and the recipient-consent choice stays in this browser for up to 180 days. GA event and user retention is set to 14 months; Google Signals, ad personalization, detailed location/device collection, and automatic page-history, site-search, and form measurement are off. We honor GPC and DNT, and you can withdraw at any time in Analytics settings. Withdrawal deletes reachable analytics cookies and reloads the page to block new requests.