1. Summary
Saber Vault’s own code uses browser localStorage for functional state (network selection, Converter outputs, Desk books). It does not currently set a first-party advertising cookie.
Third-party embeds—especially the TradingView Advanced Chart and Google Fonts—may set cookies or receive your IP address. Those technologies are not required to read the White Paper or Legal Documents; they are used on the Trade Desk and for typography.
2. Strictly necessary / functional storage
saber_network — which settlement network is selected.
saber_issuers — Issuer KYB packets, Program Review results, and public contact used on Asset Profiles.
saber_custody — asset-instance custody packets, title references, and attestation hashes.
saber_holders — holder allowlist packets, including wallet addresses and contact emails.
saber_oracle, saber_freezes — valuation refresh records and officer freeze flags.
saber_redeems — redeem-and-burn log for operational utility.
saber_mints, saber_mint_spec, saber_auth, saber_memo — Converter design records.
saber_desk, saber_desk_v2 — Desk balances, orders, bins, LP, tape.
saber_protocol — SBRV burned, protocol LP SBRV, locked/forfeited/returned access bonds, team-ops USDC, and protocol events.
saber_consent — Legal Documents version, electronic-records consent (eSign), and whether TradingView market data may load.
These are necessary to provide the features you request, except saber_consent.marketData which is optional. The Service does not offer a “no storage” mode for the Desk or Converter; if you refuse storage, do not use those tools, or use a private window and expect records to vanish.
3. Third-party cookies and pixels
TradingView widgets may use cookies and similar IDs for chart preferences and fraud/abuse protection. Google may log font requests. The preview host may use its own storage for PWA/install chrome.
Operator does not control opt-out for those parties except as follows: the first-visit banner and Cookie preferences control let you decline TradingView. If declined, the Trade Desk does not inject the TradingView script and shows a local tape instead. Google Fonts still load with the document in this version.
4. Your choices
A Cookie & Local Storage banner is presented on first visit and again if the Legal Documents version changes. Accept records saber_consent with market data on, eSign true, and the current Legal Documents version. Necessary only records the same agreement with market data off. Manage lets you change the TradingView toggle later from the footer “Cookie preferences” control. Legal Documents stay readable while the banner is open.
You can delete site data in your browser settings. That logs you out of any local Desk session and deletes mint specifications on that device. You can block third-party cookies; if TradingView is blocked or declined, the Desk still shows the local order book, liquidity book, and local tape.
5. Do not sell or share
Operator does not sell personal information and does not share it for cross-context behavioral advertising in this build. Global Privacy Control signals are not consumed by a first-party ad stack because there is none. Third parties may not honor GPC.