Tencent WorkBuddy Cookies Policy

For the purposes of this Cookies Policy, “we”, “us” and “our” means Tencent Cloud International Pte. Ltd., a Singapore registered company located at 10 Anson Road, #21-07, International Plaza, Singapore 079903.

For the purpose of any personal data we collect through cookies, we are the data controller. You can find our details in the Privacy Policy applicable to this service and how we use such data. Our data protection officer can be contacted at cloudlegalnotices@tencent.com.

We use cookies, log files, pixel tags, web beacons, scripts, eTags and similar files or technologies to collect and store the information we automatically collect about your device and use of WorkBuddy (the “Service”). You can find out more about cookies and how to control them in the information below.

We only use non-essential cookies with your consent.

What are cookies?
What types of cookies do we use?
How to Control Cookies
Changes to this Cookies Policy
Need More Information?
Cookies that have been set in the past
Contact us

What are cookies?

Cookies are text files containing small amounts of information which are downloaded to your browser or device when you visit a certain web address. Cookies are then sent back to the originating web address on each subsequent visit, or to another web address that recognises that cookie. Cookies are widely used in order to make the Service work, or to work more efficiently, as well as to provide information to the Service team.

Cookies do lots of different jobs, like letting you navigate between pages efficiently, remembering your log-in and preferences, and generally improving the user experience. Cookies may tell us, for example, whether you have accessed or used the Service before or whether you are a new visitor or user. They can also help to ensure that advertising you see online are more relevant to you and your interests. Cookies can help us safeguard the security of our data and services and detect the cheating, hacking and fraud against our products and services. For instance, cookies can store ticket information, which can be used by the server to verify if the log-in is made by yourself independently. The encrypted information in the ticket can also be used to prevent a variety of types of attacks, cross-site information theft, and access with disguised identity.

There are two broad categories of cookies:

First party cookies, served directly by us to your device.
Third party cookies, which are served by a third party on our behalf.

Cookies can remain on your browser or device for different periods of time. Some cookies are 'session cookies', meaning that they exist only while your browser or application is open. These are deleted automatically once you close your browser or application. Other cookies are 'permanent cookies', meaning that they survive after your browser or application is closed. They can be used by the Service to recognise your device when you visit and use the Service again.

What types of cookies do we use?

The types of cookies used by us and our partners in connection with the Service can be classified into the following categories, namely 'essential cookies', 'functionality cookies' and 'analytics and performance cookies'. We have set out some further information about each category, and the purposes of the cookies we and third parties set in the following table.

