PolyBuzz Cookie Policy
Effective Date: October 27, 2026
Last Updated: October 27, 2026
Introduction
This Cookie Policy explains how PolyBuzz.ai ("PolyBuzz", "we", "us", or "our") uses cookies and similar tracking technologies on our websites, mobile applications, and other online services that link to this Policy (collectively, the "Services").
It describes:
- the types of technologies we use;
- why we use them;
- the third parties that may set them; and
- the choices you have, and how to exercise them.
This Policy is part of, and should be read together with, our Privacy Policy, which explains how we handle the personal information collected through these technologies and describes the privacy rights available to you.
For users in the United Kingdom, optional cookies are your choice. You may reject them and continue using the Services. We do not treat continued use, scrolling, silence or closing a banner as consent. You can change or withdraw your choices at any time as described in Section 7 ("Your Choices").
1. What Are Cookies and Similar Technologies?
In this Policy, "cookies" refers collectively to all technologies that store or access information on the device you use to access the Services — including your computer, tablet, or mobile phone.
These technologies include:
|
Technology |
How it works |
|
HTTP cookies |
Small text files placed on your device by a website you visit. |
|
Local storage / session storage |
Data stored by your browser or app on your device (e.g., HTML5 local storage, locally stored objects). |
|
Pixels / web beacons / clear GIFs |
Tiny invisible images or code snippets, often embedded in web pages or emails, that notify us when content has been loaded or viewed. |
|
SDKs (software development kits) |
Code provided by third parties and built into our mobile apps, which can collect device and usage information. |
|
Device identifiers |
Advertising or vendor identifiers made available by your device's operating system (e.g., IDFA on iOS, AAID on Android). |
Note: We use the single term "cookies" throughout this Policy for readability. Where a technology other than a browser cookie applies — for example, an SDK in our mobile app — the same principles and choices described here apply.
2. Why We Use Cookies
We use cookies to operate, secure, and improve the Services. Specifically, we use them to:
- Keep the Services working— authenticate you, keep you logged in, remember your session, balance traffic, and protect against fraud and abuse;
- Remember your preferences— language, region, display settings, device type, and other choices you have made;
- Understand usage— measure how many people use the Services, which features are used, where users encounter errors, and how users move through the Services;
- Improve the Services— run research, diagnostics, and analytics, test new features, and develop new functionality;
- Measure marketing— understand how users discover PolyBuzz and whether our advertising and email campaigns are effective;
- Personalize advertising— where permitted, deliver advertising that is more relevant to you and limit how often you see the same ad.
We may use pixels and similar technologies in emails to measure delivery, opens and interactions. For UK users, we obtain prior consent before using non-exempt email tracking technologies. Consent to receive marketing emails does not, by itself, constitute consent to tracking. You can withdraw tracking consent through [insert verified email-tracking preference link]. Turning off automatic image loading in your email client may also limit some tracking, but does not prevent all forms of measurement.
3. How Cookies Are Classified
3.1 By origin
- First-party cookies— set by PolyBuzz on the domain you are visiting.
- Third-party cookies— set by another party, such as a provider of analytics, advertising, or embedded features, when you use the Services.
3.2 By lifespan
- Session cookies— temporary. They collect and store information only for the duration of your visit and are deleted when you close your browser.
- Persistent cookies— remain on your device for a defined period (or until you delete them manually). Depending on the cookie, this can range from a few minutes to several years. We set retention periods based on the purpose of each cookie and do not keep them longer than necessary.
3.3 By function
|
Category |
Purpose |
Consent required? |
|
Strictly Necessary |
Used only where strictly necessary to provide a service you request, such as authentication, session management, security, fraud prevention and storing cookie choices. This category does not include additional analytics, advertising or profiling uses. |
No — these cannot be switched off. |
|
Performance & Analytics |
Measure and analyze how the Services are used, including traffic volume, feature usage, error rates, session length, and the effectiveness of our advertising and emails. |
Yes (where required by law) |
|
Functional |
Enhance functionality and personalization, such as remembering your language, region, device type, or playback settings. |
Yes (where required by law) |
|
Advertising & Targeting |
Build a profile of your interests to show relevant advertising, manage ad frequency, and measure campaign performance. |
Yes (where required by law) |
4. Cookies Used on the Services
The table below summarizes the categories of cookies used on the Services, who sets them, and how long they last. Cookies identified as PolyBuzz are first-party cookies; all others are third-party cookies.
|
PolyBuzz Cookie Usage Table |
||||
|
Type of Cookie |
What these cookies do |
Source |
Cookie Name |
Duration |
|
Strictly Necessary |
Maintains the user's login state so that features requiring sign-in can be accessed; a persistent expiry is set in this browser. |
PolyBuzz |
session |
400 days |
|
Strictly Necessary / Performance |
Identifies the client and supports API calls, service routing and risk control; also used for access behavior and performance analytics. |
PolyBuzz |
poly_cuid |
365 days |
|
Strictly Necessary |
Identifies the payment device and provides a device identifier for payment anti-fraud and risk control. |
AWX_RISK_ID |
N/A |
|
|
Strictly Necessary |
An auxiliary flag used by the Airwallex device risk-control SDK. |
Airwallex |
__AWX_TEMP_F_D__ |
N/A |
|
Functionality |
Stores privacy and advertising consent choices and supports the Google privacy messaging flow. |
FCCDCF |
390 days |
|
|
Functionality |
Remembers the interface language selected by the user. |
PolyBuzz |
site-locale |
365 days |
|
Functionality |
Stores the numeric code corresponding to the interface language. |
PolyBuzz |
site-locale-key |
365 days |
|
Functionality |
Legacy interface language preference; still retained in the current browser. |
PolyBuzz |
polyai-locale |
N/A |
|
Functionality |
Legacy language code; still retained in the current browser. |
PolyBuzz |
polyai-locale-key |
N/A |
|
Functionality |
Remembers the viewport width to adapt page layout across different screens. |
PolyBuzz |
client_viewport_width |
365 days |
|
Functionality |
Remembers the viewport height to support page layout calculations. |
PolyBuzz |
client_viewport_height |
365 days |
|
Functionality |
Remembers the sign-out or auto sign-in state of Google One Tap so as to avoid an automatic sign-in loop. |
g_state |
180 days |
|
|
Performance |
Stores a browser identifier in order to associate visits and behavioral events. |
PolyBuzz |
__zs_cuid |
365 days |
|
Performance |
Stores the experiment bucket flag for age verification. |
PolyBuzz |
age_verab |
365 days |
|
Performance |
Distinguishes visitors and measures website visits and usage. |
_ga |
400 days; official default: 2 years |
|
|
Performance |
Maintains the session state for this website's GA4 property. |
Google Analytics |
_ga_4W1CFQB47F |
400 days; official default: 2 years |
|
Performance |
An analytics cookie used by Google's privacy and user messaging products. |
FCNEC |
365 days |
|
|
Advertising |
Associates ad clicks and conversions in order to measure advertising effectiveness. |
_gcl_au |
90 days |
|
|
Advertising |
Associates browser visits with conversion events for Meta ad effectiveness measurement. |
Meta |
_fbp |
90 days |
|
Advertising |
Supports the display, measurement and security of Google ads. |
__gads |
390 days |
|
|
Advertising |
Stores the Google advertising identifier to support ad delivery and security. |
Google AdSense / Ad Manager |
__gpi |
390 days |
|
Advertising |
Supports the security features of Google advertising products. |
Google advertising products |
__eoi |
180 days |
|
Advertising |
A flag retained within the advertising identity chain. |
⠀ |
_au_1d |
365 days |
|
Advertising |
Stores an advertising identifier used to recognize and match the browser. |
LiveIntent |
_lc2_fpi |
400 days |
|
Advertising |
Metadata accompanying the LiveIntent advertising identifier. |
LiveIntent |
_lc2_fpi_meta |
400 days |
|
Advertising |
Provides the advertising identifier to page scripts for use in the identity matching flow. |
LiveIntent |
_lc2_fpi_js |
Session |
|
Advertising |
Domain information used by the advertising identifier, assisting first-party cookie domain handling. |
LiveIntent |
_li_dcdm_c |
Session |
|
Advertising |
Synchronization status of the LiveIntent advertising identity chain. |
LiveIntent (polybuzz.ai) |
_li_ss |
400 days |
|
Advertising |
Records the source of the RampID identifier to support advertising identity matching. |
_lr_env_src_ats |
30 days |
|
|
Advertising |
Controls retries and concurrent requests of the advertising identity interface. |
_lr_retry_request |
1 hour |
|
|
Advertising |
Stores a first-party shared advertising identifier for use in programmatic ad bidding. |
_sharedid |
365 days |
|
|
Advertising |
A status flag accompanying SharedID. |
Prebid SharedID |
_sharedid_cst |
365 days |
|
Advertising |
Stores Criteo advertising identification information to support ad matching and bidding. |
Criteo (polybuzz.ai) |
cto_bundle |
390 days 8 hours |
|
Advertising |
A flag associated with Criteo ad bidding. |
Criteo (polybuzz.ai) |
cto_bidid |
390 days 8 hours |
|
Advertising |
A browser association flag for the AMX advertising service. |
__amc |
N/A |
|
|
Advertising |
A short-term status flag for the AMX advertising service. |
AMX / a-mo.net |
_Amc_b |
N/A |
|
Advertising |
A short-term status flag for the AMX advertising service. |
AMX / a-mo.net |
_Amc_s |
N/A |
|
Advertising |
A short-term status flag for the AMX advertising service. |
AMX / a-mo.net |
_Amc_t |
N/A |
|
Advertising |
Records which partners ID5 has established user identifier associations with, for cookie synchronization. |
3pi |
90 days |
|
|
Advertising |
A browser identifier for the Amazon advertising system; used for advertising identification. |
Amazon Ads |
ad-id |
N/A |
|
Advertising |
A browser identifier on the 1rx.io advertising domain. |
1rx.io |
_rxuuid |
N/A |
|
⠀ |
A flag on the Google DoubleClick domain. |
Google / DoubleClick |
__mggpc__ |
N/A |
|
Strictly Necessary |
Verifies the Google account and its login state, and protects the security of the sign-in process. |
SID, HSID |
400 days |
|
|
⠀ |
Associated flags that appear during the Google sign-in flow. |
Google (google.com) |
SSID, __Secure-1PSID, __Secure-3PSID |
400 days |
|
⠀ |
Associated status flags on the Google domain. |
Google (google.com) |
SIDCC, __Secure-1PSIDCC, __Secure-3PSIDCC |
365 days |
|
⠀ |
Associated flags on the Google domain. |
Google (google.com) |
APISID, SAPISID, __Secure-1PAPISID, __Secure-3PAPISID |
400 days |
|
Functionality / Advertising |
Stores Google service preferences and may also be used for ad personalization within Google services. |
NID |
183 days |
|
|
Advertising |
An associated flag for Meta advertising services, supporting ad identification and effectiveness measurement. |
Meta (facebook.com) |
fr |
90 days |
|
Advertising |
A cookie support test flag for the Google DoubleClick advertising domain. |
Google DoubleClick (doubleclick.net) |
test_cookie |
15 minutes |
|
Advertising |
A status flag for the LiveIntent advertising identity synchronization chain. |
LiveIntent (i.liadm.com, path /s) |
_li_ss |
30 days |
|
Advertising |
A browser identifier on the LiveIntent advertising domain, used for advertising identity matching. |
LiveIntent (liadm.com) |
lidid |
400 days |
|
Advertising |
Stores the ID5 user identifier to support advertising identity matching. |
id5 |
5 minutes |
|
|
Advertising |
Stores synchronization chain information, callbacks or consent information during ID5 identity synchronization. |
callback, cf, cip, cnac, car, gdpr |
Session |
|
|
Advertising |
An auxiliary flag for the ID5 synchronization chain. |
ID5 (id5-sync.com) |
gpp |
Session |
|
Advertising |
Identification information on the Criteo advertising domain, supporting ad matching and bidding. |
Criteo (criteo.com) |
cto_bundle, uid |
390 days |
|
Advertising |
Accompanying flags for ad bidding and identity synchronization. |
audit, audit_p, khaos, khaos_p |
365 days |
|
|
Advertising |
Browser identification for advertising and synchronization of partner identifiers. |
TDID, TDCPM |
365 days |
|
|
Advertising |
An associated identifier for the Venatus advertising service. |
Venatus (edge.venatusmedia.com) |
u |
365 days |
|
⠀ |
An associated flag on the Xandr advertising domain. |
Xandr (adnxs.com) |
XANDR_PANID |
90 days |
|
⠀ |
An associated flag on the Yahoo domain. |
Yahoo (yahoo.com) |
A3 |
365 days |
|
⠀ |
A session flag in the browser. |
crwdcntrl.net |
_cc_cc |
Session |
|
⠀ |
A session flag on an associated domain. |
ad.gt |
au_3p_check |
Session |
|
⠀ |
A persistent flag on an associated domain. |
ad.gt |
au_id |
365 days |
|
⠀ |
A short-term flag on an associated domain. |
ccgateway.net |
ccsid |
30 minutes |
|
⠀ |
A persistent flag on an associated domain. |
ccgateway.net |
ccuid |
89 days |
|
⠀ |
A flag on an associated domain. |
go.affec.tv |
ck |
365 days |
|
⠀ |
A flag on an associated domain. |
go.affec.tv |
pt |
90 days |
|
⠀ |
Accompanying flags on an associated domain. |
cpx.to |
dsp_pub_common, dsp_ZTP |
365 days |
|
⠀ |
A flag on an associated domain. |
rqtrk.eu |
browser_id |
365 days |
|
⠀ |
A short-term status flag on an associated domain. |
rqtrk.eu |
zsc |
1 day |
|
⠀ |
Persistent flags on an advertising domain. |
smartadserver.com |
pbw, TestIfCookieP |
365 days |
|
⠀ |
An expired flag on an advertising domain. |
smartadserver.com |
TestIfCookie |
365 days |
|
⠀ |
A session flag on an associated domain. |
contextweb.com |
INGRESSCOOKIE |
Session |
|
⠀ |
Persistent flags on an associated domain. |
contextweb.com |
V, VP |
360 days |
|
⠀ |
A flag on an associated domain. |
onetag-sys.com |
OTP |
396 days |
|
⠀ |
An identifier on an associated domain. |
demdex.net |
demdex |
180 days |
This list may be updated from time to time. The cookies actually set depend on how you use the Services, the device and browser you use, your region, and whether you are logged in. The most current, itemized list is always available in our Cookie Preference Center (accessible via the "Cookie Settings" link in the footer of our website and in-app).
5. Third Parties and Cross-Border Transfers
Some third-party providers may process personal information collected through cookies on our behalf, or for their own purposes (for example, as independent advertising partners). These providers are contractually required to use the information only for the purposes we specify, and are responsible for their own compliance with applicable law when acting as independent controllers.
Because some of these providers are located outside your country or region, information collected through cookies may be transferred to, and processed in, countries other than your own — including the United States. Where we transfer personal information across borders, we rely on appropriate safeguards as described in our Privacy Policy.
6. Mobile Applications
Our mobile applications do not use browser cookies in the same way websites do. Instead, they may use SDKs, local storage, and device identifiers (such as your device's advertising ID) for the purposes described in Section 2.
You can control these technologies through your device settings:
- iOS:Settings → Privacy & Security → Tracking (disable "Allow Apps to Request to Track"); or Settings → Privacy & Security → Apple Advertising to disable personalized ads.
- Android:Settings → Privacy → Ads → Delete advertising ID / opt out of ads personalization.
If you disable or reset your advertising ID, we and our partners will not be able to use it for advertising purposes, but strictly necessary and non-advertising functionality will continue to work.
7. Your Choices
You have several ways to control cookies. Except for strictly necessary cookies, you can withdraw or change your consent at any time, free of charge.
7.1 Cookie Preference Center
We provide a Cookie Preference Center where you can accept or reject each category of cookies. For UK users, our initial cookie notice offers equally prominent options to "Accept all", "Reject all optional cookies" and "Manage preferences". Optional technologies are off until you actively consent. The Cookie Preference Center lets you choose separately between optional purposes and view the relevant providers. You can reopen it at any time using "Cookie Settings" in the website footer or app settings and withdraw consent as easily as you gave it, free of charge. Withdrawal stops future storage, access and associated processing based on that consent; we remove relevant technologies within our control and communicate withdrawal to the relevant providers.
7.2 Browser controls
Most browsers allow you to view, block, or delete cookies, and to block third-party cookies specifically. Instructions are usually found under "Settings," "Preferences," or "Options," in the "Privacy" or "Security" section. Common browsers:
- Chrome:Settings → Privacy and security → Third-party cookies
- Safari:Settings → Privacy → Manage Website Data
- Firefox:Settings → Privacy & Security → Cookies and Site Data
- Edge:Settings → Cookies and site permissions → Manage and delete cookies
You can also set your browser to notify you before a cookie is placed, or to browse in "private" / "incognito" mode, in which case cookies are deleted when the session ends.
7.3 Do Not Track and Global Privacy Control
- Global Privacy Control (GPC):We treat a GPC signal from your browser or device as a valid request to opt out of the sale or sharing of personal information and of targeted advertising, where applicable law requires us to honor it.
- Do Not Track (DNT):There is still no common industry standard for how to respond to DNT signals. We therefore do not currently respond to DNT signals, but we do honor GPC as described above.
7.4 Industry opt-out tools
For advertising cookies, you can also use the opt-out programs operated by industry bodies, for example:
- Digital Advertising Alliance (DAA) — aboutads.info
- Network Advertising Initiative (NAI) — networkadvertising.org
- European Interactive Digital Advertising Alliance (EDAA) — eu
7.5 Consequences of blocking cookies
If you block or delete cookies, parts of the Services may not work as intended. For example, you may be signed out each time you visit, your preferences may not be saved, and certain features may be unavailable. Blocking cookies does not remove all tracking: strictly necessary cookies remain active, and some information (such as your IP address and basic device information) may still be collected as part of operating the Services.
8. Region-Specific Information
- European Economic Area and United Kingdom.We ask for your consent before setting any cookie that is not strictly necessary, and we do not set non-essential cookies until you have consented. You may withdraw consent at any time through the Cookie Preference Center.
- United States (including California, Colorado, Virginia, Connecticut, Utah, and Texas).We do not sell personal information for money. We may, however, "share" personal information for cross-context behavioral advertising, or use it for targeted advertising, as those terms are defined under applicable state privacy laws. You may opt out through the Cookie Preference Center, by broadcasting a GPC signal, or by contacting us at the address in Section 12.
- Brazil (LGPD) and other jurisdictions.Where local law requires consent for non-essential cookies, we obtain it before setting them, and you may withdraw it at any time.
- United Arab Emirates.We apply the consent and transparency principles described above to users in the UAE, and we do not knowingly set non-essential cookies on the devices of users located in the UAE without a lawful basis.
9. Data Retention
We keep information collected through cookies only for as long as necessary to achieve the purposes described in this Policy, or as long as required by law. Retention periods are set by cookie category (see Section 4) and are reviewed periodically. When a cookie expires, the information it holds is deleted automatically; you may also delete cookies manually at any time through your browser or the Cookie Preference Center.
10. Children
The Services are not directed to children, and we do not knowingly use advertising or profiling cookies in relation to users we know to be under the age required by applicable law in their jurisdiction. If you believe a child has provided information to us through the Services, please contact us using the details below.
11. Updates to This Policy
We may update this Cookie Policy to reflect changes in technologies, providers or applicable law. We will update the "Last Updated" date and explain material changes through the Services or other appropriate means. Where a change introduces a new purpose or otherwise falls outside your existing consent, we will obtain fresh consent before activating the relevant optional technologies. Updating this Policy does not itself constitute your consent.
12. Contact Us
If you have questions about this Cookie Policy or about our use of cookies, please contact us at:
PolyBuzz Legal Department
Email: legal@mail.polybuzz.ai
