VERTEXIA COOKIE POLICY

Document ID: VERTEXIA-COOKIE-POLICY-v1.1 Status: Frozen for first publication Version: 1.1 Effective date: From the first public publication of this version by Vertexia, as recorded in the legal release registry. Document frozen on: 17 October 2026

This Cookie Policy explains how the Vertexia website may use cookies and similar technologies.

It is intended to describe the actual technical behaviour of the production website.

Vertexia does not use generic cookie-policy wording to claim that technologies are present when they have not actually been implemented.

This Policy must therefore remain aligned with the runtime behaviour of the Vertexia website.

2. Relationship with the Privacy Policy

This Cookie Policy should be read together with the:

Vertexia Privacy Policy

VERTEXIA-PRIVACY-POLICY-v1.2

The Privacy Policy explains more generally how Vertexia processes personal data, including:

business enquiries;
Product purchases;
licence administration;
Stripe Managed Payments;
Product delivery;
Product Support;
contractual evidence;
and other business processing.

This Cookie Policy addresses specifically the use of cookies and similar technologies on Vertexia-controlled website pages.

It is an informational document and is not a separate contractual acceptance instrument.

3. Website operator

The website operator is:

Legal operator: Mimoun Mouhajir — sole proprietor / natural-person enterprise Commercial name: Vertexia Business address: Avenue du Scheutbosch 27, Box 2, 1080 Molenbeek-Saint-Jean, Belgium Belgian enterprise number: 1042.698.035 Privacy contact: contact@vertexia.be

Final identification must correspond with the Vertexia Legal Notice and Privacy Policy.

A cookie is a small piece of information that a website or related service may place or read on a user's device through a browser.

Cookies may, depending on their purpose, be used for matters such as:

maintaining a technical session;
remembering a requested preference;
providing security;
supporting authentication;
remembering consent preferences;
measuring usage;
or enabling advertising or tracking.

The mere technical possibility of using cookies does not mean that Vertexia uses all of these categories.

5. Similar technologies

This Policy also applies, where relevant, to technologies that perform a similar function or access information on a user's terminal equipment, including certain uses of:

localStorage;
sessionStorage;
browser identifiers;
pixels;
tags;
embedded third-party scripts;
software-development kits;
and comparable client-side technologies.

The legal and technical assessment depends on what the technology actually does, not merely on whether it is formally called a “cookie”.

6. Vertexia privacy-minimising baseline

For the version frozen on 17 October 2026, the prepared vertexia.be website does not set cookies or use local or session storage. Payment takes place on an external Stripe/Link page governed by its own policies.

The site uses local fonts and media, without marketing trackers, analytics, third-party video players or embedded Stripe.js. The purchase control is a simple link to the external Payment Link.

The automated initial-load audit of the final prepared local artefacts on 17 October 2026 covered the homepage, Product page, six legal pages and production demonstration build. Each was opened in a fresh browser context. No cookies, localStorage keys, sessionStorage keys or third-party requests were observed. This identifies the tested artefacts; it does not describe cookies on the external Checkout or independently verify Netlify's production infrastructure.

7. Strictly necessary technologies

Certain cookies or comparable technologies may be used without prior consent where they are genuinely strictly necessary under applicable law.

This may include technologies necessary:

to transmit a communication over an electronic communications network;
to provide a service expressly requested by the user;
to maintain essential security;
or to perform another technically indispensable function qualifying for the applicable exemption.

A technology is not classified as strictly necessary merely because it is useful to Vertexia.

The exemption must be assessed according to the technology's actual purpose and implementation.

8. Information about strictly necessary technologies

The absence of a consent requirement does not mean that strictly necessary technologies should be hidden from users.

Where such technologies are used, Vertexia should provide clear information concerning their relevant purpose.

The production cookie inventory must identify their actual characteristics where applicable.

Vertexia must not invent:

cookie names;
providers;
functions;
or durations

before those facts have been verified from the real production implementation.

9. Non-essential technologies

Technologies that are not genuinely strictly necessary must not be treated as exempt merely for convenience.

Where applicable law requires prior consent, the relevant technology must not be placed, read or activated before valid consent has been obtained.

Examples may include certain technologies used for:

audience measurement;
analytics;
personalisation that is not necessary for a requested service;
advertising;
behavioural profiling;
retargeting;
cross-site tracking;
or social-media tracking.

The actual legal classification must be based on the technology implemented at that time.

10. Analytics

