Security
This page describes, in full, how Ducatleigh Gardens protects your account and what you can do to protect it. Security here is a shared arrangement: the platform supplies the locks, the alerts and the logs, and you hold the keys. Read it once, then revisit the sections you need when you need them.
1. Two-factor and multi-factor authentication
Every Ducatleigh Gardens account supports two-factor authentication (2FA) and multi-factor authentication (MFA) using a time-based one-time password (TOTP) from an authenticator app such as Google Authenticator, Microsoft Authenticator or Authy. We recommend switching 2FA on the day you register, and your personal manager will walk you through the pairing on a call if you have never used one before.
2FA is strongly recommended rather than forcibly imposed at registration, because a forced second factor that a user has not understood becomes a lock-out risk. Recovery follows a verified identity process: you confirm your identity documents and answer security questions checked against your file, after which support removes the old device binding and lets you pair a new one. Support will never ask you to read a one-time code aloud or send it by email, and any such request is a fraud attempt.
2. Encryption of data at rest and in transit
All traffic between your browser and the platform is encrypted with TLS, and we enforce HTTPS across the whole site, including the registration form and every page of the client area. Data held at rest, including identity documents, contact details and account records, is encrypted on the storage layer of the systems responsible for it.
Encryption applies to the specific systems that hold each type of data: the document vault that stores verification files, the account database, and the message store that keeps support conversations. Encryption is not an invisibility cloak, so access to those systems is separately restricted by role, logged, and reviewed. Keys are managed separately from the data they protect, and rotation is scheduled rather than left to chance.
3. Fraud and phishing protection
The only domain through which Ducatleigh Gardens operates is ducatleigh-gardens.org, and our official email domain ends in @ducatleigh-gardens.org. We publish this in several places precisely so you can verify it. Messages from our personal managers always identify the sender by name and never ask for your password, your one-time codes, or remote access to your device.
When we send you an account-sensitive message, we include a protective reference code that also appears in your platform inbox, so you can check that an email genuinely came from us rather than from an impersonator. If a message asks you to move funds urgently, download an attachment you did not expect, or sign in through a link, stop and verify: open the site by typing the address yourself, or forward the message to [email protected] and ask. Reporting a suspicious message takes a minute and protects every other client too.
4. Login alerts and suspicious activity notifications
You receive an email alert whenever a new device signs in to your account for the first time, whenever a sign-in comes from a country you have not used before, and whenever we detect activity patterns that look unusual for you, such as a change of withdrawal details followed shortly by a payout request.
Alerts are informational, not merely decorative: each one tells you what happened, from roughly where, and what to do if it was not you. If you receive a sign-in alert you do not recognise, open the session manager (see point 5), end the session in question, change your password and enable 2FA if you have not already. Delayed reactions cost money in fraud cases, so we would rather send you ten alerts you recognise than stay quiet about one you do not.
5. Device and session management
The security section of your account lists every active session: browser sessions on laptops, app sessions on phones, and API connections. For each one you can see when it started and the rough location, and you can revoke any of them instantly without waiting for support.
Sessions end automatically after a period of inactivity, so a forgotten logged-in browser on a shared computer does not stay live indefinitely. Signing out on one device does not disturb the others, which is deliberate: revoking a suspicious phone should not lock you out of the laptop you are using to fix the situation. Password changes, however, invalidate all other sessions at once, which is exactly what you want after an incident.
6. Account recovery
If you lose access to your device, your authenticator or your password, recovery is a verified-identity process rather than a reset link. You contact support from the email registered on the account, confirm your identity against the documents in your file, and complete a short recorded verification call. Only then is the old second factor removed and a new one paired with you on the line.
There are limits by design: support cannot bypass verification for anyone, however convincing the story, and recovery cannot redirect payouts to new bank details at the same time as reclaiming the account. Those two requests are always handled as separate verified processes, with a cooling-off period between them. It is a minor inconvenience after a lost phone and a major obstacle to a thief.
7. API key permissions
Connections to exchanges run through API keys that you create on the exchange and enter into the platform. During set-up your personal manager shows you how to restrict each key: the platform needs read access for market and balance data and trade access for placing orders, and nothing else.
Withdrawal permission on an API key must stay switched off; automated trading does not require it and our tools never request it. IP restrictions, where the exchange offers them, are applied so the key only works from our infrastructure. Treat every API key like a house key: one per door, labelled, revocable, and replaced if you suspect it has been copied. The platform records when each key was added and by whom, and you can revoke keys from the same screen at any time.
8. Audit history
Your account keeps a chronological audit log of security-relevant events: sign-ins and sign-outs, new devices, password and 2FA changes, API key additions and removals, changes to strategies and their parameters, deposit and withdrawal requests, and changes to personal or payout details.
The log exists for the moments when memory is not enough: after an incident, during a complaint, or when you simply want to check what you changed last month and why your strategy behaved differently. Entries are attributed to the session that made them, so actions by you, by support acting on your request, or by the automation on your behalf are distinguishable. If you spot an entry you cannot explain, tell us immediately; unexplained entries are treated as potential compromises until shown otherwise.
9. Incident support
If you suspect your account has been accessed without permission, contact support at [email protected] or through the platform’s help section. The first step is containment: we can freeze trading and payouts on the account within minutes while we investigate, which prevents damage spreading while facts are established.
Incident handling follows a set order: secure the account, establish the timeline from the audit log, undo unauthorised changes, and only then unfreeze normal use. You will be kept informed at each stage by one named handler rather than a rotating cast, and serious incidents are escalated to the compliance team and, where required, reported to the relevant authorities. The same route applies if you clicked a phishing link but no damage is visible yet: early reporting is free, and it is never treated as an overreaction.
Have a security question we did not cover?
The support team answers security questions as a priority, Monday to Friday, 8:00–18:00, and Saturday 9:00–13:00 (GMT, excluding public holidays).
Security measures reduce but never eliminate risk. No platform, including ours, can rule out losses from market movements, third-party failures or sophisticated fraud. See the Risk disclosure for the full picture.