Security controls and safe account use
AvenQuant combines technical safeguards with user-controlled access, monitoring and incident support. No system is immune from attack, so security depends on both platform controls and careful user behaviour.
1. Multi-factor authentication
Multi-factor authentication adds a separate proof after the password, such as an authenticator-app code or approved device prompt. It is strongly recommended and may be required for sensitive changes, new payment destinations or account recovery.
Store recovery codes offline and never send a code to a caller. If the second factor is lost, support verifies identity and recent account details before resetting it; a security delay may apply.
2. Encryption and data handling
Supported browser connections use current transport encryption to reduce interception in transit. Sensitive records are protected at rest according to their category, and access is restricted to systems and staff with a documented operational need.
Encryption cannot protect information disclosed to an impersonator or entered on a cloned website. Confirm the domain and the connection indicator before signing in.
3. Fraud and phishing protection
Official service communications refer users to avenquant.co.uk and do not request passwords, one-time codes or remote control of a device. Automated screening may flag unusual contact changes, transfer patterns or repeated failed authentication.
Treat unsolicited urgency as suspicious. Open the site independently, compare the sender domain and report lookalike messages to support without forwarding active attachments.
4. Login and activity alerts
Email or in-product notices can identify a sign-in from a new device, a password change or other significant event. Review the time, approximate location and device, then revoke access immediately if the event is not yours.
Delivery can be delayed by mail providers, so alerts supplement rather than replace session review. Keep contact details current and protect the email account used for recovery.
5. Devices and sessions
The account area shows active sessions where supported and allows access to be revoked. Sign out on shared devices, avoid saving credentials in an untrusted browser and review sessions after travel or a lost device.
Inactive sessions may expire automatically. A revoked session can still leave local files or screenshots behind, so remove downloaded reports before returning a borrowed device.
6. Account recovery
Recovery requires evidence sufficient to distinguish the account holder from an attacker. Support may verify identity, established contact channels, recent activity and device history; it will not accept a password as proof over email.
During a disputed recovery, sensitive functions may be restricted. This can delay access but reduces the chance of funds or settings being changed by the wrong person.
7. Connection-key permissions
Where a third-party connection uses a key, enable only the permissions needed for the stated function. A monitoring connection normally needs read access; trading access should be enabled only after review, and withdrawal permission should remain disabled.
Use a unique key, restrict it by IP where the provider supports that control, and rotate it after suspected exposure. Deleting a connection in one interface may not revoke it at the provider, so check both sides.
8. Audit history
Audit records can include sign-ins, connection events, alert changes and strategy-setting updates. Review them after an unexpected result or notification to establish whether the system followed an authorised configuration.
Keep relevant statements and correspondence outside the account as well. A complete timeline helps support, payment providers and authorities investigate an incident.
9. Incident support
If you suspect compromise, change the password from a trusted device, revoke sessions and keys, secure the connected email account and contact [email protected]. State what happened, when you noticed it and which actions you have already taken.
Support can restrict the account, preserve records and escalate the case. Do not include a password, authentication code or full card number. Urgent protective action may occur before the investigation is complete.