Reference
Basis data, privacy, security and troubleshooting
Understand Basis market-data coverage, browser storage, account sync, API-key security and fixes for common chart, derivatives and agent issues.
10 min readUpdated 2026-08-224 sections
Missing, stale and zero are different states
Basis avoids converting a failed request into a plausible zero. Panels distinguish loading, partial coverage, stale data and unavailable sources. When one venue fails, available venue data can still render with a visible caveat.
- Loading: the request has not resolved yet.
- Partial: some sources returned and others failed.
- Stale: a previous value exists but is older than expected.
- Unavailable: no trustworthy value can be shown.
- Zero: the provider explicitly reported a valid zero.
Local browser data and synchronized account data
| Data | Default location | Synced? |
|---|---|---|
| Public chart state | Browser | Only saved workspace state when signed in |
| Drawings and saved layouts | Browser / account storage | Yes when signed in |
| Journal and alerts | Browser / account storage | Yes when signed in |
| Model API keys | Session storage; optional local storage | Never |
| Transient chart screenshot | Memory for one model pass | Never in agent history |
| Sandbox program | Isolated worker context | No access to browser key storage |
Fix common terminal problems
| Problem | First checks |
|---|---|
| Chart is not updating | Confirm LIVE status, symbol support and venue; then reload once |
| Derivatives says unavailable | Confirm PERP market, inspect partial-source message and timestamp |
| Order flow is empty | Choose a supported liquid symbol and confirm exact trade coverage |
| Agent cannot read data | Select a tool-capable model and verify the provider key |
| Calendar takes too long | Use cached/rule-derived events and retry the external source |
| Saved state conflicts | Check the cross-device update notice and reload before editing |
Report a reproducible issue
- Exact URL and whether the terminal was spot or perpetual.
- Symbol, exchange, timeframe and chart type.
- Visible error text without any API key.
- Approximate time and timezone.
- Steps from a fresh reload.
- Screenshot with account information excluded.
Important
Never include model API keys, provider authorization headers, passwords or private account data in a bug report.