Skip to main content
These are plain answers to the questions every security review asks: what we store, who can see it, and what we never do with it. Share this page with whoever reviews your integration.

​
Market data belongs to the trader

When a trader connects their own account at a provider, their market data flows under their own entitlement. That’s a rule of the platform, not a detail of one provider:
  • A trader’s entitled data serves that trader alone.
  • Caches of it are scoped to the trader’s session.
  • We never pass one trader’s feed on to other users.
  • No firm route sends a trader’s entitled data to the firm or to anyone else.
Shared data reaches traders only through a feed that the provider or the firm licenses for sharing. If we don’t hold the license, the route doesn’t exist. We never serve delayed data as a quiet fallback.

​
What trdrs stores

​
What a firm can see

A firm sees the accounts it issued or pre-registered: their registration status, usage and audit events. It can’t see a trader’s credential, a trader’s entitled market data, or anything that belongs to another firm. The Trading API, Partner and Venue key scopes are separate at the routing layer, so this is enforced before any handler runs.

​
What we ask of you

The integration self-check asks for the same care in return: keys stay on your server, and trader credentials never appear in your logs or ours. Nothing is sent to us; the self-check runs in the sandbox and you read its result there. If you find personal data in a response that this page doesn’t explain, tell your trdrs contact and we’ll treat it as a defect.