Cookies Policy

Last updated: 8 September 2026 · Uxier portfolio

The portfolio does not use analytics or advertising cookies. The main Virtual Me / MeAI chat sets one strictly necessary first-party cookie to enforce its bounded consultation allowance and protect the operator’s monthly API budget. The day/night and language controls use optional ?theme=dark and ?lang= URL parameters, not browser storage.

1. What cookies and similar technologies are

Cookies are small pieces of information a website can ask your browser to store and send back on later requests. Other technologies can also save or access information on a device. Their purpose matters: they may support a feature or be used for measurement, profiling and advertising.

2. What this version uses

• AI allowance cookie: __Host-uxier_chat is a random opaque value set by uxier.co after a main-chat request. It is Secure, HttpOnly, SameSite=Strict, path / and expires after 24 hours. It contains no messages, phone number, name or raw network address and is used only to enforce the chat allowance.
• Cloudflare security: Cloudflare may use necessary security cookies when a protection challenge is triggered.
• Aggregate first-party analytics: a small same-origin script on the main portfolio sends fixed public section/action labels and coarse technical categories. Its random session identifier stays in page memory only; there are no analytics cookies, persistent identifiers, third-party analytics SDKs, advertising tags or cross-site tracking. Do Not Track and Global Privacy Control disable this collection. See the Privacy Policy for the 31-day private-server retention and daily aggregate Telegram reports.
• Persistent app storage: no localStorage, sessionStorage, IndexedDB or service worker.
• Third-party embeds: none. Fonts, scripts, icons and numbering rules are served from this site.

No application cookie is set merely for opening this page; the AI allowance cookie is set only after a request reaches the main chat endpoint. Deleting it can create a new browser identifier, but the separate keyed network and monthly limits still apply. Cloudflare security features may use cookies such as cf_clearance when you complete a challenge; their use and duration depend on the protection triggered. See Cloudflare’s cookie documentation. No analytics or advertising cookies are intentionally enabled.

3. Temporary state is not a tracking cookie

The app holds form entries, chat messages, open-panel state and animation positions in the current page’s memory. This allows the interface to respond and keeps an unsent draft while moving between panels. Form entries and message contents are not used to identify you across visits or sent to analytics. The analytics collector separately measures allowlisted public section names and coarse activity, without reading these drafts.

The selected public panel may appear in the address after # and in browser history. Work form values and the full conversation are not added to site URLs. If you choose Continue in WhatsApp, its final link contains the separate editable draft you reviewed. That text can appear in browser history; the ordinary chat and phone field are not copied automatically.

4. Browser caching and autofill

Your browser may cache static files such as fonts, images, CSS and JavaScript to load the site faster. This is different from the site setting a tracking identifier. Browser autofill, session restore and history are controlled by your browser and may retain or restore information independently of this application.

Reloading starts a fresh app state, but it is not a promise to erase browser-managed copies. On a shared device, clear fields, close the tab and check your browser’s autofill, history and site-data controls.

5. Your controls

You can use your browser settings to block or remove cookies and clear cached files or other site data. Form validation, navigation and the Bravon/Lotia local chats do not require cookies. Blocking the necessary main-chat cookie can prevent reliable allowance enforcement, so the server may decline AI replies. Extensions and browser or network services may use their own technologies outside this application’s control.

6. If features change

Before adding analytics, embedded content, persistent preferences or other storage/access technology, its purpose and provider must be reviewed. This page must be updated with the actual technologies, durations and controls. Where applicable law requires consent, those technologies must stay inactive until the visitor has given the required choice, with a way to withdraw it.

7. More information

The Privacy Policy explains the current hosting, data handling and contact route. The main Work form and an explicitly consented chat contact card can deliver enquiries to Vlad via Telegram. Bravon/Lotia demonstration forms remain unconnected. These statements cover the published portfolio and demonstration projects, not future integrations.