Cookies Policy

01

What cookies and similar technologies are

Cookies are small text files stored by a website in your browser. Similar technologies include local storage, session storage, pixels, SDKs, scripts and device identifiers that store or read information on a device.

They can keep you signed in, remember choices, maintain a checkout, protect against fraud, measure website use or connect an advertising click with a later registration or purchase.

First-party technologies are set by an Axion domain. Third-party technologies may be set or read by a provider such as Google or an advertising platform.

02

Categories we use

Category	Purpose	Typical consent status
Necessary	Authentication, security, fraud prevention, load balancing, checkout state, payment handoff, consent storage and core service delivery.	Always active where required to provide the service you request.
Preferences	Remember non-essential interface, language, display or personalisation choices.	Based on your selected consent profile where required.
Analytics	Measure visits, pages, ecommerce events, errors, device categories, campaign performance and service improvement.	Activated according to your consent choice and applicable law.
Marketing	Advertising attribution, conversion measurement, remarketing, frequency controls and campaign optimisation.	Activated according to your consent choice and applicable law.

03

Axion first-party storage

Axion may use first-party cookies or browser storage including:

Name or type	Purpose	Typical duration
Session and authentication cookies	Maintain login, protect authenticated requests and secure the customer or admin session.	Session or a limited persistent period.
`axion_attribution_v2`	Preserves first-touch campaign, referral and visitor/session information across the customer journey.	Local storage until deleted or replaced.
`axion_consent_v2`	Stores your optional analytics, marketing and preferences choice.	Local storage until changed or deleted.
`axion_tracking_pending_v2`	Temporarily queues first-party events when a request must be retried.	Short-lived local storage; old entries are limited and replaced.
Checkout and duplicate-prevention keys	Remember selected programme state and avoid resending the same funnel event on refresh.	Session storage or a short expiry.

Technical names and durations may change as the platform is updated, but their purpose remains within the categories described here.

04

Google Analytics and Tag Manager

Where analytics is permitted, Axion uses Google Analytics 4 and Google Tag Manager to measure page views, registrations, challenge selections, checkout activity, purchases and other service events.

Google technologies may use identifiers such as:

_ga to distinguish visitors;
_ga_<measurement-id> to maintain session state;
Google advertising click identifiers such as gclid, gbraid or wbraid when present in a campaign URL; and
the temporary _gl linker parameter when moving between genuinely different root domains involved in the payment journey.

Axion uses consent settings intended to deny optional analytics or advertising storage until the relevant permission applies. Google may process limited consent-mode signals where configured.

05

Advertising and social platforms

If marketing consent is active and the relevant platform is enabled, Axion may use advertising technologies from providers such as Meta, TikTok or Microsoft to measure campaign performance and create audiences.

Possible identifiers include _fbp, _fbc, fbclid, _ttp, ttclid and msclkid. The exact providers enabled at any time depend on Axion’s active campaigns and dashboard configuration.

Advertising providers may combine information received from Axion with information they already hold under their own terms and privacy policies.

06

Portal and payment-domain continuity

Axion’s main website and portal use related axionfunded.com subdomains and can share appropriately scoped first-party cookies. The secure payment page may operate on a different root domain.

When needed, Axion and analytics tools may transfer a short-lived signed attribution token or linker value to preserve the original session and campaign. The token is used for continuity and is removed from the visible address where the implementation permits.

Payment providers may set their own strictly necessary cookies for security, fraud prevention and transaction processing. Their policies apply to those technologies.

07

Your choices and how to change them

When the consent banner is displayed, you can accept or reject optional categories. Your selection is stored so the banner does not need to appear on every page.

You can also:

delete cookies and site data through your browser settings and revisit the website to make a new choice;
block third-party cookies or use browser privacy controls;
use platform-level advertising controls offered by Google, Meta, TikTok, Microsoft or your device; and
contact support@axionfunded.com if you cannot access a consent choice.

Blocking necessary storage may prevent login, checkout, fraud protection, order continuity or secure payments from working. Rejecting optional cookies should not prevent the core service from operating.

08

Retention and provider information

Cookie duration varies from a browser session to a persistent period determined by the purpose and provider configuration. Axion periodically reviews enabled tags and retention settings.

Third-party providers control their own identifiers and may change names or durations. Their privacy and cookie documentation explains their independent processing. The Privacy Policy explains broader personal-data retention and sharing.

09

Updates and contact

We may update this policy when technologies, providers or legal requirements change. The latest date is shown at the top of the page.

Questions about cookies or optional tracking may be sent to support@axionfunded.com.