Security depends on layered controls, careful user behaviour and a clear response when something looks wrong.
AvenQuant supports a second authentication step where available. Enable it during setup and keep recovery information separate from your everyday device. A support review may be required if both the device and recovery method are unavailable.
No support agent should ask you to read a one-time code aloud. A second factor reduces unauthorized access but cannot protect a user who approves a fraudulent prompt.
Supported browser traffic uses encrypted transport, and controlled systems apply protections to stored personal information according to its sensitivity. Encryption applies to AvenQuant-managed transmission and storage; it cannot protect information copied into an unapproved message or third-party service.
Begin at https://avenquant.ca and verify messages from the published support address. Treat look-alike domains, remote-access requests and guaranteed-profit claims as warning signs.
Report a suspicious message without forwarding live credentials. We can compare sender details, restrict access and preserve evidence.
A new device or unusual access pattern may generate email or in-product notice. Review the time, approximate location and device, then change credentials and contact support if the activity is not yours.
Use the account view to review active sessions and revoke access you do not recognize. Sessions may expire automatically after inactivity or a security event; shared devices should never be marked as trusted.
Recovery requires enough evidence to distinguish the account holder from an impersonator. Support may verify identity and recent account context before restoring access, and sensitive actions may remain restricted during the review.
Use the narrowest available permission. Read access allows observation, trade access may permit orders and withdrawal access should remain disabled unless a documented workflow genuinely needs it. Revoke an unused or exposed key immediately.
Account records may include logins, device changes, connections and strategy-setting updates. Review history after an alert and retain relevant timestamps when reporting an incident.
Email [email protected] with “Security incident” in the subject, identify the account and describe the event without including a password. We may restrict access, preserve records, investigate affected systems and provide staged updates.