Storage on the public site exists to preserve continuity, not to manufacture surveillance.

A few client-side features in Brionix rely on browser storage so the experience remains stable across visits. The storage posture is intentionally narrow and tied to product function.

Essential storage

The site uses browser storage where it helps preserve continuity in the public and account experiences. That includes saved workspace preferences, shortlist behavior, and other lightweight state needed to avoid resetting the session every visit.

Currency and interface preferences can be preserved locally.
Buyer workspace context may be stored on the device for continuity.
The goal is experience stability, not aggressive profiling.

Preference-level behavior

Some storage is there to support quality-of-life features such as remembered UI state and previously opened modules. Without it, the product still works, but it becomes less coherent between sessions.

Storage supports a smoother return visit.
Preferences can usually be cleared through the browser.
Loss of saved state does not affect property ownership or transaction records.

Analytics posture

Brionix keeps the tracking posture intentionally light. The focus is on understanding whether the product is useful, which modules matter, and where requests are getting stuck rather than building a broad advertising profile.

Product-oriented measurement over ad-tech style tracking.
No needlessly complex consent theatre on static pages.
If the data ever expands materially, the policy should be updated in the open.

Read the privacy page→Ask a policy question→