MindBridge Business Academy logoMindBridgeBusiness Academy

MindBridge Policy Framework

Cookie and Local Storage Policy

This policy explains the browser storage and network technologies used to deliver the publication, maintain continuity, protect the service, and measure operational performance.

Technology overview

Websites can use cookies, localStorage, sessionStorage, browser memory, network requests, pixels, scripts, and similar technologies. A cookie is a small value stored and sent with certain web requests. localStorage remains in the browser until it is removed. sessionStorage normally remains only for the current browser tab or session. A network request can transmit information without placing a cookie.

The current site relies primarily on localStorage, sessionStorage, first-party operational events, and third-party network requests. The site code does not need to label every network request as a cookie. This policy describes each technology according to what it actually does.

Browser storage and privacy settings

ItemPurposeTypical duration
Operational visitor identifierMaintains a pseudonymous identifier used for operational measurement and duplicate control.Until browser storage is cleared.
Session identifierMaintains continuity for events generated during the current browser session.Current browser session.
Optional measurement preferenceRemembers whether clearly identified optional measurement services should be enabled or disabled.Until the preference is changed or cleared.

These items support website delivery, session continuity, operational measurement, and link behavior. They are not brokerage, bank, securities, payment, or login credentials.

Technical implementation details

Technical implementation details
  • ITI_VISITOR_ID: localStorage identifier for operational visitor continuity.
  • ITI_SESSION_ID: sessionStorage identifier for the current session.
  • ITI_MEASUREMENT_CHOICE: localStorage value written as accepted or rejected for the optional measurement preference.

First-party operational measurement

The publication sends first-party operational events to support page performance, security review, traffic quality, route integrity, aggregate engagement analysis, and troubleshooting. Events can include page open, communications-link activity, browser language, entry URL, page code, route status, approximate country, and pseudonymous visitor or session identifiers.

Necessary operational events continue even when the optional measurement preference is disabled. The preference page is not represented as stopping processing that the current code continues to perform. Operational event names and endpoint behavior are described in customer terms rather than exposing internal routing rules.

Optional measurement

The current preference control is reserved for measurement services that are separately identified as optional. Enabling the preference permits such a service to operate if it is added and clearly connected to the control. Disabling the preference prevents that optional service from being activated through this preference mechanism.

At present, the control does not erase necessary operational identifiers, stop delivery or security requests, reverse information already processed, or change the independent practices of a third-party service that you choose to open. See Privacy Choices for the current control.

Third-party network requests

The site’s network delivery and security provider may receive request and security information needed to deliver and protect the site. Google Fonts may receive the IP address and request information needed to provide the font files. TradingView may receive device, browser, request, and interaction information when the market component loads. WhatsApp receives information when you choose to open its service. Each provider controls its own cookies and similar technologies under its own policies.

Blocking a third-party script, font, or widget can affect appearance or functionality. A third-party cookie or identifier, if used by the provider, is controlled by that provider rather than by the local preference stored by this site.

Global Privacy Control

Global Privacy Control is a browser signal used in some jurisdictions to communicate an opt-out from sale, sharing, or targeted advertising. The current site does not describe its operation as selling personal data or using personal data for targeted advertising. As a result, the present data practices do not include a sale or targeted advertising activity for the signal to disable.

If the data practices change, any legally required recognition of an applicable opt-out preference signal must be implemented and explained before the new activity begins. The current optional measurement preference remains a separate control.

Managing and clearing storage

You can use the Privacy Choices page to enable, disable, or clear the optional measurement preference. Browser settings can remove localStorage, sessionStorage, cookies, cached files, and site permissions. Private browsing may shorten storage duration, and browser extensions may block requests.

Clearing storage can create a new operational identifier, reset duplicate controls, or remove the saved optional preference. The site does not attempt to restore data that a browser has removed.

Storage-to-function review

Each browser storage item should map to an active site function, a stated purpose, and a typical duration. A stored key that no longer supports an active function should be removed from the code and inventory. A function that begins using a new key should update this policy before or with the site change.

Operational event records should use the minimum fields reasonably needed to understand page delivery, route integrity, communications-link use and route integrity. They should not be presented as brokerage, banking, investment-account, or authentication records.

Retention, security, and changes

Browser storage remains for the periods stated above unless the browser, user, operating system, or site removes it earlier. Server-side operational records are retained only as reasonably needed for security, integrity, aggregate measurement, troubleshooting, legal obligations, and dispute handling. Exact retention can vary by event type and system.

This policy will be updated when the technologies, providers, purposes, or controls materially change. The current version remains available through the Policy Center.