Cookie name	What it does and what data it processes	Duration of cookie	First or Third party cookie	How to Control Cookies
Cookies necessary for essential services
loginType	To record your login type (main account/sub-account) and help determine permissions	179 days	Third party	Please see the instructions set out in 'How to control cookies' below.
mfaRMId	To store a Multi-Factor Authentication related ID	24 days
ownerUin	To store your unique user ID	Session
qcmainCSRFToken	To prevent cross-site request forgery attacks	Session
qcommunity_identify_id	To identify users of Tencent Cloud for login and community interactions	341 days
refreshSession	To extend session validity without re-logins	Session
saas_synced_session	To sync login statuses	Session
skey	To store a core account login credential for identity verification purposes	Session
subAccountLoginPage	To identify configuration for sub-account login flows	29 days
systemTimeGap	To help prevent replay attacks	Session
tinyid	For cross-product user identification	Session
uin	For identity recognition and permission controls	Session
appid	For resource attribution and billing identification	Session
ewpUid	For ticket system session identification	303 days
__Secure-1PAPISID	To securely call Google APIs in logged-in user context	394 days
__Secure-1PSID	To maintain your logged-in status	394 days
__Secure-1PSIDCC	To enhance account security and anti-CSRF	365 days
__Secure-1PSIDTS	For session validity verification	365 days
__Secure-3PAPISID	For embedded cross-site Google services	394 days
__Secure-3PSID	To maintain login status in embedded scenarios	394 days
__Secure-3PSIDCC	For account security verification of cross-site requests	365 days
__Secure-3PSIDTS	For session renewal and validity judgments	365 days
AEC	To ensure requests from browsers are authentic and secure	177 days
HSID	To prevent accounts from being maliciously hijacked	394 days
SAPISID	For calling APIs in logged-in user context	394 days
SEARCH_SAMESITE	For cookies behavior control of cross-site requests	176 days
SID	To maintain login status	394 days
SIDCC	To detect abnormal account activity	365 days
SSID	To verify account login security	394 days
OTZ	To conduct cross-service account experience analysis	30 days
ACCOUNT_CHOOSER	To record the list of accounts logged in on the device	400 days
__Host-GAPS	To enhance login security	400 days
LSID	To conduct login status maintenance within the account system	400 days
__Host-1PLSID	To manage login session IDs limited to the host scope	400 days
__Host-3PLSID	To manage login session IDs in cross-site login scenarios	400 days
qcommunity_session	To identify login sessions for community login state maintenance	23 days
APISID	To identify user and to log in	394 days
397f1c3795037d16	To request routing or anti-scraping identification	Session	First party
session	To maintain login status	Session
session_2	To isolate sessions in multi-device or multi-account scenarios	Session
AUTH_SESSION_ID	To track sessions in OAuth/OIDC login flow	Session
KEYCLOAK_SESSION	To unify the login state across applications	365 days
KC_RESTART	To recover and restart when login flow is interrupted	Session
KEYCLOAK_IDENTITY	To persist logged-in user identity	Session
cookietest	To check if the browser is set to block or to permit cookies	Session
Functionality Cookies
lastLoginIdentity	To record your last login identity and login method recommendation	179 days	Third party	Please see the instructions set out in 'How to control cookies' below.
moduleId	To page-route and monitor statistics	Session
regionId	To record your currently selected region	Session
themeType	To record your preferred interface theme (e.g., light/dark)	Session
intl	To determine page language version	29 days
language	To determine your preferred language settings for localized display	399 days
oneid_web_lang	To record web page language preference	365 days
Performance / Analytics Cookies
qcloud_uid	To track sessions and behaviour statistics	400 days	Third party	Please see the instructions set out in 'How to control cookies' below.
trafficParams	For traffic attribution analysis	59 days
test_cookie	To determine whether the browser supports cookies	Session
IDE	To measure ad effectiveness and personalized delivery	400 days
NID	To record search/ad-related preferences	183 days
_ga	To distinguish unique visitors	341 days
_ga_RPMZTEBERQ	To persist and maintain your unique session state	341 days
_gcl_au	For ad conversion attribution	28 days
_qimei_fingerprint	For anti-fraud purposes	306 days
_qimei_h38	For cross-product visitor analysis	306 days
_qimei_q36	For behaviour statistics and deduplication	306 days
pgv_pvid	For traffic statistics and deduplication	338 days
qcloud_from	For market channel attribution	23 days
qcloud_visitId	To collect statistical data on user activity during the session	Session
qcstats_ouin-100045088556	To categorise the user and segmentation analysis	Session
qcstats_seo_keywords	For search traffic attribution	29 days
qcstats_utype-100045088556	For user profiling and segmentation	Session
sensorsdata2015jssdkcross	For user behaviour tracking and statistics	359 days
x-client-ssid	To identify the given session and perform security verification	Session
x_host_key_access_https	To provide site security access control	Session
_gclxxxx	To store and track conversions	60 days
_gcl_au	To record data on visitor source	84 days	First party
_TDID_CK	To identify site visitor devices and gather statistics	Session	First party

How to Control Cookies

You have the right to choose whether or not to accept cookies and we have explained how you can exercise this right below. When you use our Service for the first time, we will provide you with a notice which lets you know how we use cookies, why we use them and how you can change which cookies you accept. You can opt-into non-essential cookies or change your preferences at any time here. Please note that if you choose not to receive our cookies, we cannot guarantee that your experience of our Service will be as good as it could otherwise be.

Alternatively, most browsers allow you to change your cookies settings. These settings will typically be found in the “options” or “preferences” menu of your browser. In order to understand these settings, the following links may be helpful for popular browsers, otherwise you should use the “Help” option in your browser for more details.

Changes to this Cookies Policy

We will update this Cookies Policy to reflect changes in our practices and services. When we post changes to this Cookies Policy, we will revise the "Last Updated" date at the top of this Cookies Policy. If we make any material changes in the way we collect, use, and/or share information held in cookies, we will notify you by prominently posting notice of the changes when you log in to or use the Service. We recommend that you check this page from time to time to inform yourself of any changes in this Cookies Policy or any of our other policies.

Need More Information?

If you would like to find out more about cookies and their use on the Internet, you may find the following link useful:

All About Cookies

Cookies that have been set in the past

If you have disabled one or more cookies, we may still use information collected from cookies prior to your disabled preference being set, however, we will stop using the disabled cookie to collect any further information.

Contact us

If you have any questions or comments about this Cookies Policy, or privacy matters generally, please contact us via email at cloudlegalnotices@tencent.com.