Privacy and your enquiry

Consultation source information

An enquiry may include your optional source choice and bounded visit information: public page paths, a referring website hostname and named campaign labels. Full referring URLs, arbitrary query strings and sign-in tokens are excluded. Source signals help follow-up; a referral alone does not establish an AI recommendation. Enquiry records remain available only through the existing owner-protected admin workflow.

The websites count public page views, contact actions and durably saved non-test enquiries using their respective definitions. www.ttsqc.com counts successful public HTML requests as page views; ttsglobal.net counts browser page-view events. Visit analytics do not read names, email addresses, form contents, full referrer URLs or URL query parameters. Existing page-view and contact counters use no visitor identifier. The previous optional consent-based UV client remains retired. The new daily visitor estimate is reported separately, with no reconstructed visitor counts for past collection gaps. Visitor-estimate requests from ttsglobal.net are sent directly to a dedicated collector on the TTS-owned main server www.ttsqc.com, rather than the secondary website hosting platform. That TTS server handles the connection; the request body still contains only the secondary site public page path. The secondary site uses a separate estimate database and independent site/day keys. Its digests are not combined with main-site visitor digests and no cross-site identity link is created. Daily visitor estimates are not counts of verified people. On visible public pages, the browser sends an estimate request containing only the public page path and no visitor ID. It contains no name, email address, form contents, full referrer URL or URL query parameters. The server uses the connection IP address and a broad browser category in memory to create a keyed deduplication digest limited to this website and one calendar day in Beijing time. The visitor-estimate process and database do not persist raw IP addresses or full User-Agent strings. No visitor cookie or daily visitor identifier is stored in the browser, and visitors are not linked across websites or days. Digests and their independent daily keys are eligible only for the current and preceding Beijing dates. Expired data is cleaned on new estimate events or authorized daily-report reads. Service or report-read interruptions can delay physical cleanup, but expired digests are not used for deduplication. Daily aggregates cover the most recent 90 days; older aggregates are cleaned on new events or report reads. Use “Do not include my visits” in the footer to stop future estimate events, or “Include my visits” to participate again. The browser stores only a non-unique opt-out boolean, not a visitor identifier. If this preference cannot be saved, estimate events are not sent. Opting out does not retroactively remove existing daily aggregates. Browsers with Do Not Track or Global Privacy Control enabled do not send new estimate events. Marked tests, monitoring and identified bots are excluded. Different people using a similar browser on a shared network may be combined. One person changing networks, devices or browsers may be counted again. Unidentified bots, disabled JavaScript, blockers and lost requests can also affect coverage. The metric is labelled “daily visitor estimate”, not exact people, customers or sales, and is not used as a session-conversion denominator. Page views, contact clicks and durably saved non-test enquiries retain their separate definitions. Page views are not used to reconstruct visitor estimates before collection starts or during missing coverage.