Trust and security

Security controls designed around trading operations

Copy trading connects accounts, servers and permissions. We separate access control, funding flows and trading authorisation, and keep a traceable record of sensitive actions so teams stay in control as they scale.

Encryption in transit and at rest, with managed credentials
Permissions isolated by brand, role and account
Funding flows separated from trading authorisation
Auditable actions and a defined incident response

Capability matrix

Controls and scope

What each control protects and where it applies.

#	Control area	What it means	Scope
01	How is data encrypted and protected?	Data is encrypted in transit and at rest, with keys, tokens and account credentials managed separately. Day-to-day operations follow least privilege so individuals do not handle production data directly.	TLS encryption between browsers and the management console Sensitive data stored with encryption API tokens and login credentials held separately and rotated Encrypted backups with restricted restore permissions
02	How are permissions isolated?	Permissions are scoped by brand, role and account. Different brands, trading servers and admin seats only see their own scope, and high-risk actions require additional authorisation.	Accounts, orders and reports isolated by brand and tenant Admin seats assigned view, operate or approve rights by role Server connections and copy accounts bound to an authorised scope High-risk actions support confirmation and approval records
03	How are funding and trading authorisation separated?	FXCopyNex is a software provider. We do not hold client funds or place trades on a client's behalf. A licence controls software features and account scope; money movement stays with the broker or payment provider.	No custody of client funds and no deposit or withdrawal settlement Licence expiry affects software access, not account balances Payments handled by licensed payment providers or the broker Trade execution remains with the broker's servers and liquidity providers
04	How are actions audited and incidents handled?	Key administrative, licensing and risk-control actions record who acted, when and with what result. If something looks wrong, logs help scope the issue before isolation, remediation and review.	Login, licence changes and risk-rule edits are recorded Logs retained and access-restricted for compliance and operations Unusual logins and actions can raise alerts Incidents follow isolation, remediation, notification and review

How is data encrypted and protected?

Data is encrypted in transit and at rest, with keys, tokens and account credentials managed separately. Day-to-day operations follow least privilege so individuals do not handle production data directly.

How are permissions isolated?

Permissions are scoped by brand, role and account. Different brands, trading servers and admin seats only see their own scope, and high-risk actions require additional authorisation.

How are funding and trading authorisation separated?

FXCopyNex is a software provider. We do not hold client funds or place trades on a client's behalf. A licence controls software features and account scope; money movement stays with the broker or payment provider.

How are actions audited and incidents handled?

Key administrative, licensing and risk-control actions record who acted, when and with what result. If something looks wrong, logs help scope the issue before isolation, remediation and review.

Need a detailed control statement or a security review for private deployment? Ask our team for written documentation.

Control area

What it means

Scope