Cookies Policy
Last updated: · Uxier portfolio
The portfolio application does not set cookies or use tracking technologies for analytics or advertising. There is no cookie-consent banner because the application does not currently activate those features. The day/night control uses an optional ?theme=dark URL parameter, not a cookie or 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
- Cookies: none set by the application or origin web server. Cloudflare may use necessary security cookies when a protection challenge is triggered.
- Analytics and advertising: no analytics SDKs, tracking pixels, advertising tags or cross-site identifiers.
- 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 preference is stored just for opening this page. 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 by this application.
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. It is not used to identify you across visits or sent to an analytics service.
The selected public panel may appear in the address after # and in browser history. Your name, phone number, brief and chat messages are not added to the URL.
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. The current portfolio does not require cookies for its form validation, navigation or local chat. 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 demonstration form does not deliver questions or requests. These statements cover the published portfolio and demonstration projects, not future integrations.