Governance and privacy
Student rows are isolated per account by row-level security, not by a separate tenant database. FERPA-aligned defaults for K-12 and higher-ed. No model is trained on student work. The DPA at /legal/dpa is published for your counsel to read and redline — it is a draft pending our own counsel review, which the document says on its face, and it is not pre-signed.
How students get in
An emailed invite, a join link you post anywhere in your LMS, or domain auto-join: set a verified email domain on the organisation and anyone who signs up from it lands in it, taking a seat. Setup is minutes, not an IT project, because there is nothing to install.
There is no SAML, no OIDC, no LTI of any version, and no SIS or SFTP roster sync. This page previously said otherwise; none of it exists in the product. If deep LMS launch or true SSO is a hard requirement for your deployment, Brainback is not the right tool this term, and we would rather say that here than during your implementation window.
Multi-year deployments
Successful pilots convert to multi-year deployments. Terms are annual or 3-year with a locked seat price. Contact institutions@brainback.chat to start the conversation. Response within 2 business days.
Support during a pilot
You get the person who built it, by email, same day in North American hours. There is no CSM, no Slack Connect channel and no ticket queue, because there is no team to staff them — Brainback is one person. At pilot scale that is an advantage and you should use it; above it, it is a real limit and you should weigh it.
Instructors do get a group dashboard with cohort metrics, which is built and content-blind.