FERPA AUDIT EVIDENCE PACK · v1.0 · 2026-04-21

Auditor-ready FERPA evidence pack.
One source of truth.

What student data Pinnova handles, how we protect it, how long we keep it, and what we will never do with it — written for district IT directors, compliance officers, and counsel. The complete FERPA Audit Evidence Pack is provided to districts during procurement and security review.

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:

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:

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

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

7. Retention and deletion

DataRetention
Operational data (students, buses, routes, dispatches, incidents)Deleted 30 days after subscription end
FERPA audit recordsRetained 7 years
General audit logsRetained 2 years
BackupsRetained 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:

ProviderPurposeData involved
DigitalOceanHosting and managed databasePlatform data, encrypted at rest
StripeSubscription billingDistrict billing contact details — no student data
ResendAccount email deliveryAdministrator email addresses — no student data
Mapbox / OSRMMaps and routingCoordinates only — never student data
CloudflareSecurity and content deliveryWeb 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:

StepCommitment
DetectionContinuous monitoring
Triage and scopingWithin 4 hours of detection
District notificationWithin 72 hours of a confirmed breach
PostmortemWithin 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.

Request the evidence pack →