Cookie categories in use
The landing page currently distinguishes between necessary cookies and optional experience cookies linked to the live AI widget.
- Necessary cookies keep the site functioning, remember language and consent preferences, and support security controls.
- Optional experience cookies allow the delayed live widget and interactive demo flow to load after consent.
- Optional cookies do not turn on automatically under the Thai PDPA consent flow.
How consent works
The page shows a consent banner and a preferences modal. Users can accept all cookies, allow only necessary cookies, or customize later through the persistent cookie settings button in the footer.
- Consent choices are stored in a first-party cookie named
aileo_cookie_consent. - The current consent memory is stored for 180 days unless the user changes it sooner.
- Users can reopen settings and change their choice at any time.
Widget behaviour after consent
The AILEO live widget is gated behind optional cookie consent. This keeps the page PDPA-aware while preserving the visual flow of the landing page after the user opts in.
- Without optional consent, the landing page still works and the hero content remains visible.
- With optional consent, the widget loads after a short delay instead of being forced at first paint.
- This approach balances user experience, transparency, and performance.
Cookie detail snapshot
| Name | Category | Purpose | Retention |
|---|---|---|---|
| aileo_cookie_consent | Necessary | Stores the visitor consent choice for cookie categories | 180 days |
| Language route memory | Necessary | Keeps the landing experience on the selected TH/EN route when applicable | Session or browser-defined |
| Live widget experience | Optional | Enables the delayed AI widget and demo bridge after user opt-in | Only after consent |
If you want a deeper description of AILEO security architecture, retention, and DLP controls, continue to the Security & Data Policy page.