Cookie Transparency

1. Doctrine

Zero Surveillance.

This site does not deploy third-party behavioural pixels.
It does not run advertising trackers.
It does not maintain cross-site profiling logic.
It does not sell, lease, or syndicate visitor behaviour.

The operating standard is restraint.

2. Anti-AI Clause

Site content, page structure, metadata, and associated assets are not authorised for AI or LLM training, model tuning, synthetic dataset generation, or retrieval harvesting.

This prohibition is not decorative. It is enforced at the edge.

AELION applies edge-side filtering and bot controls to identify and block AI crawlers and related scraping behaviour before content is served. Cloudflare documents dedicated controls for blocking verified AI bots and similar crawler traffic, and also provides controls for expressing that site content is not to be used for AI training. (Cloudflare Docs)

3. Technical Cookies

Only technical cookies required for security and edge integrity are used.

XSRF-TOKEN
Laravel sets an encrypted XSRF-TOKEN cookie to support CSRF protection on same-origin requests. Laravel’s documentation states that this cookie is included with framework responses and is used to populate the X-XSRF-TOKEN request header. (Laravel)

Cloudflare Enterprise edge tokens
Where Cloudflare challenge, bot, or edge integrity controls are active, Cloudflare may set strictly technical cookies such as __cf_bm or cf_clearance. Cloudflare states that __cf_bm is generated separately for each site and is not used to track users from site to site. Cloudflare also documents the cf_clearance cookie as part of its challenge and request validation flow. (Cloudflare Docs)

No marketing cookie layer sits behind these controls.
No audience enrichment layer is attached to them.
They exist to keep the site stable and requests legitimate.

4. Telemetry

This site uses anonymised server-side telemetry for infrastructure health only.

That telemetry is limited to operational signals such as request performance, edge events, error rates, uptime state, and service degradation indicators. It is used to maintain platform integrity, not to construct behavioural profiles.

There is no third-party remarketing loop.
There is no session resale logic.
There is no surveillance analytics stack.

5. Do Not Track

AELION natively respects Do Not Track browser signals.

The DNT header was defined by the W3C as a mechanism for expressing a user’s preference regarding tracking. This site’s position is straightforward: when that signal is present, no tracking behaviour is activated because tracking behaviour is not part of the architecture in the first place. (W3C)

6. Operating Standard

This page is not a banner apology.

It is the technical standard of the firm:

No behavioural advertising trackers.
No third-party surveillance pixels.
No consent theatre for systems we do not deploy.
No use of site content for AI training.
Only security cookies.
Only operational telemetry.

That is the rule.