What this policy covers
“Cookies” here includes HTTP cookies and comparable storage or access technology such as local storage, identifiers, pixels, tags and SDKs. Standard browser caching used to retrieve public files is not treated as a site-authored identifier. The authenticated live platform is a separate product surface with its own inventory and notices.
Current declared inventory
Source inspection found no site-authored cookies, local or session storage, IndexedDB, service worker, analytics tag, advertising pixel, embedded chat, video or scheduling widget. Public assets are served from the same origin. Cookie Settings presents this same inventory and therefore stores no unnecessary preference record.
Strictly necessary technology
A future technology may be treated as necessary only when it is essential to transmit a communication, provide a feature explicitly requested by the visitor or protect that requested service within the applicable legal exception. Convenience, measurement and advertising are not silently reclassified as necessary.
Optional categories are inactive
Preferences, analytics and performance, advertising and targeting, and embedded third-party services are not active in the reviewed public build. If introduced, they must be declared by exact provider, purpose, data, duration, recipient and transfer boundary and remain off until the required valid choice is recorded.
Hosting and edge boundary
A CDN, WAF or hosting layer can set its own strictly necessary security technology even when the site source does not. The current source claim therefore remains subject to a production network audit. Any detected item must be added to the inventory with its provider, purpose, legal exception and lifetime before publication.
External links and Google search
The site does not embed Google search or contact Google in the background. Google receives the query and technical request data only after the visitor chooses external search and leaves this site in a new tab. Other external links and the live platform are governed by the destination's own cookie and privacy practices.
Cookie Settings and browser signals
The reviewed build makes Cookie Settings available from the footer. Because no optional technology is declared, it displays status rather than fake toggles and does not create a preference cookie. Global Privacy Control is detected locally for transparency; it is not treated as GDPR consent and the site activates no sale, sharing or marketing technology regardless of the signal.
Controls for future optional technology
Optional technology must be blocked before a choice, default to off, and use equally accessible Accept, Reject and Customize actions when consent is required. A visitor must be able to reopen settings and withdraw as easily as they accepted. Consent cannot be inferred from scrolling, silence, a preselected box or acceptance of website terms.
Inventory changes and questions
A new provider, purpose, category or material retention change requires a versioned inventory, policy update, renewed technical tests and legal review before activation. Email info@advanexus.com with “Cookie question” in the subject and do not include unrelated sensitive data.
Legal and privacy contact
Pending legal verification
info@advanexus.com