Trust
Security
What we do to keep accounts and student data safe — and how to report a vulnerability.
Infrastructure
- Data stored in the European Union (Ireland); application server in Dublin.
- HTTPS everywhere with HSTS; database and backups encrypted at rest.
- Fonts and the 3D engine are self-hosted: no third-party requests when you use the labs.
- Payments handled entirely by Stripe (PCI DSS level 1); card data never reaches our servers.
Accounts
- No passwords: sign-in by single-use 6-digit code or link, valid 15 minutes, with rate limits per address and per network.
- Sign-in links require a click on a confirmation page, so email security scanners cannot consume them.
- Session cookie HttpOnly, Secure and SameSite; cross-site requests are rejected.
Application
- Strict Content Security Policy, frame and permissions policies.
- Teachers see only their own classes; students see only their own account.
- Webhooks from Stripe and Resend are verified by signature.
- Every change is tested automatically before deployment; the pipeline blocks any secret key in the source code.
Responsible disclosure
Found a vulnerability? Please write to hello@visotrain.com with the details, give us reasonable time to fix it before disclosure, and do not access other people’s data or disrupt the service. We reply within five working days and credit reporters who wish it. Machine-readable contact: security.txt.
Build your first circuit in two minutes — free, in the browser.Open the 3D workbenchPlans and pricing