Security at LMS Bridge
For professors, department chairs, and school IT and security teams. Last updated: 2026-10-30
This page describes how LMS Bridge protects accounts, LMS access, and course and student data. For what data we collect and why, see our Privacy Policy. To report a security problem, see Reporting a security problem.
1. Accounts and login
- Passwords are never stored. We store a salted scrypt hash (random 16-byte salt per password) and compare hashes in constant time. Passwords must be at least 8 characters.
- School email required. Faculty and staff accounts need an institutional
email address (for example
.eduor.ac.uk). Every account must verify its email before its first login. - Verification and reset links are random, single-use, and expire after 48 hours. A password reset signs the account out on every device.
- Sessions use a random 256-bit token in a cookie marked
HttpOnly,Secure, andSameSite=Lax, so page scripts cannot read it and browsers send it only over HTTPS. Sessions last up to 30 days. Signing out deletes the session on the server. - Attack resistance. Login, registration, and password-reset requests are rate-limited per network address. Registration and password-reset responses are the same whether or not an account exists, so they do not reveal who has an account.
2. Connecting to your LMS
LMS Bridge works with Canvas, Blackboard, and Brightspace (D2L). It acts in the LMS as the professor who connected it, with that professor's own permissions, never with administrator rights. There are two ways to connect.
Sign in with your LMS (OAuth 2.0), recommended
The professor clicks Sign in with Canvas (or Blackboard or Brightspace), signs in on the LMS's own login page, and approves LMS Bridge. We never see the professor's LMS password.
- Each Canvas school controls access with its own developer key, created by the school's Canvas administrator. See setup for Canvas admins. The administrator enters the key on lmsbridge.ai over HTTPS, never by email. It is encrypted on arrival and stored only after Canvas accepts it and confirms that the person is a Canvas account admin.
- Every sign-in uses a random, single-use
statevalue that expires after 10 minutes, which blocks forged or replayed sign-ins. - The LMS returns a short-lived access token (one hour on Canvas) and a refresh token. Both are encrypted on our server. The professor's browser receives only an opaque reference, never an LMS token. A sign-in that is not used for 30 days ends.
- The server sends a token only to the LMS site where the professor signed in, and refuses to send it anywhere else.
- Revoking access. A school can switch off its developer key in Canvas, which ends every sign-in at once. A professor can remove LMS Bridge under Canvas Account โ Settings โ Approved Integrations.
Pasted access token
A professor can also generate a Canvas access token and paste it into the dashboard. The token stays in that professor's browser and goes to our server over HTTPS with each request. We store a pasted token only when a feature must run while the professor is away, such as scheduled grading, check-ins, or outcome reports. Stored tokens are encrypted. Professors can delete or expire a token in Canvas at any time.
3. Encryption
- In transit: all traffic to lmsbridge.ai uses HTTPS (TLS). Plain HTTP requests are redirected to HTTPS, and browsers are told to use HTTPS only (HSTS). Calls from our server to your LMS also use HTTPS.
- At rest: LMS access and refresh tokens, Canvas developer-key secrets, and school-provided AI keys and email passwords are encrypted with Fernet (AES-128-CBC with HMAC-SHA256 authentication). The encryption keys are kept apart from the databases, in files that only the service and the system administrator can read. If encryption is unavailable, the service refuses to store a token rather than store it unencrypted.
4. Who can see what
- Professors see their own courses, and only what their LMS account can already see.
- Department roles (chair, program coordinator) see department data, such as outcome reports, for their own institution only.
- Institution subdomains (for example
yourschool.lmsbridge.ai) admit only signed-in members of that institution. - User administration (assigning roles, importing the course catalog and faculty roster) needs a chair role, and only within the chair's own institution. Creating or deleting accounts directly is reserved for platform administrators.
- Internal services, such as the AI job queue, accept only callers that present a secret key held on our servers.
- Demo sandboxes run as separate instances, with their own databases, files, and login cookies. Sandbox data never mixes with production data.
5. AI processing
- AI features such as grading suggestions, feedback drafts, and course building send the relevant course material to an AI model. Depending on the feature, that can include assignment text, rubrics, and student submissions.
- AI grading suggestions are drafts that the professor reviews before they are posted. The one exception is scheduled auto-grading: a professor who turns it on for an assignment lets LMS Bridge post grades and comments to the LMS directly. The professor can review and change them in the LMS, and can turn the schedule off at any time.
- No student names or IDs. The AI requests LMS Bridge builds do not include student names or LMS IDs. Messages to students get the student's name only after the AI has written the draft. A student's own work is sent as the student wrote it.
- Our AI provider is listed with our other sub-processors in the Privacy Policy. A school can instead connect its own AI service, so that AI requests go only to a provider the school has approved.
6. Student data
- We read student data from your LMS only to deliver the features a professor uses, and we never sell it or use it for advertising.
- Institutions can designate LMS Bridge as a "school official with a legitimate educational interest" under FERPA through a Data Use Agreement. Write to us to start one. Without one, individual professors are responsible for following their institution's policies.
- The LMS stays the system of record for grades. Grades and comments that a professor approves are written back to the LMS.
7. Hosting and operations
- The service runs on Amazon Web Services in the United States (us-east-1).
- Administrative SSH access is limited to approved network addresses. Only web traffic (HTTPS) is open to the internet.
- The application runs as a dedicated, unprivileged system user with no login shell. Its services run under systemd restrictions that block privilege escalation and make system directories read-only.
- Secrets such as encryption keys and API keys live in a configuration file readable only by the system administrator. They are never stored in our code repository.
- Backups: before every software update we take a consistent snapshot of each database and keep each snapshot for 30 days.
- Activity logs record who made changes, and when (user, action, time, and network address). Logs do not record request contents.
8. Incidents
If we find that a security incident has exposed your data, we will tell you without undue delay, and in any case within 72 hours of confirming it, as our Privacy Policy states.
9. Reporting a security problem
If you think you have found a security problem in LMS Bridge, email support@lmsbridge.ai with the subject "Security report". Include the steps to reproduce it. Please do not access other people's data, and give us a reasonable time to fix the problem before you disclose it. We do not take action against good-faith research that follows these rules.
Contact
Security questionnaires (HECVAT and similar) and other questions: support@lmsbridge.ai.