Pinnova FERPA Compliance
Version 1.0 — April 21, 2026
How Pinnova protects student data: what we handle, how we protect it, how long we keep it, and the commitments your district can hold us to. Written for district IT directors, compliance officers, and counsel. See also our Privacy Policy and FERPA controls.
The short version: Pinnova acts as a “school official” under FERPA. We use student data only to run your transportation operation, encrypt it in transit and at rest, record every access to it, and delete it shortly after your subscription ends — and we never sell it, rent it, or use it for advertising. Ever.
1. The law we build to
Pinnova is designed around the Family Educational Rights and Privacy Act (FERPA) — 20 U.S.C. § 1232g and its regulations at 34 C.F.R. Part 99 — including:
- § 99.31(a)(1)(i)(B) — the “school official” provision under which a district designates Pinnova to handle student data for a legitimate educational interest.
- § 99.32 — the record-of-access requirement: who has accessed a student’s record must itself be recorded.
- State student-privacy laws — including VA Code § 22.1-287.04, MD § 7-105, and NC GS 115C-402.5.
2. Our role: your school official
Each customer district designates Pinnova as a “school official” with a legitimate educational interest under FERPA, 34 C.F.R. § 99.31(a)(1)(i)(B). We process student data solely to provide transportation management services to that district — for no other purpose, and for no one else.
3. The data we handle
To run buses safely and on time, Pinnova handles only the student data your district provides for transportation:
- Student information — name, grade, date of birth, home address, and assigned pickup and drop-off points and times.
- Parent and guardian information — names, email addresses, phone numbers, relationship to the student, emergency contacts, and the adults authorized to receive a student at drop-off.
- IEP and special-needs transportation accommodations — the requirements a student’s plan attaches to their ride.
- Operational data — routes, stops, dispatches, incidents, and live bus locations.
District staff accounts — the names and work contact details of your own employees — are ordinary business contact data, not student records.
4. How we protect it
- Encryption — student data is encrypted at rest with AES-256 and in transit with TLS 1.2 or higher.
- Role-based access control — administrators, dispatchers, transportation staff, drivers, and parents each see only what their role requires, and nothing more.
- District separation — one district’s data is never visible to another district.
- Parent portal protections — a parent can only ever see their own child’s information. The most sensitive details — date of birth, home address, and emergency contacts — are never displayed back to parents, and lookups are protected against repeated guessing.
- IEP safeguards — IEP transportation accommodations are restricted to authorized transportation staff only. They are never accessible through the parent portal or a general dispatch view.
- Personal data stays out of everyday logs — student personal information is kept out of routine operational system logs.
5. Every access is recorded
FERPA § 99.32 requires a record of access to student records. Pinnova maintains a complete audit log of access to student data — including parent lookups, whether they succeed or fail — and a district can review the access record for its own students. We retain these audit records for 7 years, even after a subscription ends, so districts can correlate them with their own records.
6. What Pinnova will never do
- Sell, rent, or lease student data
- Use student data for advertising or profiling
- Build non-educational profiles on students
- Disclose student data without district consent
7. Retention and deletion
| Data | Retention |
|---|---|
| Operational data (students, buses, routes, dispatches, incidents) | Deleted 30 days after subscription end |
| FERPA audit records | Retained 7 years |
| General audit logs | Retained 2 years |
| Backups | Retained 7 days |
8. Sub-processors
Pinnova does not sell or share district data. A small number of vetted service providers process data on our behalf, under contract, solely to run the platform:
| Provider | Purpose | Data involved |
|---|---|---|
| DigitalOcean | Hosting and managed database | Platform data, encrypted at rest |
| Stripe | Subscription billing | District billing contact details — no student data |
| Resend | Account email delivery | Administrator email addresses — no student data |
| Mapbox / OSRM | Maps and routing | Coordinates only — never student data |
| Cloudflare | Security and content delivery | Web traffic in transit |
These providers are the entire third-party surface.
9. If something goes wrong
If a security incident involves student data, we work to a fixed clock:
| Step | Commitment |
|---|---|
| Detection | Continuous monitoring |
| Triage and scoping | Within 4 hours of detection |
| District notification | Within 72 hours of a confirmed breach |
| Postmortem | Within 14 days |
Report a security concern to security@pinnovatms.com. District privacy inquiries go to privacy@pinnovatms.com.
10. Request the full evidence pack
This page is the public summary. The complete FERPA Audit Evidence Pack — the implementation-level document your IT and security teams will want during procurement and security review — is provided directly to districts on request.