Security at Calvero Spark
Your account sits behind several layers of protection, and every one of them is designed so that you keep control. This page explains each layer in plain English: what it does, whether it's compulsory, and what to do if something ever looks wrong.
2FA / MFA
Optional today, recommended always — one tap keeps your login yours.
Encryption
Data protected in transit and at rest across the systems that hold it.
Login alerts
New device or odd activity, and you're the first to know by email.
1. Two-factor and multi-factor authentication
Calvero Spark supports time-based one-time codes (TOTP) from any authenticator app, which means a password alone is never enough to open your account. Two-factor authentication is currently optional but strongly recommended for every user, and we may require it before sensitive actions such as changing withdrawal details. If you lose access to your authenticator device, recovery is handled through the support team with identity verification — never through an emailed code alone. Set 2FA up when you first log in; it takes about a minute and removes most of the risk from a stolen password.
The order of operations matters: enrol the authenticator while you still have your password and device to hand, save the backup code somewhere offline (a password manager or a printed card), and only then treat the account as protected. If you ever receive a 2FA prompt you didn't trigger, that is your cue to change the password immediately — someone else has it.
2. Encryption of data in transit and at rest
All traffic between your browser and the platform travels over TLS, so login details, identity documents and payment instructions cannot be read in transit. At rest, personal data held in our systems — including KYC documentation — is stored encrypted, with access limited to the systems and teams that genuinely need it. Encryption is applied at the storage layer as well as the application layer for the most sensitive fields. The scope covers account data, verification documents, support conversations and transaction records.
Responsible systems are explicit: the login and API layer terminates TLS; the document store holding KYC material is encrypted with keys separate from the application database; and backups inherit the same protection as live data. Access to decryption keys is itself logged, so misuse leaves a trail.
3. Fraud and phishing protection
We communicate from our official domain only, and we will never ask you for your password, your 2FA codes, or a payment to a "safe account" over the phone or by email. Where a message involves money movement, it carries a recognisable structure and no urgency pressure. If a message claims to be from Calvero Spark but looks off, don't click anything in it — write to [email protected] and we'll confirm what's genuine. Our Fraud warning page lists the current patterns we're aware of, including clone firms misusing our name.
4. Login notifications
Whenever your account is accessed from a device we haven't seen before, you receive an email notification. The same applies to password changes, new 2FA enrolment and any modification of withdrawal details. If a notification arrives for something you didn't do, use the link in it to lock the account immediately and contact support. These alerts are always on; you cannot switch them off, because they exist to protect you rather than to market to you.
5. Managing devices and sessions
The dashboard shows every active session on your account — browser sessions and mobile app sessions, with device type, approximate location and last activity. You can end any session instantly from that list, which signs the device out and requires a fresh login. Sessions expire automatically after a period of inactivity, so a forgotten open tab on a shared computer doesn't stay live indefinitely. Review the session list occasionally, particularly after travelling or changing devices.
Two situations deserve an immediate "end all sessions": after using a public or shared computer, however briefly, and after a device is lost or stolen. Ending sessions costs you nothing but a new login; not ending them can cost considerably more.
6. Account recovery
If you lose your password or your 2FA device, recovery goes through the support team, not through an automated reset link that a fraudster could also trigger. We verify your identity using the information already on your account — including documentation held from KYC — before any credential is reissued. That makes recovery slower than a one-click reset by design. Expect to answer questions and possibly provide a fresh document; the delay is the safeguard working.
7. API key rights
Where the platform connects to exchanges on your behalf, API keys are provisioned with the narrowest rights the function requires: reading data, trading, or withdrawing, as separate scopes. Withdrawal permission is never enabled on a key that only needs to read prices or place trades. Keys can be revoked at any time from your dashboard, and revocation takes effect immediately. This separation means a compromised trading key cannot empty your wallet.
8. Audit history
Every login, every connection, every change to a strategy or a setting on your account is written to an audit log you can see. The history includes what changed, when, and from which device — so you can reconstruct exactly how your account reached its current state. If anything in the log surprises you, that's the moment to end foreign sessions and contact support. We retain audit records for the periods required by UK expectations for financial records.
A useful habit: open the audit history after any support interaction and confirm that what was done matches what was agreed. The log is the same for you and for us — neither side can quietly rewrite it.
9. Support during a security incident
If you suspect your account has been accessed without permission, write to [email protected] immediately — the Client Support & Compliance team monitors that mailbox during Monday to Friday, 9:00–17:30 GMT (excluding public holidays). Your account can be locked pending review, withdrawals can be frozen, and an escalation path takes over if credentials or personal data may have been exposed. You'll get an acknowledgement quickly, then updates at agreed intervals until the incident is closed. We treat security reports from users as priority traffic, not as complaints.
Putting the nine layers together
Individually, each layer blocks a particular class of problem: 2FA stops stolen passwords, encryption protects data in place, alerts warn of misuse, session control limits exposure, recovery verifies humans, API scopes contain keys, the audit log records everything, and the incident process catches what slips through. Together they follow one principle — you should never have to take our word for anything. The state of your account is visible to you, the history is visible to you, and the escalation routes are published on this site rather than revealed on request. Use them: the security features only work when you look at them.
Deposit protection: Money held with a UK-authorised firm may be covered by the Financial Services Compensation Scheme (FSCS), subject to its rules and eligibility criteria. Eligible investments held with a covered firm may similarly be protected within FSCS limits. Cryptoassets and other digital assets are generally not covered by the FSCS, and any protection depends on the scheme’s own rules — it is never a guarantee of the amount invested.