Vertexia does not use an analytics service in the prepared website covered by this Policy.

If analytics is later introduced, Vertexia must determine before activation:

what data is collected;
which provider receives it;
whether browser storage or another tracker is used;
the applicable purpose;
the applicable consent requirement;
any personal-data processing involved;
retention;
international transfers;
and required Privacy Policy updates.

Vertexia must not assume that analytics is automatically exempt from consent.

11. Advertising and behavioural tracking

The intended Vertexia website does not require advertising or behavioural-tracking technologies for the current commercial architecture.

Vertexia therefore does not plan, by default, to use:

advertising pixels;
behavioural advertising cookies;
retargeting technologies;
cross-site advertising identifiers;
or marketing-profile trackers.

If this changes in the future, the relevant technologies must not be introduced silently.

The legal, privacy and consent architecture must first be reassessed.

Where a technology requires consent, that consent must satisfy the applicable legal requirements.

In particular, the mechanism must not treat:

inactivity;
pre-selected options;
or simple continued browsing

as valid affirmative consent where such consent is legally required.

Users must receive adequate information before making the relevant choice.

Where applicable, withdrawing or changing a consent choice must be reasonably accessible.

Vertexia must not add a cookie-consent banner simply because cookie banners are common on commercial websites.

The correct implementation depends on the actual technologies used.

If the verified production website uses only technologies that genuinely qualify as strictly necessary, a consent banner should not be introduced merely for appearance.

The user should still receive appropriate information about any strictly necessary technologies that are actually used.

If the production audit identifies one or more non-essential technologies requiring prior consent, an appropriate consent mechanism becomes mandatory before those technologies operate.

A consent banner or preference centre must not be implemented unless it corresponds to actual technical controls.

A user interface claiming to reject a technology while allowing that technology to execute anyway is not acceptable.

Where consent is required, technical enforcement must correspond with the user's choice.

A consent mechanism must therefore be tested through actual browser and network behaviour rather than assessed solely by visual appearance.

15. Browser storage

Vertexia may use browser storage only where there is an identified and legitimate technical purpose.

Before LIVE publication, the audit must inspect at least:

cookies;
localStorage;
sessionStorage;
and relevant browser-accessible storage.

The final Policy must describe any relevant production use accurately.

A storage key must not be classified solely from its name.

Its actual function and behaviour must be examined.

16. Server-side processing

Not all website processing involves cookies or browser storage.

For example, a server may process limited request information for:

security;
delivery of the requested page;
fault diagnosis;
or infrastructure operation.

Such processing may fall under the Privacy Policy even where no cookie is stored on the user's device.

This Cookie Policy should therefore not be interpreted as an exhaustive description of all personal-data processing by Vertexia.

17. Stripe-hosted Checkout

Urbia A2 purchases are intended to use Stripe Managed Payments through Stripe-hosted Checkout.

The Stripe / Link hosted transaction environment is technically and operationally distinct from ordinary Vertexia-controlled website pages.

Stripe, Link and their applicable affiliates may use their own:

cookies;
browser storage;
security mechanisms;
fraud-prevention technologies;
payment technologies;
and other tracking or terminal-access mechanisms

in accordance with their own applicable policies and legal responsibilities.

Vertexia must not list Stripe-hosted cookies as if Vertexia itself placed them directly on vertexia.be when that is not technically the case.

18. Checkout redirect

The payment link redirects the purchaser to an external Stripe / Link page, which is subject to that provider's own privacy and cookie policies.

A user's decision to proceed from a Vertexia Product Page to Stripe-hosted Checkout may result in the user leaving the Vertexia-controlled web environment and entering the applicable Stripe / Link transaction environment.

The privacy and cookie information applicable within that hosted environment may therefore differ from the technologies used on Vertexia-controlled pages.

Vertexia's Cookie Policy describes the Vertexia-controlled site and does not replace Stripe / Link customer-facing privacy information.

19. Stripe scripts or embedded components

The website uses externally hosted Checkout; ordinary Vertexia pages do not embed payment components.

If a future implementation loads:

Stripe.js;
an embedded Checkout;
a Payment Element;
Link components;
or another Stripe-controlled browser component

directly on a Vertexia page, the cookie and browser-storage impact must be reassessed before LIVE use.

Such a change may require:

an updated runtime inventory;
updated Privacy and Cookie Policies;
a consent assessment;
and changes to technical controls.

The fact that Stripe is already used for hosted Checkout does not eliminate that reassessment.

