Legal

Privacy Policy

This notice explains what operational data NexoIP may process across nexoip.com and the related hubs, why it is processed and which third-party services participate in delivery, analytics and audience flows.

Coverage Public network

root and thematic hubs

Processors Infrastructure and measurement

only when the function requires it

Local control Consent and storage

first-party state when applicable

1. Scope

This policy applies to the public NexoIP network, including the root site and the AI, Gaming, Crypto, Biohacking and Smart Home hubs.

It covers normal page delivery, newsletter flows, account surfaces, security logging and audience measurement used to operate and improve the network.

2. Data we may process

Depending on the page and the action you take, NexoIP may process server logs, device and browser metadata, referral data, interaction events, newsletter submissions and account-related identifiers.

The network may also store first-party browser state for consent, session continuity, layout preferences or account snapshots when those features are active.

Request and delivery logs used for uptime, abuse prevention and diagnostics.
Newsletter submission data when you explicitly send a form.
Account and session state needed to keep user-facing tools working.
Audience and UX telemetry when analytics tooling is enabled on a property.

3. Third-party services and processors

NexoIP relies on infrastructure and measurement vendors to publish pages and operate network services. Those vendors only receive the data needed for the function they provide.

A page may expose a Google AdSense publisher identifier in metadata even when ad slots are off. That closes publisher identity for platform verification and does not, by itself, mean that display ads are active on the page.

Cloudflare for hosting, caching, DNS, edge delivery and worker endpoints.
Operational worker endpoints for newsletter and control-plane actions.
Microsoft Clarity for behavioural analytics and session replay when enabled.
Google services such as Search Console verification, sitemap discovery and AdSense publisher identity.

4. Why the data is used

Operational data is processed to render pages, secure the network, understand failures, measure demand, improve navigation, operate newsletters and keep account surfaces available.

Not every page uses every processor. Tooling is enabled by property, by feature and by the operational state of the network.

5. Cookies, consent and local storage

Some features use browser cookies or local storage to remember consent choices, maintain account continuity or reduce repeated prompts.

When a property requires consent for measurement or ads, the network stores that preference in first-party browser storage and applies it to the relevant client integrations.

Consent state can be stored in first-party browser storage.
Analytics or ad-related storage may depend on the configured consent policy.
You can clear browser storage locally through your browser settings.

6. Retention, controls and updates

Retention depends on the operational purpose of the data. Security, delivery and analytics logs are kept only for the time needed to run, secure or review the service.

This notice may be updated when infrastructure, analytics or commercial tooling changes. The latest public version is the one published on this page.