Cookie Policy
Publication Date: October 20, 2026
Effective Date: October 20, 2026
This Cookie Policy (hereinafter referred to as "this Policy") applies to the official website platform (twt.com), all subdomains, web console management portals, and mobile web responsive portals operated by HIGHSOON PTE. LTD. (registered address: 8 Temasek Boulevard #21-03, Suntec Tower 3, Singapore 038988; hereinafter referred to as "TWT", "we", "us", or "our").
As an all-scenario intelligent service and collaboration cloud ecosystem serving enterprise clients globally, we place the utmost importance on user data security and privacy protection. This Policy is designed to explain in a clear, transparent, and professional manner how our systems automatically deploy and read Cookies and similar tracking technologies when you access, browse, or utilize the TWT platform, the business scenarios and data scope involved, and how you as a subscriber or user can flexibly exercise your choices and opt-out rights through browser settings and technical tools.
Special Notice: This Policy constitutes an integral part of our platform Terms of Service and Privacy Policy. Matters not expressly addressed herein shall be governed by the provisions of the Privacy Policy regarding personal data processing, cross-border transfers, security safeguards, and legal rights.
1. What Are Cookies and Similar Tracking Technologies
1.1 Basic Definition of Cookies: A Cookie is a small text file containing a string of characters. When you access or navigate the TWT platform via a web browser, our servers send this small, secure text file to be stored on your computer, mobile device, or other browser terminal storage space. During subsequent sessions or upon revisiting the platform, your browser automatically transmits these Cookies back to our servers, enabling our systems to identify your device, maintain authenticated login sessions, remember your preferences, and ensure network communication continuity.
1.2 Similar Technologies (Equivalent Mechanisms): In addition to standard HTTP Cookies, we may also utilize the following front-end technical mechanisms with equivalent functional effects to optimize system performance and maintain network security:
(1) Web Local Storage (HTML5 LocalStorage and SessionStorage): Enables secure client-side key-value data storage. SessionStorage remains active only during the current browser tab session to temporarily record page input states; LocalStorage persists across sessions to save user language preferences (e.g., Chinese/English) and console display theme settings locally, avoiding repeated backend queries and reducing latency;
(2) Web Beacons / Tracking Pixels: Tiny, transparent graphics embedded within web pages or system transactional notification emails, primarily utilized to confirm whether page elements render properly and verify email delivery of system notices;
(3) Security Authentication Tokens: Utilized in microservice API calls to maintain authenticated requests and perform permission verification.
2. Industry Classification System for Cookies
In accordance with standards established by the Internet Engineering Task Force (IETF), World Wide Web Consortium (W3C) specifications, Singapore Personal Data Protection Commission (PDPC) guidelines, and global enterprise privacy best practices, Cookies are classified across three core dimensions:
2.1 Classification by Origin: First-Party Cookies & Third-Party Cookies
(1) First-Party Cookies: Set, stored, and read directly by the website domain you are currently visiting (i.e., the domain displayed in your browser address bar, twt.com). These Cookies are fully owned, managed, and controlled by TWT, and are primarily used to implement core website functions, including user authentication, Cross-Site Request Forgery (CSRF) defense, and user interface preferences.
(2) Third-Party Cookies: Set by a third-party service provider's domain other than the current domain you are accessing. When the TWT platform integrates external technical infrastructure—such as Google Analytics for global web traffic statistics, Microsoft Clarity for UI/UX interaction analysis, or Cloudflare for global network security protection—scripts from these trusted third parties may place Cookies on your terminal. TWT enforces strict security onboarding criteria and contractual DPA obligations on third-party service providers, strictly prohibiting them from utilizing customer data for their own independent commercial marketing purposes.
2.2 Classification by Lifespan: Session Cookies vs. Persistent Cookies
(1) Session Cookies: Temporary Cookies strictly bound to your browser session. When you close your browser or navigate away, these Cookies are automatically purged from system memory.
(2) Persistent Cookies: Cookies with a predefined expiration period that remain stored on your device storage. They allow our platform to recognize your identity or preconfigured settings upon your next visit, eliminating the need to repeatedly reconfigure initialization settings.
2.3 Classification by Operational Purpose: Platform Practical Deployment
Based on the actual operational requirements of the TWT platform, Cookies deployed primarily cover the following functional categories:
(1) Strictly Necessary Cookies: Indispensable technical credentials required to maintain network communications, perform secure identity authentication, prevent credential stuffing, and defend against DDoS attacks;
(2) Performance & Analytics Cookies: Measurement tools utilized to compile aggregated, de-identified statistics on traffic flow, diagnose system exceptions, and continuously optimize user interaction performance;
(3) Source & Attribution Cookies: Used to objectively record lawful promotional channels, referral codes, or ad campaign landing parameters to evaluate marketing reach and conversion efficacy.
Platform Commitment: Such technologies are deployed solely for statistical and measurement purposes regarding business channel efficacy and are strictly prohibited from being utilized to build targeted commercial profiles across websites.
3. Singapore Legal Compliance and Notice-Consent Mechanism
3.1 Standards and Legal Basis under Singapore PDPA: Pursuant to Sections 13 through 17 of the Singapore Personal Data Protection Act 2012 ("PDPA") and Chapter 16 of the Advisory Guidelines on Selected Topics issued by the Personal Data Protection Commission ("PDPC"):
(1) Where Cookies collect solely de-identified aggregated traffic metrics or purely technical parameters (such as browser type, page visit duration, or random session IDs) that cannot identify an individual natural person, such information does not constitute "Personal Data" under the PDPA, and enterprises are not legally required to obtain mandatory express consent from users prior to deployment;
(2) For technical Cookies that may connect to or support personal identifying information, Singapore law recognizes the compliance model of "Notification and Deemed Consent / Implied Consent". So long as the platform provides clear, prominent notification upon initial access, details the processing purposes, and offers accessible opt-out mechanisms, a user's informed, continued access to platform services constitutes valid authorization under Singapore law.
3.2 Legal Effect of Notice and Deemed Consent: To adhere to common SaaS industry standards and strict regulatory compliance while maintaining an uninhibited enterprise collaboration user experience, the TWT platform presents prominent compliance notices across website footers and relevant interfaces. By continuing to browse platform web pages, registering or logging into accounts, or utilizing console features after being notified, you are legally deemed to have acknowledged and agreed to the operational deployment of Cookies and similar technologies pursuant to this Policy and the Privacy Policy.
The platform respects your autonomy and provides detailed opt-out instructions below, enabling you at any time to block or delete non-essential Cookies via your terminal browser settings or dedicated opt-out extensions.
4. Inventory of Cookies Deployed on TWT Platform
To ensure full transparency regarding user data processing, the following inventory details the core Cookies deployed across the TWT platform and its product pages, including identifiers, origins, purposes, and retention lifespans:
|
Cookie Name |
Provider & Attribute |
Category |
Core Processing Purpose & Business Scenario |
Lifespan |
Personal Data Collection Status |
|
twt-token |
TWT |
Strictly Necessary |
Stores encrypted session authentication tokens for logged-in users to maintain secure session status across the console and subdomains |
Approx. 7 days |
Contains no direct identity fields; backend maps encrypted token to active account session |
|
NEXT_LOCALE |
TWT |
Strictly Necessary |
Records user interface language and routing preferences (e.g., zh-CN/en-US) to ensure multi-language interface consistency |
Persistent storage |
No (records only language code such as zh-CN/en-US) |
|
twt-account-page-entered |
TWT |
Strictly Necessary |
Records console account center page visits and security notice status for synchronized recognition across main site and sub-services |
Approx. 1 year |
No (contains only internal operational state and numerical identifiers, no direct PII) |
|
PHPSESSID |
TWT |
Strictly Necessary |
Maintains continuity of server-side PHP sessions for specific subsystems (such as visitor inquiry access and account services) |
Browser session |
No (server-generated random temporary session identifier) |
|
acw_tc / |
Alibaba Cloud |
Strictly Necessary |
Operates alongside Alibaba Cloud Anti-DDoS and CAPTCHA components for network request risk control and scraper interception |
Approx. 1 hour |
No (records only network device behavioral fingerprints and session characteristics) |
|
_ga |
Google |
Performance & Analytics |
Core Google Analytics 4 key used to distinguish unique visitor devices and measure global traffic and conversion performance |
Approx. 13 months |
Contains no direct plaintext PII; aggregated via anonymization; authenticated sessions may link to pseudonymous internal UID |
|
_ga_* |
Google |
Performance & Analytics |
Maintains and tracks user session state and interaction depth within Google Analytics channels |
Approx. 13 months |
No (aggregated session statistical data) |
|
ga_pending_event |
TWT |
Performance & Analytics |
Temporarily buffers pending analytics event parameters during cross-domain navigation or redirects; automatically cleared upon dispatch |
Approx. 1 minute |
No (contains only temporary event types and metric codes) |
|
_clck |
Microsoft |
Performance & Analytics |
Microsoft Clarity component used to store unique analytics identifiers and maintain interaction continuity across pages |
1 year |
Contains no names/emails; authenticated sessions link to pseudonymous internal UID for experience analysis |
|
_clsk |
Microsoft |
Performance & Analytics |
Microsoft Clarity component used to aggregate multi-page interaction trajectories within a single visit into a coherent session |
1 day |
No (de-identified aggregated diagnostic data) |
|
CLID / |
Microsoft |
Performance & Analytics |
Core Microsoft Clarity component used to identify visitor devices and generate click heatmaps and diagnostic reports |
Approx. 13 months |
No (contains only online device analytics identifiers assigned by Microsoft) |
|
twt-tracking-origin |
TWT |
Source & Attribution |
Records external referral sources, initial landing page, and visit timestamps for legitimate marketing performance measurement |
Approx. 365 days |
May contain referrer URL or campaign codes; contains no direct sensitive personal data |
|
rc |
TWT |
Source & Attribution |
Records legitimate marketing partner identifiers or referral codes accompanying user visits for commercial attribution |
Approx. 7 days |
Records only referral code string; contains no personal data |
|
t |
TWT |
Source & Attribution |
Records advertising campaign parameter identifiers to measure reach and conversion efficacy of online promotional campaigns |
Approx. 90 days |
Contains only ad campaign and click identifiers; contains no direct sensitive personal data |
|
_gcl_au |
Google |
Source & Attribution |
Google conversion measurement component used to evaluate business conversions following clicks on search or promotional links |
Approx. 90 days |
No direct personal data; utilizes algorithmically generated hashes to measure campaign performance |
5. Third-Party Service Providers and Infrastructure Integration
To guarantee high availability, top-tier network security, and continuous software performance, the platform integrates technical infrastructure provided by industry-leading third-party providers under strict contractual and security commitments:
5.1 Google Analytics (Google Traffic Statistics Service): We utilize Google Analytics 4 (GA4) to monitor macro traffic trends, bounce rates, and module engagement across our platform. TWT has implemented IP address anonymization/masking at the codebase level, ensuring that the last octet of your IP address is truncated prior to transmission to Google servers, preventing reverse identification of your physical identity. Furthermore, tracking plaintext sensitive personal data via GA4 is strictly prohibited. To review its official privacy policy, please visit: Google Official Privacy Policy.
5.2 Microsoft Clarity (Microsoft Diagnostic Analytics Service): We integrate Microsoft Clarity to analyze user interface friction points and experience hurdles through de-identified click heatmaps and session recordings, guiding UI/UX enhancements. Clarity incorporates client-side masking mechanisms by default, automatically suppressing passwords and sensitive personal information in input fields prior to transmission. Microsoft is restricted from using such data for cross-site ad attribution. To review its official terms, please visit: Microsoft Clarity Official Terms of Service.
5.3 Infrastructure Security & Network Risk Control (Alibaba Cloud Security Components): To mitigate malicious cyberattacks, credential stuffing, and safeguard high-concurrency communications, we deploy security components including Alibaba Cloud CAPTCHA (AliyunCaptcha) and network traffic distribution gateways across key pages. Technical Cookies deployed by these components (such as acw_tc and cdn_sec_tc) are strictly limited to validating request legitimacy at the protocol level, distributing network traffic, and blocking anomalous concurrency. They are never used to track individual commercial privacy or build behavioral profiles.
6. How Users Can Manage and Control Cookies
While our platform operates under the Singapore statutory notice-and-consent framework, we fully respect your absolute control over your terminal equipment. You may manage, restrict, or completely purge Cookies through the following channels:
6.1 Global Management via Browser Settings: Most modern web browsers accept Cookies by default but offer rich privacy configuration options. You can access "Settings/Options - Privacy & Security - Cookies and Site Data" within your browser to restrict all third-party Cookies, automatically clear Cookies upon closing the browser, or block Cookies from specific domains. Below are official configuration paths for common browsers:
(1) Google Chrome: Settings -＞ Privacy and security -＞ Third-party cookies;
(2) Microsoft Edge: Settings -＞ Cookies and site permissions -＞ Manage and delete cookies and site data;
(3) Apple Safari: Preferences -＞ Privacy -＞ Prevent cross-site tracking / Block all cookies;
(4) Mozilla Firefox: Settings -＞ Privacy & Security -＞ Enhanced Tracking Protection.
6.2 Dedicated Third-Party Opt-Out Tools: In addition to global browser configurations, you may independently opt out of third-party analytics via the following official channels:
(1) Google Analytics Opt-Out: You may download and install the official Google Analytics Opt-out Browser Add-on to disable tracking;
(2) Microsoft Clarity Opt-Out: You may manage preferences via the Microsoft Privacy Dashboard, or enable Do Not Track (DNT) or Global Privacy Control (GPC) signals in your browser, which Clarity respects automatically.
6.3 Impact of Disabling or Restricting Cookies: Please note that Cookies are foundational technical building blocks for modern web applications to maintain security and authenticated user sessions. If you block "Strictly Necessary Cookies" via browser settings, you will be unable to log into the TWT console, access console functions, or execute critical operations due to repeated security verification failures. Disabling "Performance & Analytics Cookies" will not affect your access to core business functions, but it will impair our ability to detect system defects and optimize software usability for your organization.
7. Policy Revisions and Version Updates
7.1 To reflect evolving TWT platform business features, technical iterations, and Singapore or global statutory amendments and regulatory guidelines, we may update or amend this Cookie Policy from time to time.
7.2 Where material amendments occur (such as changes to tracking technologies, onboarding of new sub-processors, or substantial modifications to processing purposes), we will publish the revised version on our official website and notify you via prominent interface notices or system broadcasts prior to the effective date. We encourage you to review this page periodically to stay informed of our latest Cookie compliance practices.
8. Contact Us
If you have any questions, comments, or complaints regarding this Cookie Policy, or wish to inquire further about our technical deployment in specific product scenarios, please feel free to contact our legal and data protection team through the following official channels:
(1) Operating Entity: HIGHSOON PTE. LTD.
(2) Registered Address: 8 Temasek Boulevard #21-03, Suntec Tower 3, Singapore 038988
(3) Official Customer Support Email: support@twt.com
(4) Data Protection Officer (DPO) Email: legal@twt.com
Upon receiving your inquiry and verifying your identity, we will provide a comprehensive written response within fifteen (15) business days as stipulated under the Singapore PDPA.