Not a certification claim — a plain description of the engineering behind the vault, the audit trail, and the retention timers your school relies on.
Vendor notice: Driving School Desk is software for licensed Texas driver education providers. We are not a TDLR-licensed school, not a TDLR partner, and not a substitute for your provider obligations. This page describes our engineering practices, not a compliance certification.
No jargon, no badges we don't have. Just what the system does today.
Student records, documents, and bookings are scoped to the school that owns them. Automated checks run before every production deploy specifically to catch any code change that could let one school see another school's records — that check blocks the deploy if it fails; it is not a manual promise.
Document uploads, road test outcomes, and other status changes on a student's compliance file are timestamped on the compliance timeline. As enrollment e-sign rolls out, approving, rejecting, requesting corrections on, or retracting a contract is built to require a written reason the same way — nothing gets silently edited.
Texas driver education providers must keep student records for at least three years after completion or withdrawal. DSD calculates that date automatically from the completion or withdrawal date already in the system, instead of relying on a sticky note or a calendar reminder.
The Teen enrollment form calls for a parent or guardian signature. As we roll out e-sign, that flow is built to enforce the second signature before a teen contract can be marked complete — the same requirement as the paper process, not a shortcut around it.
An instructor sees the students assigned to them. An admin sees their own school. Our own staff access is limited to what is needed to provide support — not open by default.
If a school cancels, records stay available to export for 90 days before deletion. We do not hold your student records hostage to keep you as a customer.
Driving School Desk runs on Google Cloud (Cloud Run + Cloud SQL) — the same class of infrastructure used for regulated workloads generally. We do not hold a specific third-party compliance certification today (for example, SOC 2), and we won't claim one we don't have. If that becomes something our schools or a regulator need from us, we'll pursue it and update this page.
Also see our Privacy Policy and TDLR compliance tooling overview.
No. Driving School Desk is independent software for licensed Texas driver education providers. We are not a TDLR partner, not TDLR-approved software, and not a TDLR-licensed school.
No — and we will not claim one we do not have. This page describes engineering practices already built into the platform (tenant isolation gates, the compliance timeline, retention automation) — some tied to features still rolling out, like enrollment e-sign. If schools or a regulator need a formal attestation, we will pursue it and update this page.
Privacy Policy and Terms of Service are linked in the footer. This page is a plain-language companion, not a substitute for those documents.
Email us directly — a real person replies, not a support bot.
We use cookies and similar technologies to improve your experience and understand how our site is used. See our Cookie Policy and Privacy Policy.