1. TradingView is third-party
The Trade Desk may load TradingView’s Advanced Chart widget from TradingView’s servers when you grant market-data consent (saber_consent.marketData). Operator does not operate that widget, does not warrant its uptime, and does not sublicense the underlying exchange data. TradingView’s terms and privacy policy govern that component.
If you decline market data, if the widget is blocked in a preview frame, or if the script fails, the Desk shows a local tape generated from this interface’s last price and prints. That local tape is not a licensed market-data product.
2. Mapped symbols are references only
SBRV is not a listed TradingView symbol. The native pair displays a USDC settlement reference (for example a USD stablecoin tape) so the chart has a real feed. RWA classes may map to sector proxies (REIT, gold, rates, equity indices, and similar). Those symbols are not the Factory instrument, not a NAV, and not a valuation opinion of the underlying real-world asset.
3. Local order book and liquidity book
Depth, spreads, bin inventory, and “fills” are produced by a browser matching engine with seed liquidity. They can be empty, skewed, or stale. They are not a national securities exchange, not an ATS, not a consolidated tape, and not evidence of public float or fair market value.
Native USDC/SBRV books remain separate from Factory RWA books. Do not read a print in one book as a print in the other.
4. No redistribution
You may not scrape, retransmit, or commercially redistribute TradingView data obtained through the Service. You may not present the local tape as “Saber Vault last sale” to third parties as if it were an official price.
5. Delay, gaps, and errors
Feeds may be delayed, halted, or wrong. Charts may disagree with the local mid. Operator is not liable for trading decisions made on either display. Nothing here is a recommendation to buy or sell SBRV, USDC, or any RWA.