> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Data policy

> Plain answers to the questions every integrator's security review asks: what we store, who can see it, and what we will never do with it.

Plain answers to the questions every integrator's security review asks: what we store, who can
see it, and what we will never do with it.

## Market data belongs to the trader

When a trader connects their own venue account, their market data flows under their own
entitlement. This is platform law at trdrs, not a per-venue detail:

* a trader's entitled data serves that trader alone;
* caches are scoped to the trader's session;
* we never redistribute one trader's feed to other users;
* no partner surface fans a trader's entitled data out to the firm or to anyone else.

Shared data reaches traders only through a feed the venue or partner actually licenses for
sharing. If we do not hold the license, the surface does not exist. We do not serve delayed data
as a quiet fallback anywhere.

## What the engine stores

* **Order intent and outcome.** The durable order ledger keeps what your integration sent and
  what the venue answered. The venue's raw payload is stripped from every served row, so what you
  read back is the documented shape and nothing more.
* **Executions and positions.** The account surface serves what the connected venue reports.
  Money fields the venue has not reported are `null`, never an invented `0`.
* **Connect registrations.** A registration holds the account number, venue login label, and the
  trader's email. It never holds a password. The trader enters their own credential themselves, so there
  is no moment where the firm's data path and the trader's secret touch.
* **Key hashes.** We store a SHA-256 hash of each issued key, not the key. A read of our
  database cannot produce a working credential.

## What partners can see

A firm sees the accounts it issued: registration status, usage, and audit events. A firm does not
see the trader's credential, the trader's entitled market data, or anything belonging to another
firm. Tenant and partner scopes are disjoint at the routing layer, so this is enforced before any
handler runs.

## Your side of the contract

The conformance checklist asks for the same discipline back: keys stay server-side, evidence
bundles are redacted, and trader credentials never appear in your logs or ours. If you find any
personal data in a served response that this page does not explain, report it to your trdrs
contact and we will treat it as a defect.