Data handling
The SDK runs entirely in the end user's browser. It transmits nothing to TradeScript at runtime, and it contains no analytics, telemetry, or tracking. Use this page to complete a data protection assessment from documented behaviour rather than from inspection.
Roles
You are the controller for all personal data in your application. TradeScript supplies software that runs on your users' devices under your control.
The SDK does not send end-user data to TradeScript. Where a future arrangement requires TradeScript to process personal data on your behalf, that is governed by a separate written agreement entered before the processing begins.
What leaves the browser
The SDK makes network requests only to endpoints your integration configures.
| Destination | When | Configured by |
|---|---|---|
| Market data provider | History, realtime, search, quotes | Your MarketDataFeed |
| Broker | Orders, positions, executions, balances | Your TradingBrokerAdapter |
| Chart storage backend | Saving and loading layouts, drawings, templates | Your ChartStorageAdapter |
| Image storage | Chart image export and upload | Your image storage adapter |
| Snapshot endpoint | Snapshot upload, when enabled | Your snapshot URL |
There is no TradeScript endpoint in that list. Deployment leases are verified offline in the browser against public keys embedded in your build, so authorisation contacts nothing at runtime. See Production authorization.
What the SDK stores in the browser
Storage is local to the device and holds user preferences and workspace state. These are the keys the SDK itself writes, enumerated from source:
| Key | Contents |
|---|---|
tradescript.interval-favorites | Intervals the user pinned |
tradescript.chart-type-favorites | Chart types the user pinned |
tradescript.drawing-tool-favorites | Drawing tools the user pinned |
tradescript.indicator-favorites | Indicators the user pinned |
tradescript.favorites-toolbar-position | Position of the favourites toolbar |
tradescript.chart.recent-colors.v1 | Recently used colours in the colour picker |
tradescript.pointerMode | Selected pointer mode |
tradescript.perf.console | Whether the performance console is open |
tradescript:hotkeys:* | Keyboard binding overrides, one key per hotkey scope |
None of these requires personal data to function.
Three further areas write keys assembled at runtime, so the suffix depends on your deployment rather than the SDK:
| Area | Key shape | Written when |
|---|---|---|
| Chart storage | Prefixed per layout, drawing, and template record | Local storage is your configured ChartStorageAdapter |
| Watchlist sync | Prefixed per cross-tab channel | Watchlist cross-tab synchronisation is enabled |
| Account panel | Prefixed per account panel view | The broker account panel is mounted |
Personal data appears only where your own application supplies it — a symbol list a user created, a note typed onto a chart, an account identifier in a trading panel. That content is yours, held under your lawful basis.
This table is generated from source and verified in the build, so it cannot drift
from what the SDK does. The machine-readable form is
docs-site/docs-data/storage-inventory.json.
Removing stored data
Storage lives in the browser under your application's origin. Clearing site data for that origin removes everything the SDK has stored.
Where your integration supplies a ChartStorageAdapter backed by your own
service, deletion and retention for that data are governed by your service, not
by the SDK.
Cookies
The SDK sets no cookies.
Embedded content from a third-party provider may set its own cookies inside its frame. Restrict or disable embedded content if that conflicts with your consent model — see Security.
Data location
The SDK adds no data location of its own. Data resides wherever your market data, broker, and storage services hold it, and in the end user's browser. Determine residency from those services.
Related pages
Read Security for content isolation and Content Security Policy, and Supply chain to verify the artifact you deployed.