Security of your account
Security at Stakemonry is not a settings page you visit once; it is a set of measures that are switched on from the moment your account is created. This page explains each of them in plain English: what is protected, how, and what you should do if something looks wrong. It complements the technical detail on the AML / KYC page, which covers identity verification specifically.
Encrypted end to end
Data in transit and at rest is protected with modern ciphers.
2FA available
An extra verification layer for every sign-in.
1. Two-factor and multi-factor authentication
Two-factor authentication (2FA) adds a second proof of identity beyond your password, so someone who steals or guesses your password still cannot sign in. Stakemonry supports authenticator apps (TOTP) as the primary method, and we strongly recommend enabling it the first time you sign in rather than postponing it. Multi-factor options extend the same idea with additional factors where available.
Using 2FA is not compulsory for every account action, but it is required before sensitive operations such as changing withdrawal details. If you lose access to your 2FA device, recovery is possible: confirm your identity through verified channels with our support team, after which 2FA is reset under controlled conditions and you can enrol a new device. The recovery flow deliberately takes longer than ordinary sign-in; that friction is there to protect you from an attacker pretending to be you.
2. Encryption
Encryption applies in two places. In transit, all traffic between your browser and our platform travels over TLS, so credentials, personal details and account activity cannot be read by anyone intercepting the connection. At rest, personal records and account data are stored in encrypted form within systems whose access is restricted and logged.
The scope covers the account database, document storage used for identity verification, and the logs that record platform activity. Responsibility for these systems sits with our infrastructure and security teams, whose administrative access is itself subject to the same authentication standards, including 2FA for staff. Encryption is not a one-off setting: cipher suites and key management follow current industry guidance and are reviewed on a regular schedule.
3. Fraud and phishing protection
Phishing, where a message imitates a brand to trick you into revealing credentials, is the most common attack against financial platforms. Our protections start with domains: our only website is https://stakemonry-ai.co.uk, and links in our emails always lead to that domain. Any message referencing a different domain, a look-alike spelling or an urgent "verify now" demand should be treated as fake.
Verified messages from us carry consistent formatting and, where applicable, a protective code you can recognise; we never ask for your password, your full card number or a one-time code over the phone or by email. If a message looks even slightly wrong, do not click anything in it: type our address into the browser yourself, sign in, and check the notifications inside the platform. The fraud warning page lists the clone patterns we are aware of.
4. Login notifications
You receive an email notification whenever a new device signs in to your account for the first time. The message tells you the device type, the approximate location derived from the network, and the time, so an unfamiliar sign-in is obvious within minutes rather than weeks.
Suspicious activity, such as repeated failed password attempts or a sign-in pattern that does not match your history, additionally raises an internal alert that our team reviews. Where the signal is strong enough, precautionary restrictions are applied to the account until the legitimate owner confirms the activity. If you ever receive a login notification you do not recognise, treat it as an incident: change your password immediately and contact support.
5. Device and session management
The dashboard lists your active sessions, with device type, location and sign-in time, so you can audit who is signed in as you at any moment. A single control revokes access from a specific device or from all devices at once, which is the right response to a lost phone or a shared computer you no longer control.
Sessions expire automatically after a period of inactivity, and signing in on a new device can invalidate older sessions where the pattern looks risky. Idle sessions are not kept alive indefinitely: the default is a working-session length that balances convenience against exposure, and you can always end a session manually from the device list.
6. Account recovery
Recovering an account starts with verifying your identity, never with resetting first and asking later. You will be asked for information tied to your registration and, depending on the case, to repeat part of the identity verification performed at onboarding. This is deliberately strict: the inconvenience is what prevents an attacker from socially engineering their way into your account.
Recovery requests are handled only through official channels, the email address published on this site and the in-platform support route. There are limitations worth knowing: we cannot restore an account without verification, we cannot bypass 2FA reset rules for speed, and we will never ask you to pay for a recovery. If someone claiming to be from Stakemonry demands payment or remote access to your device to "fix" your account, it is not us.
7. API key rights
Connections to external services use API keys with scoped permissions, and the scopes matter more than the keys themselves. The available scopes separate three levels: read access to see account data, trading access to execute strategy actions, and withdrawal access to move funds out. Read keys cannot trade; trading keys cannot withdraw.
We recommend granting the narrowest scope that a connection needs, and reviewing your active keys periodically, revoking any you no longer use. When a key is compromised, the response is the same as for a password: revoke it, then create a fresh one after the cause is understood. The platform records key creation, changes and revocation in the audit history described below, so nothing about your API surface changes silently.
8. Audit history
The audit history records the events that matter for accountability: logins, connections from services, changes to strategies and updates to settings. Entries carry timestamps and, where relevant, the device or key responsible, giving you a single chronological record of how your account has been used.
Two practical uses are worth highlighting. First, after any security concern, the audit history shows exactly what did or did not happen, which removes guesswork from the conversation with support. Second, it deters misuse: anyone with partial access to your account knows their actions are recorded and reviewable. The history is retained for a defined period consistent with our storage obligations under the Privacy Policy.
9. Incident support
If you suspect a security incident, an unrecognised login, a suspicious message, a changed withdrawal address, the first step is to contact support through the channel described on the Contact page and, in parallel, to secure your account by changing your password and revoking sessions. Our team can place a precautionary block on the account while facts are established, which freezes withdrawals without closing your access permanently.
Incidents are escalated internally on receipt, and you can expect an acknowledgement quickly, with a named contact for the follow-up, during Monday to Friday, 9:00–17:30 (excluding public holidays). The communication sequence is: acknowledgement, precautionary measures taken, findings, and resolution with any corrective steps. We will tell you what happened in plain language, including when the finding is that nothing happened, and we will never use an incident as an occasion to ask for your credentials.