Privacy Policy
Effective date: 2026-06-08 · Last updated: 2026-10-30
1. What this policy covers
This policy describes what data LMS Bridge collects when you use the Service, why we collect it, how we store it, and your rights. For institutional deployments under a separate Data Use Agreement (DUA) or Data Processing Agreement (DPA), the terms of that agreement control to the extent of any conflict.
2. Data we collect from you (the instructor)
- Account information: name, email address, password (hashed), institution name, role, discipline, the LMS you use, and other onboarding fields you provide.
- Free-text descriptions you provide (e.g., teaching pain points, faculty narrative for reports). Used to improve the product and inform feature priorities.
- LMS access tokens. A token you paste stays in your browser and is sent with each request; we store it only when a feature must run while you are away (scheduled grading, check-ins, outcome reports). Tokens from "Sign in with Canvas" and other LMS sign-ins are kept only on our server. Stored tokens are encrypted at rest (Fernet: AES-128 with HMAC-SHA256) using a key kept in our server environment, separate from the database.
- Server logs: IP address, browser, timestamps, and the URL of pages you visit. Used for security monitoring and debugging.
3. Data we read from Canvas on your behalf
When you connect a Canvas access token, we use it to call the Canvas API to read:
- Your course list, assignments, rubrics, quiz questions and quiz statistics
- Per-student submission scores and rubric assessments (for outcome reports, used only to compute aggregate outcome attainment — see §4)
- Student submissions (text and attached files), when you use AI grading or feedback
- Your class roster (student names and email addresses), when you use features that address students, such as check-in messages and polls
We do not write to Canvas without your explicit instruction (e.g., when you click "Push to Canvas"). We do not request admin scopes or institutional API tokens.
4. Aggregation guarantee
When you run "Compute" on an Outcomes Assessment report, we pull per-student grade data from Canvas through our server, but we do not store per-student grade data. We store only the aggregate counts: how many students fell into each of the four attainment levels per Performance Indicator. Per-student data is held only in memory during the computation and discarded immediately after.
5. AI processing
Some features use a third-party AI provider (listed in §11) to generate content (lecture material, assessment items, grading suggestions, feedback and message drafts, narrative drafts, tag suggestions). A request includes the prompt you supply and the material the feature needs: for example, the assignment description, the rubric, and, for AI grading, the student's submission. The requests we build do not include student names or LMS IDs; a student's own work is sent as the student wrote it. An institution can instead connect its own AI service, so that AI requests go only to a provider it has approved. The AI provider's data handling is governed by its published policies.
5a. FERPA safeguards
To protect student privacy under FERPA, LMS Bridge implements the following safeguards:
- The professor's own access: we reach student data only through the professor's own LMS access, so we see only what that professor can already see.
- No names in AI requests: the AI requests we build do not include student names or LMS IDs (see §5).
- Pseudonymous records: records of AI-detection scans are kept under a hash of the student's LMS ID instead of the ID itself.
- Activity logging: changes made through the Service are logged with the user, action, time, and network address. Logs do not record request contents.
- Educator domain validation: faculty and staff accounts require a verified institutional email address (.edu, .ac.uk, etc.).
- Encryption: all traffic uses HTTPS, and stored LMS tokens are encrypted (see §2 and our Security page).
6. Cookies and tracking
We set a session cookie when you log in so we can identify you across page loads. We do not use third-party advertising cookies or cross-site tracking.
7. Where data is stored
Application data is stored on servers operated by Amazon Web Services in the United States. Backups are retained for up to 30 days.
8. Retention
- Account data: retained until you delete your account.
- Stored LMS tokens: deleted when you delete the outcome report, when scheduled grading finishes, or when you turn off check-ins for the course. LMS sign-ins end after 30 days without use. You can also revoke any token in your LMS at any time.
- Aggregate outcome counts and narratives: retained for the standard accreditation cycle (typically 6 years for ABET) unless your institution requires shorter retention under a DUA.
- Server logs: retained only as long as needed for security monitoring and debugging.
9. Your rights
You can request to access, correct, export, or delete your data at any time by emailing support@lmsbridge.ai. We will respond within 30 days. If you are in a jurisdiction with specific data subject rights (e.g., California, EU), those rights apply.
10. FERPA
LMS Bridge handles data that may constitute "educational records" under the Family Educational Rights and Privacy Act. For institutional deployments, LMS Bridge can be designated as a "school official with legitimate educational interest" under FERPA via a Data Use Agreement. Until such designation, individual instructors using the Service are responsible for ensuring their use complies with their institution's policies.
11. Sub-processors
We use the following sub-processors:
- Amazon Web Services (hosting)
- Anthropic (AI inference)
- Resend (transactional email)
We will give 30 days' notice before engaging a new sub-processor.
12. Security incident notification
If we determine that a security incident has resulted in unauthorized access to your data, we will notify you without undue delay and in any case within 72 hours of confirmation.
13. Contact
Privacy questions: support@lmsbridge.ai.