Trust, access, and governance

Security and student data privacy at Faraday AI.

Faraday AI separates account access, workspace capabilities, connected providers, and institutional data authority so that one kind of access is not mistaken for another.

Access follows identity, role, and ownership

Faraday AI uses multiple boundaries together rather than treating a login or provider connection as universal authority.

Role-based capabilities

Teacher, administrator, developer, and other capabilities are checked by the service before protected workflows are exposed.

Workspace and tenant boundaries

Saved work and education records are scoped to authorized owners, workspaces, and organizations.

Connected-account boundaries

Connecting a Microsoft or Google account identifies that provider account; it does not grant classroom, school, or district-data permissions.

Real student data requires an authorized school workspace

General, personal, guest, and synthetic-demo workspaces are not authorized for real student records.

Institutional authorization

Processing real education records requires an authorized school or district workspace, a written agreement, configured access, and a documented purpose and retention period.

Human responsibility

Educators and institutions remain responsible for notices, consent or authority assigned to them, professional review, and decisions that must stay human.

Product features and security controls do not by themselves establish FERPA school-official authority, verified COPPA school consent, a HIPAA business-associate relationship, or a certification. Contractual and legal requirements must be confirmed for each rollout.

Connected systems are rollout-specific

Microsoft 365 storage is the currently established external connection. Other Microsoft, Google Workspace, SSO, SIS, LMS, calendar, mailbox, and rostering capabilities depend on provider setup, administrator consent, account validation, and the specific institutional rollout.

  • Use only the data necessary for the authorized workflow.
  • Keep personal and synthetic-demo workspaces free of real student records.
  • Review generated material before it is used for instruction, communication, or decisions.
  • Use the legal policies and institution-specific agreement as the controlling terms.

Discuss your school’s requirements

Bring your roles, systems, data classifications, approval needs, and retention requirements to a tailored walkthrough.

Request a walkthrough