For your IT team
Security and privacy
How SimLabDisplay protects your school's data. This is the summary. In a walkthrough we'll go as deep as your team wants, down to the individual access rules.
Start with a pilot, not a roster
Demo accounts hold no email address and no password, only a PIN plus a seat number at a dental school or a name at an undergraduate one. Nothing is imported and no system is connected.
Access rules live in the database
Who sees what is enforced inside the database itself, not in app code. A student can only ever read their own records. A bug in the interface can't leak the wrong row.
Revoked means now
Close an account and the database refuses it on the very next request, even mid-session, even on a phone that's already signed in.
Minimal data, fully exportable
Names, school emails, class records, photos of practice work: that's the inventory. All of it exports to open formats at any time. There is no lock-in to us.
Single sign-on ready
SAML 2.0 is built in. Your identity provider vouches for students, they inherit your MFA, and deprovisioning follows your directory. Enabling it is configuration, not a project.
Records outlive accounts
Students can delete their accounts any time. Their identity goes, but faculty-signed coursework stays, nameless, as the institution's record. The line FERPA draws, drawn in the code.
Nothing watches your students
No ads, no analytics, no AI, no location. The app never even requests the permission. Encrypted in transit and at rest on SOC 2 Type II certified infrastructure.
If something ever goes wrong
If we discover a breach, the credentials that matter are revoked in minutes. That ends the exposure. Your designated contact hears from us within 24 hours with what we know, and within 72 hours you have it in writing: scope, cause, and fix. If your policy requires a different window, tell us the number and we'll hold to it in writing.
Questions about security or data handling? Email support@simlabdisplay.com.