Can I Trust Qlef With My Students?

Video of minors is sensitive. Schools know that. Parents know that. We know that. And different schools have very different rules about what they're comfortable with. One district may permit students to submit video directly through an educational platform, while another requires all student media to remain inside its existing Google or Microsoft environment. Some families may not want their child recording video at all.

Qlef is being designed for all of those scenarios. Our goal isn't to convince schools to loosen their privacy standards to use Qlef. It's to build Qlef so that a school's existing privacy requirements don't prevent its students from participating. That means giving organizations control over whether student media is recorded, where it lives, who can see it, and how long it exists.

Your Privacy Policy, Not Ours

• Privacy and submission policies can be established at the Organization level.
• Individual Ensembles can apply stricter policies when necessary.
• Assignment-level requirements operate within those boundaries.
• Individual student accommodations can provide additional flexibility.
• Organization → Ensemble → Assignment → Student inheritance.
• Hard restrictions established by the district or Ensemble cannot be bypassed at a lower level.
• Directors don't have the ability to override district-level privacy prohibitions.

Students Don't Have to Submit Video to Qlef

Introduce the Qlef privacy ladder:

• Qlef-hosted video.
• Externally hosted video.
• Qlef-hosted audio.
• Externally hosted audio.
• Staff/in-person verification.
• Parent attestation.
• Students can participate without Qlef ever storing their video.
• Students can participate without recording video at all.
• Parent attestation can verify assignment completion, while staff verification provides stronger evidence of performance quality.

Suggested visual: A privacy ladder showing the progression from Qlef-hosted video through completely media-free verification.

Keep Student Video Inside Your Existing School Environment

• Google Drive and Microsoft OneDrive as preferred external-storage options.
• Student media can remain within school-controlled accounts.
• Qlef manages the assignment, deadlines, feedback, verification and progress without becoming the permanent home of the video.
• Authorized staff can access externally hosted evidence through the Qlef assignment workflow.
• Future direct integrations can reduce the need for students to manage sharing links manually.
• Schools that prohibit third-party student-media storage can still use Qlef.

Suggested visual: Student → School Google/Microsoft Account → Qlef Assignment → Authorized Director.

When Qlef Does Host Student Media

• Student media is never publicly accessible.
• No public or "unlisted" sharing links.
• An authenticated Qlef account is required.
• Access is permission-based.
• Students can access their own submissions, not another student's.
• Staff access is limited to students and Ensembles they're authorized to work with.
• Parent access is limited to their own child and can be further restricted by school policy.
• Student data is encrypted in transit and at rest.
• Student data is stored using U.S.-based infrastructure.
• Normal downloading of student media is disabled.
• Exceptional media retrieval requires a formal Qlef/legal process.

Every View Leaves a Record

• Every access to student media is logged.
• Record who viewed the submission and when.
• Students and parents can inspect their media-access history.
• Authorized administrators have more detailed audit capabilities.
• Organizations can optionally notify students/parents when media is viewed.
• Dynamic viewer watermarking is always displayed on student media.
• Captured copies can therefore identify the authorized account through which the media was viewed.

Student Data Doesn't Live Forever

• Qlef-hosted student media automatically expires after 90 days.
• Organizations can request earlier deletion.
• Student/family deletion requests are routed to authorized school officials.
• Organizations must designate a Privacy/Data Contact.
• Qlef deletes school data when the customer relationship ends.
• Externally hosted media remains subject to the school's own Google/Microsoft/etc. retention policies.
• Explain separately what operational/aggregate records may need different retention rules.

We Collect What We Need—and Avoid What We Don't

• Data minimization as a product-design principle.
• No home addresses.
• Avoid collecting dates of birth unless legally necessary.
• School email used for student identity/access.
• Phone numbers collected only when SMS functionality requires them.
• A parent/guardian phone may be used instead of a student's phone and is explicitly identified as such.
• Don't collect information simply because it might become useful someday.

