Students join with a first name and a PIN — no student emails, no accounts to provision, nothing sold or shared. Here's exactly what we hold, and what we never do.
To join a class, a student enters a first name and a 4-digit PIN their teacher sets. That's it. We do not ask students for a last name, an email address, a phone number, a home address, a birthdate, a parent's information, or a government ID. A student account exists only so their teacher can see their quiz scores and flashcard progress.
A teacher creates an account with their name, work email, and a password — the normal things needed to sign in and run a gradebook. Teachers are adults acting in their professional role.
Any records in DroneReady belong to the school. We handle them only as a school official acting under the school's direction, consistent with FERPA. We will sign your Data Privacy Agreement (DPA) before any district contract, complete your security questionnaire, and delete your data on request. We're a small independent publisher — we are not SOC 2 certified, and we'll tell you that up front rather than imply otherwise.
Students sign in with a short PIN rather than a reusable password, connections are encrypted in transit, teacher sessions use secure cookies, and teacher password resets are single-use and time-limited.
We're adding an optional "Sign in with Google" for teachers, and for students only where a district chooses to enable it. It will always be optional: the first-name-and-PIN path stays available, so a district that doesn't allow third-party access to its Google accounts loses nothing. If a student does sign in with Google, we use their school Google identity only to log them in.
Email [email protected] — a real person reads it. We'll send our data-practices summary, sign your DPA, or answer anything your IT or privacy office needs.
Last updated November 13, 2026. This page describes how the DroneReady curriculum and LMS handle data; it isn't legal advice, and it doesn't override a signed agreement between DroneReady and your school or district.
Spot a wrong answer, a confusing page, a bug, or have an idea? Tell us — no sign-in, and please don't include any personal info.
✓ Thanks — got it. This goes to the team to make the course better.