Cookies.
Clear expectations.
What the current interface stores in your browser.
Prepared for review at the operator’s request. Example operator: Uptiva. Example contact: info@uptiva.example (not an active mailbox). Country and legal entity: to be confirmed. No effective date has been adopted.
About this sample
This inventory describes the current implementation, with sample operator contact info@uptiva.example. It must be reviewed alongside any hosting, payment, identity or analytics services deployed by the operator.
Essential sign-in cookie
The application uses the uptiva_session cookie to maintain a signed-in session. It is configured as secure, SameSite=Lax and with a maximum age of fourteen days. Sign-out and browser controls can remove it earlier.
Sign-in and security state
Email-link sign-in uses a short-lived nonce cookie for its flow. Administrative access can use separate gate and session cookies. These are functional security mechanisms, not marketing identifiers.
Theme preference
The public site stores the selected appearance in localStorage under uptiva-front-theme. This is not an HTTP cookie. It persists until browser storage is cleared or the preference is changed.
Third-party services
Google sign-in, payment checkout and connected notification providers can have their own browser storage and policies when their features are used. The operator must maintain an accurate inventory of enabled providers.
Optional tracking
No advertising or analytics scripts are bundled in the current public site code. This statement does not audit scripts added by a host, proxy or future deployment. If optional tracking is introduced, review the applicable consent requirements before loading it.
Your controls
You can clear site cookies and local storage in your browser. Removing sign-in storage can sign you out; removing the theme preference resets appearance. Browser settings may also block storage.
Contact
Use the working Support link for questions. The example mailbox on this sample page is not active.