Security
How Ardent CrowdFund protects your account, your data, and your money, from authentication through to infrastructure.
Security
Security is not a feature of Ardent CrowdFund; it is a precondition of the platform. This page is a plain-English summary of the controls we run, the user-facing settings you should enable, and how we respond if something goes wrong. It is aimed at investors and issuers alike, and is deliberately non-exhaustive, the full control set is available on request to partners and regulators.
Account security
Password requirements, multi-factor authentication, session management, and how to spot a phishing attempt targeting your Ardent account.
Funds security
How escrow, segregation, daily reconciliation, and payout whitelisting protect the money flowing through the platform.
Data security
Encryption in transit and at rest, data residency, access controls, and the retention periods that apply to investor and issuer data.
Application security
Secure development practices, dependency management, third-party penetration testing, and our disclosure programme for researchers.
Infrastructure security
Hosting posture, network controls, patching cadence, and the compliance standards we map our infrastructure controls against.
Incident response
How we detect, triage, and communicate incidents, and what you can expect from Ardent if an incident affects your account.
Reporting a security issue
The fastest way to reach our security team, and how we handle responsible disclosure from external researchers.
Last updated on