← Back

Privacy Policy

Last updated: October 19, 2026

SimLabDisplay is a web and iPhone application, operated by BML Innovations LLC, that helps instructors run simulation labs: assigning students to tasks, managing rotations, recording sign-offs, and summarizing a lab day. This policy explains what information SimLabDisplay collects, how it is used, and how it is protected. SimLabDisplay is used by educational institutions; the institution remains the owner of its students' educational records, and SimLabDisplay processes that data on the institution's behalf.

Information we collect

SimLabDisplay collects only what it needs to run a lab:

  • Account details: name, email address, and role (student, faculty/TA, or professor), used to sign in. Demo accounts are different: they never hold an email address, and at a dental school they hold no name either, only a seat number. At an undergraduate school a demo account holds the student's name (see "Demo accounts" below).
  • Class and lab data: the classes you belong to, your seat assignment where the lab has seats, the group you work in where the lab works in groups, and the day plans and activities an instructor creates.
  • Activity records: which activities a student has completed, when, and who signed them off.
  • Check-in times: if a professor turns on check-in for a lab day, we record when you first open that lab day in the app or on the website, whether that was on time or late, and any change a member of staff makes to it. Staff can also mark a student as away for a lab day.
  • Help and task requests: messages a student sends asking for help, and their status and timing. Requests from demo accounts carry no written message, only the student's identifier, the task, and the timing.
  • A notification token: if you turn on push notifications in the app, a device token that lets SimLabDisplay send them (for example, "you've been moved to a new task"). It identifies the device, not your location or anything on it, and it is deleted when you sign out or turn notifications off.
  • Photos of lab work: if a student chooses to upload them, photographs of their practice work (for example, a prepared tooth), stored privately and visible only to the student and, for class submissions, their instructors and their school's administrator (such as a dean). Photographs uploaded from a demo account are held against whatever that account is identified by: a seat number at a dental school, a name at an undergraduate one.

SimLabDisplay does not collect Social Security numbers, grades of record, financial information, or health information, and it does not use tracking or advertising cookies.

Demo accounts

An institution may trial SimLabDisplay using demo accounts. A demo account never holds an email address and never has a password to remember. A student signs in with a four-digit PIN and one other thing, and what that other thing is depends on the kind of school.

  • Dental schools: a seat number. A dental simulation lab is a room of numbered chairs, so a demo student signs up with only a seat number and a PIN. The account holds no name and no email address, and their work is recorded against the seat. The instructor knows who sits at each seat; SimLabDisplay does not, and cannot connect the account to a person on its own.
  • Undergraduate schools: a name. An undergraduate laboratory has no numbered chair to identify a student by, so a demo student there signs up with their name and a PIN. The account still holds no email address. A name is identifying information, and an institution choosing this kind of account should understand that SimLabDisplay holds it: what is kept is a name, a PIN, which lab tasks were completed, and any photographs of lab work the student uploads (see below), which are held against that name.

Which kind an account is follows from the school it is created under, not from anything the student chooses.

  • Photographs of lab work. Demo students can upload photographs of their work, up to a small storage allowance. At a dental school the photograph is the work being assessed (a prepared tooth an instructor reviews), and it is stored against the seat number, never linked to a name or an email address. At an undergraduate school it is stored against the student's name, because that is what the account holds. Students should photograph their work only, and not faces, badges, or anything else that would identify a person. A student can delete a photograph they took until an instructor has viewed it; after that it is part of the class record. An instructor can remove a photograph a student took, for example to ask for a retake, and a photograph an instructor took can be removed only by that instructor. Help requests from demo accounts still carry no written message.
  • Demo accounts are not deleted on a timer. A student can delete their own demo account at any time, and a school administrator can close one.
  • To prevent abuse of demo sign-up and sign-in, the network address a demo account is created from, and a scrambled form of the network address behind each wrong PIN, are kept briefly (no more than a few hours) and then deleted.

Demo records that are in use are otherwise retained like other class records, under the institution's direction.

How we use it

The information is used solely to operate the lab: to sign you in, to place and rotate students through tasks, to show instructors a live view of the lab, to record sign-offs, and to generate an end-of-day report for the instructor. SimLabDisplay does not sell your information or use it for advertising.

If your institution has enabled it, an instructor may email students who did not complete their lab work; those emails are sent only to students in that instructor's own class.

Where your data is stored

Data is stored in a managed PostgreSQL database (Supabase), hosted on Amazon Web Services in the United States (US East, Ohio region). It is encrypted in transit and at rest, and the provider maintains SOC 2 Type II certification. The application itself runs on Vercel (also SOC 2 Type II); student data is stored only in the database, not on the hosting layer.

Who can see your data

Access is scoped by role and enforced at the database level, so each person only sees what they are permitted to:

  • A student can see their own class, their seat or group, and their progress.
  • An instructor and their designated faculty/TAs can see the students in their own classes.
  • Your school's administrator, such as a dean, can view, but not change, the lab work in the classes at your school, and can download a copy of your school's records.
  • Apart from your school's administrator, no one can see data from a class they do not teach, assist with or take, and no one can see data belonging to another school.

Service providers

SimLabDisplay relies on a small number of providers to operate, who process data only to provide their service and not for their own purposes: Supabase (database and authentication), Vercel (application hosting), and Expo (delivery of push notifications to the iPhone app). If email reminders are enabled, Resend is used to deliver those messages. Like most web services, these providers keep short-lived technical logs of requests, such as the network address a request came from, for security and troubleshooting, and delete them on their own schedules, typically within days.

Data retention and deletion

Lab and activity records are kept for as long as your institution uses SimLabDisplay, so instructors can reference past labs. An instructor can delete a day plan, which permanently removes its associated placements, completions, and requests. On request from your institution, account and class data can be exported or deleted. Accounts are never deleted on a timer.

If you're a student, you can delete your own account at any time, from Profile on the website or in the app. If no member of staff has signed off, reviewed, or commented on your work, the account and everything in it is removed. If they have, the account is deleted and your name and email address are permanently removed, while the records of your work, including sign-offs and class photographs, are kept without your name attached as part of your institution's educational record. Photographs in your personal library are always removed. Those records belong to the institution rather than to us, and accreditation and student-records law require them to outlast the account.

If you have a staff account (a professor, faculty member or TA, or administrator), we keep a record of when you agreed to our Terms of Service and Privacy Policy — your name, email address, and the version you agreed to — even after the account is deleted. If a professor, faculty member or TA account is deleted, that person can no longer sign in and their email address is removed, but their name stays on the records of their work, such as sign-offs, notes, photo removals, and help given to students.

Student records (FERPA)

Some of the information SimLabDisplay handles (such as a student's participation and completion records) may constitute educational records under FERPA. SimLabDisplay acts as a service provider to the institution and handles this data under the institution's direction and any agreement in place. Students seeking to review, correct, or delete their records should contact their institution, which controls those records.

Security

Data is encrypted in transit and at rest, access is restricted by role and enforced at the database, and sign-in is protected by a password. No system is perfectly secure, but SimLabDisplay is built to limit access to the minimum each person needs.

Changes to this policy

This policy may be updated as SimLabDisplay changes. The date at the top reflects the most recent revision.

Contact

Questions about this policy or your data can be directed to support@simlabdisplay.com.