[ NARROW ACCESS AND EXPLICIT OWNERSHIP ]
Security and privacy
Protect school information with tenant boundaries, role-based review, and deliberate operations.
Keep schools and classes separate
Teacher review is limited to assigned school classes. It does not include another school or unrelated personal conversations.
Minimize data movement
Approve each connected source and provider. Keep credentials out of content, logs, and support messages.
Review operational controls
Check role changes, revoked access, backups, monitoring, and incident contacts on a regular schedule.
School access has explicit boundaries
Membership and assigned classes determine who can use school resources and review conversations. Teachers need the prompts and responses for their own classes; this does not give them access to unrelated classes or personal accounts.
Guardrails combine several controls
Class instructions shape the learning response. Model access and spending limits are enforced separately from those instructions. Safety review can restrict unsuitable output. These layers reduce risk, but schools should still test realistic misuse and review reported failures.
Review the data flow before adding sources
Decide what material may be sent to the selected model provider and who may retrieve connected documents. Provider processing terms can vary. Use the privacy and legal pages to review the operating terms, and raise school-specific requirements before rollout.
Report a security concern
Send the affected service, a concise description, and safe reproduction steps to support@narb.cc. Avoid including live credentials or other people's records. For an access concern, stop using the exposed data and describe the boundary that failed.