Cookie policy

Who runs AdXenx and what this policy covers

AdXenx is run by UpgradeX, a sole proprietorship registered with the RCCM in Cotonou (Benin) under number RB/ABC/24 A 117739 since 31 December 2024. The operator and publication director is SOVIMI Aziz Vorrez, a Beninese national.

Registered seat: Îlot 4600, Parcelle N, Zogbadjè, Abomey-Calavi, Atlantique, Benin.

This policy covers our two sites: adxenx.com (the advertiser dashboard) and publisher.adxenx.com (the publisher and creator portal). It explains what we put in your browser, why, and how to get rid of it.

It also explains what happens when an AdXenx banner is shown on a publisher's website, from the point of view of that site's visitor. That has its own section below.

For everything about your data beyond the browser, see our privacy policy.

Last updated: 4 September 2026.

Cookies, localStorage, sessionStorage: what we mean

Three different mechanisms, one subject: data a website writes onto your device.

A cookie is a small file a site places in your browser, which the browser then sends back to the server on its own with every request.

localStorage and sessionStorage are storage areas in the browser. The site writes information there and reads it back itself; nothing is sent to the server automatically. localStorage survives closing the browser; sessionStorage disappears when you close the tab.

We use all three. This policy treats them the same way and lists all of them, because from a privacy point of view the question is identical: what is being put on your device, and why.

Strictly necessary storage

These exist because the service cannot work without them. We do not ask your permission for them: without them there is no sign-in, and therefore no dashboard.

access_token and refresh_token - two cookies set when you sign in. They are httpOnly, which means the page's JavaScript cannot read them; only our server receives them. They prove it is you on every request. The first lasts 30 days, the second 12 months, so you are not forced to sign in again constantly. Both are deleted when you sign out.

auth-storage - a localStorage entry that keeps you signed in from one page to the next: your name, your email, your role, and the fact that you are signed in. No authentication token is written there.

add-site-store - a localStorage entry that keeps your draft while you are adding a space, meaning the website or app you want to monetise: what you have filled in so far and which step you reached. It is there so that a tab closed by accident does not make you start over. It is cleared once the space is added.

You can delete all of this from your browser, but you will be signed out and any draft in progress will be lost.

Non-essential storage

Two outside tools can write to your browser on our two sites. Neither is needed to use AdXenx.

Microsoft Clarity - a product analytics tool. It records how our pages are used: pages viewed, clicks, scrolling, and replays of how you moved through our interface. It sets its own cookies and its own storage entries, under its own names. To be plain about it: this is a recording of your behaviour in the interface, not a simple visit counter.

When you are signed in, we additionally pass Clarity your account identifier and your display name - or your email address if no name is set - so that a session can be traced back to an account when something goes wrong.

We use this to see where people get stuck and fix the interface. It is not used to decide which ads you are shown.

Cal.com - the booking widget for demo calls. Its script loads with the page that contains the button, before you click anything. If you open it, the scheduler is loaded from Cal.com's servers and may set its own cookies and storage. If you never open it, nothing happens.

The ad tag on publisher websites

When a publisher installs AdXenx on their website or app, a tag - a small script - asks our server for a banner for each ad slot.

That tag sets no cookies in the visitor's browser. It identifies the ad slot and the publisher's site, not the person. A visitor to a publisher's site has no account with us and is not attached to any profile.

The recording happens on our servers, when the request arrives. For each impression and each click we record: the campaign id, the creative id, the publisher site id, country, city, device type, the referrer (the page the request came from), the IP address, an invalid-traffic flag, and a timestamp. Country and city are derived from the IP address. The IP address is kept both in the clear and as a hash; it is used to place the request and to detect invalid traffic, which is excluded both from what the advertiser is billed and from what the publisher earns.

The tag does write three keys into sessionStorage on the publisher's own site: _adx_sid, a random session identifier; _adx_fired, the views already counted; and _adx_clk_dedup, the clicks already counted. Their only job is to stop the same impression or click being counted twice. sessionStorage belongs to each site separately and disappears when the tab is closed, so that identifier does not follow you from one publisher site to another, and we do not use it to build an advertising profile.

What we ask you, and when

Let's be straight about this: nothing non-essential loads until you have answered. The first time you visit adxenx.com or publisher.adxenx.com, a banner asks whether you accept usage analytics. Until you answer, Microsoft Clarity is not loaded at all: no script, no request to clarity.ms.

Refusing is as easy as accepting. The two buttons sit side by side, at the same size, in the same place. If you refuse, Clarity never loads. If you accept, it loads from that moment on, and not before.

Your answer is kept in your browser, not on our servers, and it is not attached to any request. You can change it at any time from the "Your choice" box at the bottom of this page.

The Cal.com widget is different: its script loads with the page that holds the booking button, before you click anything. It does not depend on the banner. The next section explains how to avoid it.

If you have a question about this, write to [email protected].

How to refuse or remove

For usage analytics, the simplest route is the "Your choice" box at the bottom of this page: your answer takes effect immediately, with no reload. For everything else, your browser remains the most powerful tool you have.

In your browser settings, look for the privacy section, then "cookies and site data". From there you can block third-party cookies, block or delete the data for one specific site, or clear everything. Clearing site data also removes localStorage and sessionStorage. Chrome, Firefox, Safari and Edge all offer this, on desktop and on mobile. A private browsing window wipes everything when you close it.

To refuse Microsoft Clarity specifically: block the clarity.ms domain in your browser or with a content blocker, or clear the site data for adxenx.com and publisher.adxenx.com.

To refuse Cal.com: don't open the booking widget. Its script loads with the page; to avoid it entirely, block the Cal.com domain in your browser.

Refusing the non-essential items does not stop you using AdXenx. You can open an account, fund and run a campaign, add a site, get paid, book and deliver a creator collaboration: all of it works without Clarity and without Cal.com.

If you also delete the necessary items, you will be signed out and any in-progress "add a space" draft will be lost. Nothing else goes: your campaigns, earnings, invoices and conversations live on our servers, not in your browser.

The other services we use

These are the other providers involved, and what they do - or don't do - in your browser. This list is complete.

Moneroo - payment processing, by card and by West African mobile money. When you pay or receive a payment, the payment page comes from Moneroo. Any cookies set at that moment are set by Moneroo under its own rules, not by us.

Cloudflare R2 - storage for the creatives you upload and the attachments exchanged in a deal. Files are served from that storage; we set no cookie on your device to do it.

An SMTP provider - the service emails: address verification, password reset, deal and payout notifications. This happens on our servers and puts nothing in your browser.

Telegram - internal alerts sent to the operator to keep an eye on the platform. It puts nothing in your browser, and no user content is sent there as a product feature.

Changes to this policy

If we add or remove a tool, or if what we store changes, this page is updated and the "last updated" date at the top changes with it.

We will not add a non-essential tool without listing it here. Have another look at this page from time to time, or write to us if you want to know what changed.

Contact us

For any question about this policy, about what is stored in your browser, or to ask us to delete data about you:

Email: [email protected] Phone: +229 0198981541

UpgradeX (AdXenx), sole proprietorship - RCCM Cotonou RB/ABC/24 A 117739 Îlot 4600, Parcelle N, Zogbadjè, Abomey-Calavi, Atlantique, Benin Operator and publication director: SOVIMI Aziz Vorrez