If LMS Bridge is being adopted across multiple instructors in your program or department, your data governance, IT, and compliance teams will want documentation. Below is everything they typically ask for. Share the relevant links directly — no gatekeeping, no lead-capture friction.
Talking points for the conversation: LMS Bridge ingests Canvas data per instructor under instructor-issued tokens; per-student grade data is processed only in memory to compute aggregate outcome counts (no per-student data persisted); Canvas tokens are encrypted at rest; sub-processors are documented; the standard DUA template designates LMS Bridge as a "school official" under FERPA upon execution.
FERPA-aligned DUA template, designed to be redlined by your General Counsel against your institution's standard form. Includes Schedule A specific to the outcomes assessment data flow.
Download / view →What we collect, why, how it's stored, retention windows, sub-processors, and FERPA position. The reference for what an instructor agrees to at signup.
Read →Click-through terms each individual instructor accepts at signup. Does not bind your institution; the DUA covers institutional designations.
Read →What instructors agree not to do with the Service. Includes the explicit duty to initiate a DUA conversation when use expands beyond individual pedagogy.
Read →Pre-completed responses available on request. Covers data protection, business continuity, vulnerability management, sub-processors. Reply within 5 business days.
Request →Current sub-processors (AWS, Anthropic, Resend) with jurisdiction + data-flow notes, plus a draft Data Protection Impact Assessment for high-risk processing reviews.
Request →