1. What this policy covers
This Cookie Policy explains how ConnexaX and third-party services used on ConnexaX can use cookies, localStorage, Cache Storage, web beacons, IP addresses and similar technologies. It should be read together with the ConnexaX Privacy Policy.
2. Browser storage used by ConnexaX features
ConnexaX can use browser-side storage for product functionality rather than advertising. Examples include AI image history, generated-audio counters, PWA resources, cached assets or interface state. Depending on the feature and browser, this can involve localStorage, IndexedDB, Cache Storage or similar technologies.
Blocking all browser storage can affect convenience features, cached resources or PWA behavior even when advertising is not involved.
3. Google AdSense cookies and identifiers
ConnexaX uses Google AdSense. When Google advertising services operate on the site, third-party vendors including Google may place and read cookies on your browser or use web beacons, IP addresses and other identifiers as a result of ad serving.
These technologies can be used for functions such as ad delivery, security, invalid-traffic detection, fraud prevention, frequency capping, measurement, reporting and, where permitted by consent and law, ad personalization.
Google explains how it uses information from publisher sites at How Google uses information from sites or apps that use its services.
4. Google-certified CMP for the EEA, UK and Switzerland
For personalized AdSense advertising in the European Economic Area, the United Kingdom and Switzerland, Google requires a Google-certified consent management platform (CMP) integrated with the IAB Transparency and Consent Framework (TCF).
ConnexaX code includes the AdSense tag so Google Privacy & Messaging can operate when the European regulations message is configured and published in the connected AdSense account. Where that message applies, the Google CMP can present consent choices, management options and participating advertising-vendor information and can communicate the resulting consent signals.
CMP configuration is completed in Google AdSense under Privacy & messaging. The website code alone cannot activate, publish or replace that account-level configuration.
5. Why ConnexaX no longer uses its old custom advertising banner
Earlier ConnexaX versions used a custom Accept/Decline banner backed by a localStorage key. That custom mechanism has been removed from the current code path for Google advertising consent because it is not a substitute for a Google-certified TCF CMP where Google requires one.
A legacy value from an older visit may remain in a visitor's browser until that browser storage is cleared, but the current AdSense loader does not use that legacy value to decide whether the Google advertising tag is present.
6. Personalized, non-personalized and limited ads
The type of advertising that can be served depends on the visitor's region, consent status, Google configuration and applicable law. Google may serve personalized, non-personalized, limited or no ads. Some technical processing can still be required for ad delivery, security, fraud prevention, frequency controls or measurement where permitted.
7. Changing or withdrawing advertising choices
Where Google's European regulations message applies, users can manage or withdraw consent through the privacy and cookie settings entry point provided by Google's Privacy & Messaging system. Google can show the consent message again so a visitor can revise an earlier decision.
Google also provides advertising controls through Google Ads Settings.
8. Browser-level controls
Most browsers allow you to block, delete or restrict cookies and local site data. You can also clear ConnexaX localStorage, IndexedDB, Cache Storage and other site data from browser settings. Blocking storage or third-party technologies can change how some website features, ads or consent messages operate.
9. Other third-party technologies
Hosting, CDN, security, email, AI and advertising providers can use technical identifiers, request logs or their own storage when their services are used. These providers can have separate cookie and privacy policies. The specific data involved depends on the requested feature.
10. No blanket claim that every request is local
Some ConnexaX creator tools process selected files locally, but the website still makes ordinary network requests for pages, scripts, models, fonts, ads, security resources and network-dependent AI features. A local file-processing claim therefore does not mean that the entire website operates without network communication.
11. Updates to this policy
We may update this Cookie Policy when ConnexaX changes advertising providers, consent configuration, browser-storage behavior or product features. The date at the top of this page identifies the current revision.
12. Contact
Cookie, advertising or privacy questions can be sent to support@connexax.com.