Trust & compliance
FERPA Compliance
Compliant
Skillvora is built for the higher-education context and treats student-generated simulation data as a FERPA education record.
We use pseudonymous identifiers in transcripts, encrypt data at rest and in transit, support institution-defined retention windows, and offer a signed Data Protection Addendum for every institutional contract.
Faculty and admins control access through your existing LMS roles via LTI 1.3. Skillvora never sells or shares education records with third parties.
Faculty self-serve FERPA guide
If you're using Skillvora on an individual plan without an institutional agreement, you are responsible for FERPA compliance on the data you provide. Follow these rules:
DO: Author scenarios using fictional patients/clients/cases. Have students access simulations via a shareable link. Let students self-identify with a name or identifier of their choice.
DO NOT: Upload your class roster. Upload graded student work. Use real student names in scenario content. Share Evidence Packets containing student transcripts via unsecured email.
Evidence Packets generated on individual plans are tied to the identifier the student chose at session start, not to a verified institutional identity. If you need verified identity, roster sync, or gradebook integration, you need an institutional plan with LTI and a signed DPA.