Security & Privacy

How we protect your data, your traders, and your operations

QuantSentry is built to detect coordinated abuse while minimising data exposure. Privacy by design is not a checkbox — it's a foundational architectural decision.

Privacy First by Design

QuantSentry is built to help proprietary trading firms detect coordinated abuse while minimising data exposure. The platform is designed around privacy by design and purpose limitation, so you can run effective risk operations without collecting more personal data than you need.

This document explains what data QuantSentry processes, how it is secured, how the optional Fraud Intelligence Network works, and what controls you retain at every stage.

What QuantSentry Processes

QuantSentry primarily processes trade execution and platform activity data to detect behavioural similarity and coordinated patterns. The system is designed to work with the minimum data necessary for effective detection.

Typical Inputs

📈

Trade execution data

Instrument, time, size, entry and exit prices, profit and loss, hold duration, lot size, and ticket identifiers.

📋

Account and program context

Challenge stage, verification status, funded phase, account group, initial balance, and program type.

⚙️

Platform context

Server identifier, account group, execution metadata, and platform type (MT5, cTrader, Match Trader) where available.

👤

Optional identity fields

Name, email address, and KYC identifiers — only if you choose to provide them. Used for investigation workflow, not for detection.

You can run QuantSentry without identity fields

Many firms start with obfuscated or non-personal datasets during evaluation. Detection is driven by behavioural signals, not personal identifiers. Identity fields are optional and only enhance the investigation workflow if you choose to include them.

Read-Only Access and Operational Safety

QuantSentry connects to supported trading platforms through read-only manager API access. This is a foundational architectural decision, not a configurable setting.

What QuantSentry does
  • Reads trade execution data
  • Reads account metadata and program context
  • Processes data within your defined scope
  • Generates alerts and evidence from observed patterns
What QuantSentry never does
  • Place, modify, or close trades
  • Change account settings or configurations
  • Modify platform data or records
  • Store credentials beyond initial integration

During trials and evaluation, you can restrict scope to specific servers, groups, or programs to minimise exposure and validate value safely before expanding access.

Internal-Only Mode and Data Minimisation

QuantSentry operates in internal-only mode by default. This means all detection and alerts are generated solely from your firm's data, within the scope you define. No data leaves your instance unless you explicitly opt into the Fraud Intelligence Network.

Data Minimisation Controls

Exclude personal identifiers

Run detection without names or email addresses. The system works on behavioural signals, not identity.

Obfuscate during evaluation

Provide hashed or anonymised personal fields during trial periods. Replace with real data only if and when you choose.

Limit ingestion scope

Restrict to specific servers, account groups, or programs. Expand incrementally as you gain confidence.

Stage-based sensitivity

Configure different alert thresholds for challenge, verification, and funded accounts. Apply the right level of scrutiny at each stage.

Fraud Intelligence Network

Optional and consent-based

The Fraud Intelligence Network is designed to improve detection of coordinated abuse across participating firms. Network mode is opt-in. If you opt out, you remain fully segregated and do not contribute signals or receive network alerts. This is your choice, not a default.

The Fraud Intelligence Network is designed to share signals, not identities. The distinction is fundamental to how the system works.

Shared in Network Mode
  • Anonymised fingerprints derived from identifiers
  • Behavioural similarity signals and match indicators
  • Risk scores and non-identifying metadata needed to support the signal
Never Shared
  • Raw names or email addresses
  • Full personal identity records
  • Which participating firm generated a match
  • Raw trade data or account details
  • Your firm's identity to other participants

When a network match occurs, you receive a signal indicating that a behavioural pattern has been observed elsewhere. You do not learn which firm, which trader, or any identifying details about the external match.

Security Controls and Auditability

QuantSentry is designed for defensible investigations and consistent enforcement. Every action, alert, and configuration change is recorded and auditable.

Full audit trails

Every alert, every evidence kit generated, every configuration change, and every user action is logged with timestamps and attribution.

Exportable evidence kits

Generate and export complete evidence packages for disputes, internal reviews, and regulatory inquiries. Includes network visualizations, trade-level detail, and timeline overlays.

Configurable thresholds and weights

Set your own score thresholds, factor weights, and minimum trigger criteria per alert type. Align detection sensitivity to your rulebook and terms of service.

Stage-based settings

Apply different detection sensitivity to challenge, verification, and funded accounts. Higher scrutiny where the financial exposure is greatest.

Encryption in transit and at rest

All data is encrypted using industry-standard protocols during transmission and while stored. Credentials are not retained beyond initial setup.

Role-based access

Control which team members can view alerts, generate evidence, modify settings, or access sensitive investigation data.

Regulatory Posture

Fraud prevention and security operations often rely on privacy frameworks that permit processing and limited sharing for the purpose of preventing fraud. QuantSentry is designed to support compliance with these frameworks.

EU GDPR

Fraud prevention can be supported under the legitimate interests basis. Data minimisation, purpose limitation, and consent-based sharing are built into the platform architecture.

US GLBA

Financial privacy frameworks such as the Gramm-Leach-Bliley Act include allowances related to fraud prevention. The platform's read-only access model and data minimisation controls support compliance.

Other Jurisdictions

The platform's configurable scope, data minimisation options, and consent-based network mode are designed to accommodate a range of regulatory environments.

Important

QuantSentry does not provide legal advice. Your legal counsel should confirm the appropriate lawful basis, disclosures, and contract terms for your jurisdiction and operating model.

Your Controls and Governance

You control what data is provided, what scope is ingested, and whether network mode is enabled. QuantSentry is designed to support your internal policies — not to replace them.

ControlWhat You Decide
Data Scope

You decide which servers, groups, and programs are ingested. You can expand or restrict scope at any time.

Identity Fields

You choose whether to include names, emails, and KYC identifiers. Detection works without them.

Network Mode

Opt-in only. You can enable or disable participation in the Fraud Intelligence Network at any time.

Retention

You control retention policies. We support your internal data lifecycle and deletion requirements.

Access Controls

You assign roles and permissions for your team members within the platform.

Investigation Workflow

You define your enforcement process. QuantSentry surfaces evidence and scores — it does not make enforcement decisions.

Questions? We're here.

For security, privacy, or compliance questions — reach out directly. We respond to all enquiries within one business day.

Email

Privacy first by design. Detection without overreach.