Security & data architecture
Designed around the sensitivity
of trade data.
TradeConduct is being designed to support secure data integrations and customer-resident analysis for firms that require sensitive trade data to remain within their own environment. Deployment model is a design constraint here, not an afterthought.
Principles we are building to
Read-only access
Surveillance should observe trade activity, never alter it. Nothing TradeConduct is being designed to do requires write access to an order, an execution or an allocation.
Customer-controlled data scope
The firm decides which accounts, which periods and which fields are in scope — and can narrow that at any time without losing the analysis already performed.
Role-based permissions
Compliance, operations and management should not see the same surface. An investigation in progress is sensitive inside the firm, not only outside it.
Auditability
Who looked at what, when, and what they concluded — recorded as a matter of course, because a review nobody can reconstruct is not a defensible review.
Private deployment options
Analysis that can run inside the firm’s own environment where that is required, rather than assuming every firm will send trade data to a vendor.
Data minimization
Collect the fields the analysis needs and not the ones it does not. Trade data the product never reads is risk carried for no return.
Where we actually are today.
TradeConduct is pre-launch software in active development. The principles above describe the architecture we are building toward, not a system you can audit today.
We hold no security certifications. We are not SOC 2 attested. We make no audit or penetration-test claims. No third-party integrations are available, and no firm's trade data has ever been processed by this product.
If your diligence process needs specifics, ask us and we will tell you plainly what does and does not exist — including where the answer is “not yet”. Write to [email protected].