20. External websites

Vertexia pages may contain links to external websites or services.

Following an external link does not mean that Vertexia controls the cookies or technologies used by the destination website.

Users should consult the relevant third party's information where appropriate.

Vertexia remains responsible for assessing any third-party technology that it actively embeds or causes to execute on its own pages.

Surface	Cookies	localStorage	sessionStorage	Third-party requests on initial load
Prepared Vertexia homepage, Product page and six legal pages	None observed	No keys observed	No keys observed	None observed
Prepared production demonstration build	None observed	No keys observed	No keys observed	None observed

The inventory records the clean-context automated audit on 17 October 2026. There are no cookie names, providers or expiry periods to list for these observed surfaces. Previous browser checks and the founder's operational attestations are retained in the evidence record.

The external Stripe/Link payment environment has its own policies. Its technologies are not presented as cookies set by Vertexia. An authenticated Netlify draft-session cookie does not establish a cookie set for an ordinary visitor.

22. Runtime audit

Before commercial launch, Vertexia must perform a runtime audit using a clean browser context.

The audit should examine at minimum:

initial visit to the Vertexia website;
navigation between ordinary pages;
Product pages;
legal pages;
checkout initiation;
redirection to Stripe-hosted Checkout;
return from Checkout in test mode;
cookies created or read;
localStorage;
sessionStorage;
third-party network requests;
externally loaded scripts or resources.

The audit should distinguish:

Vertexia-controlled behaviour

from

Stripe / Link hosted-environment behaviour.

The resulting inventory must be retained as LIVE-readiness evidence.

23. Changes in website technology

A material change to the website technology may require a new cookie assessment.

Examples include introducing:

analytics;
advertising;
embedded media;
social widgets;
chat services;
customer-support widgets;
A/B testing;
embedded payment interfaces;
consent platforms;
or new third-party frontend scripts.

A technology must not be considered acceptable merely because the Cookie Policy can be edited afterwards.

Where prior consent is legally required, the technical control must exist before the technology is activated.

24. Urbia A2 customer deployments

This Policy governs the Vertexia website.

It does not automatically govern websites or applications created by Licensees or End Clients using Urbia A2.

Urbia A2 is a source-code Product that customers may customise and deploy independently.

A Licensee or End Client may choose to introduce its own:

analytics;
CRM;
advertising;
maps;
video embeds;
chat tools;
cookies;
forms;
hosting;
or other integrations.

The operator of that deployment is responsible for assessing its own cookie and privacy obligations.

Vertexia's Cookie Policy must not be copied into a customer deployment and presented as automatically accurate without reviewing the customer's actual technical configuration.

25. User choices and browser controls

Users may have browser-level options to:

view stored cookies;
delete cookies;
block certain storage;
or restrict particular website technologies.

Browser controls do not replace a website operator's obligation to obtain valid prior consent where applicable law requires it.

Similarly, the fact that a user can technically delete a cookie later does not make an otherwise required prior consent unnecessary.

26. Personal data and cookies

Where a cookie or similar technology involves personal data, the applicable data-protection principles also apply.

Depending on the activity, this may include requirements relating to:

transparency;
purpose limitation;
data minimisation;
security;
legal basis;
recipients;
retention;
international transfers;
and data-subject rights.

Further information is provided in the Vertexia Privacy Policy.

27. Rights and enquiries

Questions concerning Vertexia's use of cookies, browser storage or similar technologies may be sent to:

Privacy contact: contact@vertexia.be

Where the relevant processing involves personal data, applicable rights are described in:

VERTEXIA-PRIVACY-POLICY-v1.2

Where a technology is operated independently by Stripe, Link or another external provider, certain requests may need to be addressed directly to that provider according to its own privacy framework.

Vertexia may update this Policy where:

website technology changes;
a provider is added or removed;
the cookie/storage inventory changes;
consent requirements change;
or applicable law or regulatory guidance changes.

The Policy must describe actual current behaviour.

A change in technology should therefore trigger review of this document rather than leaving an inaccurate historical inventory publicly displayed.

Material changes receive an appropriate new policy version.

29. Versioning

This release is identified as:

VERTEXIA-COOKIE-POLICY-v1.1

Each frozen production version must be reproducible.

A materially revised Policy must receive a new version identifier rather than silently overwriting the previous frozen release.

The SHA-256 of a production release is calculated only after the exact final file bytes exist.

END — VERTEXIA COOKIE POLICY — v1.1