Records the platform supports
Records the platform is designed to organize include student, guardian, enrollment, package, lesson, instructor, vehicle, document, waiver, payment-status, communication, portal, and support records. Public websites are separated from authenticated dashboard and document workflows.
Schools should collect only information needed for legitimate operations and should avoid placing unnecessary sensitive information in free-text fields, support messages, AI prompts, or uploads.
Platform safeguards
Safeguards are designed to include authenticated access, role-based permissions, tenant-scoped queries, restricted media delivery, encrypted transport, secure secret handling, input validation, anti-spam and abuse controls, audit and security logging, backups, deployment checks, and monitoring.
Providers used for hosting, email, payments, security, analytics, support, and optional AI functions receive only the access reasonably needed for their role and operate under their own security and privacy commitments.
Shared responsibility
The platform maintains service-level controls; each school controls its users, role assignments, passwords, devices, exports, content, forms, integrations, and retention choices. Schools must remove former users, review permissions, train staff, protect local copies, and report suspected misuse promptly.
No system can guarantee absolute confidentiality, integrity, or availability. Security measures reduce risk but do not eliminate phishing, compromised devices, user error, provider incidents, or sophisticated attacks.
Shared responsibility for minors and guardians
Parents or guardians should submit information for minors when required. Schools must establish appropriate notice, consent, access, correction, minimization, and deletion procedures and must not assume a generic checkbox or stored signature resolves every legal requirement.
Documents are available only through controlled workflows, but schools should avoid requesting unnecessary government IDs or sensitive records. Stripe handles full card credentials; the application retains only identifiers and transaction status needed for billing and school workflows.
Incidents and continuity
We investigate suspected incidents, take proportionate containment and remediation steps, preserve necessary evidence, and provide required notifications. Schools must maintain current contacts and cooperate with reasonable verification and response requests.
Backups and recovery procedures support continuity but are not a replacement for school-required exports, retention, emergency communications, or business-continuity planning.
Questions
Security or privacy concerns should be sent to support@softwarefordrivingschool.com without including passwords, full card numbers, or unnecessary student documents. Contact: Software for Driving School, 8245 NW 36 Street #5, Doral, FL 33166; support@softwarefordrivingschool.com; 617-600-3678.