Effective: August 7, 2026
Website traffic measurement
We use a limited first-party measurement feature to understand visits, pageviews, contact-channel clicks, traffic sources, landing pages, language use, countries, and inquiry outcomes. This privacy page does not send its own analytics pageview or contact-click event.
- The public page path without query parameters or fragments.
- A normalized source and channel based on the referring hostname or selected campaign labels (utm_source, utm_medium, and utm_campaign) when present. The complete referring URL and complete query string are not stored in the traffic analytics tables.
- The site language, event time, and a two-letter country code supplied at the request edge when available.
- When you actively click a contact entry, the normalized method (WhatsApp, Telegram, email, phone, WeChat, or QQ) and the public source-page path. The contact address, phone number, account, and destination URL are not stored in the traffic analytics tables.
Daily visitor key and 30-minute sessions
Our web server necessarily receives an IP address and User-Agent with an HTTP request. For traffic measurement, these values are used transiently to create a keyed HMAC visitor identifier that changes each UTC+8 calendar day. The raw IP address and full User-Agent are not written to the traffic analytics tables.
Pageviews associated with the same current daily identifier are grouped into a visit while the session remains active. The session expires after 30 minutes of inactivity; a later pageview starts another visit.
This measurement feature does not set an analytics cookie or use browser local storage.
Do Not Track and Global Privacy Control
When the browser exposes an enabled Do Not Track (DNT) or Global Privacy Control (GPC) signal, pageviews and contact-click events are not recorded by this traffic measurement feature.
Retention and inquiry attribution
Raw traffic-analysis visit, pageview, and contact-click records are retained for 190 days and then removed. An attribution snapshot linked to a submitted inquiry may remain with that inquiry after the underlying visit is removed.
Inquiry form details, including contact details and the project message, are business records used to answer and follow up on the request. An inquiry record may also include the submitting IP address and User-Agent for abuse prevention and support diagnostics. Inquiry records are stored separately from traffic measurement records and are not governed by the 190-day traffic-record period. When possible, the submitted source page and current traffic attribution are linked to the inquiry so we can understand which channels produce genuine requests.
Server access and security logs
Web server, reverse-proxy, and security logs serve separate reliability, abuse-prevention, and diagnostic purposes. They may contain request details such as an IP address, User-Agent, requested path, status, and time. Application-container logs are capacity-rotated. Other infrastructure log retention depends on the applicable server settings and may vary with traffic and storage capacity; this notice does not promise a fixed number of days.
External services and privacy questions
If you open an external contact service or map from this website, that provider handles the resulting request under its own terms and privacy practices.
For a privacy question or a request concerning an inquiry you submitted, use our Contact page and provide enough information for us to identify the relevant inquiry.