Security Statement
Effective date: 8 October 2026
We protect your data with the following measures. Everything listed here is in place today (checked October 2026).
How we protect your data
- Hosting: The Service runs on Oracle Cloud Infrastructure in the UK South (London) region, on a server used only for the Service. Oracle's data centres hold recognised security certifications such as ISO 27001.
- Encryption: Data is encrypted in transit (HTTPS/TLS), both between your device and our network provider and between our network provider and our server. Data is encrypted at rest on our hosting provider's storage, and backups are encrypted again with a key that is not kept on any server.
- Passwords: User passwords are stored using strong one-way hashing. We never see them. Accounts are locked automatically after repeated failed login attempts. Two-step verification is available to all staff accounts and required for trust administrators. Schools can also let users sign in with their school Google or Microsoft account, so the school's own security settings (such as its two-step verification) apply. New accounts are only created this way if the school has switched it on: students need a class code from their teacher that works only with the school's own email domains, and staff accounts are made only after a school administrator approves the request.
- Access: Only founders who need access have it. Server access uses security keys only (no passwords), our cloud and hosting accounts use multi-factor authentication, and keys and passwords are kept in a password manager.
- Backups: Data is backed up every night. Encrypted backups are kept in two separate locations in the UK (14 and 30 days), plus a weekly copy of the whole server (4 weeks). We test that backups can be restored at least once a month, and we are alerted automatically if a nightly backup does not run.
- Updates: Security updates for the server install automatically every day. We update the application's components promptly.
- Monitoring: All visits pass through Cloudflare, which filters out attacks. Our server only accepts website traffic from Cloudflare, and admin tools are not reachable from the internet. Repeated failed logins are blocked automatically, and security logs are kept for up to 90 days.
- Payments: Card payments are handled by Stripe. We never store full card numbers.
Reporting a security issue
If you find a security weakness, email hello@wio.org. Please give us time to fix it before telling anyone else. We will not take action against people who report issues in good faith.
About this statement
This statement describes our current practice and may change as we improve our security. It is for information only and does not create contractual promises. Our contractual security commitments are set out in our Terms of Service and Data Processing Agreement.
Terms of ServicePrivacy PolicyCookie PolicyAcceptable Use PolicyData Processing AgreementSub-processor List
