← Privacy & legal resources

TrustPort Beacon · Legal information

Cookies & browser storage

Last updated: 26 October 2026

The inspected web client uses browser storage for application functionality and preferences. This page distinguishes that storage from HTTP cookies; production hosting, authentication and security layers may behave differently and should be checked in a live-browser audit.

Storage used by the web client

  • Local storage: theme and currency preferences; signed-in user/session token data; and, for platform-owner workflows, impersonation session details.
  • Session storage: selected view/filter state for some screens.

Authentication/session storage is used to provide requested account functionality and should be protected as sensitive data. The precise keys, lifetimes, logout/deletion behavior and security model should be reviewed. Preference and interface state are used to remember choices.

Cookies and third-party storage

No advertising or analytics-cookie mechanism was identified in the inspected frontend source. This is not confirmation that the production website or infrastructure sets no cookies: hosting, security controls, authentication APIs and embedded third-party services must be tested in the deployed environment. A consent mechanism may be required depending on the storage, its purpose and the jurisdictions served.

Managing storage

You can clear site data through your browser settings. Doing so may sign you out or reset preferences. Do not clear session data if you are in the middle of a transaction or administrative workflow.

Before publication, verify cookies and storage in production, identify any provider-set identifiers, document expiry and purpose, and implement consent controls where required.