Virtual funds are for practice. They are not cash and cannot be withdrawn.
Security
How Paave protects your account and data
The security measures we use today.
Account protection
- Sign-up confirms your email with a one-time verification code
- Optional two-step verification by authenticator app, email or passkey
- Passkeys, and face or fingerprint sign-in in the mobile app
- Changing a sign-in factor needs re-verification and signs out your other sessions
- Two-step verification is required to link a broker account
Web and app
- HTTPS only
- A strict content security policy
- Session cookies that scripts cannot read
- Bot protection on sign-up and sign-in
- Rate limits
Infrastructure
- All traffic passes through Cloudflare’s firewall, and our servers accept only that traffic
- No direct server logins: production changes need multi-factor authentication
- Secrets sit in a managed, encrypted secret store, with separate keys for separate purposes
- Data is encrypted at rest
- Our core services and databases are hosted in Singapore
- Daily backups that our servers cannot alter or delete, with tested restores
Privacy
- We limit and pseudonymize personal data in logs and crash reports
How we build
- Every code change is reviewed independently before release
- Dependencies are checked for known vulnerabilities
- Release images are built in a controlled pipeline, and the same build is promoted from test to production
Report a security issue
Found a weakness? Tell us and we will look at it.
Last updated: 8 November 2026