Rollbook touches the most sensitive data a college holds. This page says plainly how that access works, where data lives, and what happens if you leave. Your IT staff and counsel are welcome to email hello@getrollbook.com with anything this page doesn't answer.
Rollbook operates as a school official with a legitimate educational interest under each school's FERPA policy (34 CFR 99.31(a)(1)), performing services the institution would otherwise perform for itself, under the school's direct control with respect to records. A data processing addendum naming FERPA, our obligations, and our subprocessors comes with every contract, before any key is exchanged.
Current subprocessors: Cloudflare (site and application hosting), Stripe (payments; never sees student records), Google (only when your school uses Feeds delivery to Google Sheets). The DPA lists these and commits to notice before any change.
A formal SOC 2 examination is planned as the company grows; until then, a written security summary is available for your vendor-review file, and every claim on this page is contractual, not marketing.
On request or at termination, the exit pack produces your complete data in standard formats: CSV bundles shaped for common student-record systems, transcript-ready extracts, and your full snapshot history. Because the database is in your account, you keep everything even if you simply stop paying. There is no data-hostage scenario here, by design.