No Advertising. No Selling Student Data. No AI Processing Student Data.

State these plainly:

• Qlef does not sell student data.
• Qlef does not share student data with advertisers.
• Qlef does not serve behavioral advertising to students.
• Qlef does not use student data to train AI models.
• AI does not process student accounts.
• AI does not process student submissions.
• AI does not process student video or audio.
• Qlef does not claim ownership of student submissions or school content.

Schools Stay in Control

• Central Privacy & Data Controls for administrators.
• Organization-wide policies.
• Ensemble-level stricter policies.
• Student accommodations.
• Parent-access controls.
• Verification-method controls.
• Communication controls for appropriate director/admin roles.
• Google Workspace and Microsoft 365 SSO.
• District-controlled account provisioning and deprovisioning.
• Audit logs for privacy/security actions.
• Required Organization Privacy/Data Contact.
• Downloadable plain-English summary showing exactly how Qlef is configured for that organization.

What About FERPA and COPPA?

• Explain that Qlef is being designed around the privacy obligations schools face.
• Avoid treating "FERPA compliant" or "COPPA compliant" as a meaningless marketing badge.
• Explain school authorization for educational technology where legally applicable.
• Support direct parental consent where required.
• Organizations can require school authorization, parental consent, or both.
• Lower levels cannot weaken the Organization's consent requirements.
• Explain Qlef's role as a school-directed educational service rather than a consumer platform for children.
• Link eventually to detailed legal/privacy documentation.

What Can Other Students See?

• Students cannot see another student's submission.
• Students cannot see another student's individual feedback or scores.
• Students cannot inspect another student's individual readiness record.
• Qlef may provide aggregate Ensemble/section progress.
• Example: "Trumpets are 82% Ready."
• Directors control whether aggregate progress is visible to students.
• Small-group privacy considerations prevent aggregate reporting from inadvertently identifying individual students.

Can Someone Still Record the Screen?

Be transparent about the technical limits of media protection:

• "View only" does not mean physically impossible to reproduce.
• Qlef disables normal downloading.
• Playback requires authenticated authorization.
• Media uses protected/temporary access mechanisms rather than permanent public URLs.
• Qlef will use available device/browser protections against capture where practical.
• Capture detection/notification can be implemented where platforms support it.
• Dynamic viewer watermarking provides additional deterrence and accountability.
• No web or native application can prevent someone from physically recording a screen with another device.
• Avoid making security promises technology cannot actually guarantee.

What Happens When You Leave Qlef?

• Schools aren't locked into Qlef because their historical program data lives here.
• Student-specific data is deleted according to Qlef's deletion policies.
• Student submissions and media are not retained indefinitely.
• Schools can request immediate deletion.
• Ensemble-level historical analytics can be exported.
• Examples: assignment completion, readiness progression, acceptance rates and program-level trends.
• Section/instrument-level aggregate reporting where privacy thresholds permit it.
• Individual student records aren't included in analytics exports.
• Small-cohort protections prevent supposedly "anonymous" exports from effectively identifying a student.

Privacy Shouldn't Be the Reason You Can't Use Qlef

Schools shouldn't have to decide between useful instructional technology and their standards for protecting students. A district comfortable with securely hosted student video should be able to use it. A district that requires student media to remain inside Google Workspace or Microsoft 365 should be able to do that instead. And a student who cannot record video at all should still be able to participate through audio, in-person verification or another approved method.

That's why the most important privacy decision in Qlef isn't a particular encryption technology or storage provider. It's the decision to not make Qlef-hosted student video a requirement of the product in the first place. The same assignment and readiness system can work across very different privacy environments.

So when a director, parent or district technology administrator asks, "Can I trust Qlef with my students?" we don't want the answer to simply be "trust us." We want schools to be able to decide where student media lives, who can access it, how long it exists, and whether it needs to exist at all—and configure Qlef accordingly.