Tenant isolation
Institution data is kept separated through the platform architecture and tenant-aware routing.
Security
Security should be visible in the architecture.
We keep public claims careful and specific. AcademicGrid is designed around tenant boundaries, role-aware access, auditability, and separated admin surfaces.
Request security reviewPublic app
Lead and portal handoff
API guard
Validated endpoints
Tenant data
Scoped records
RBAC and personas
Users see only scoped capabilities.
Audit trail
Sensitive operational changes can be reviewed.
Role-based access
Persona and permission layers control what each user can see or edit.
Audit logging
Sensitive actions can be tracked so administrators have a clearer operational record.
Public endpoint protection
Public routes are treated carefully so signup and lead paths stay safe.
Backup and restore posture
Recovery expectations should be confirmed as part of the guided rollout and support model.
SuperAdmin separation
The SuperAdmin security domain stays separate from public marketing and institution access.
What we will discuss
How tenant boundaries are handled in the platform
How the public signup route is gated
How role and persona access stays scoped
How SuperAdmin stays separated from institution access
Enterprise foundation
Qualified review, not public overclaiming.
Security review conversations should stay grounded in the architecture we can explain today and the roadmap we are actively building.
Contact security teamSecurity FAQs
Is AcademicGrid encrypted?
Yes. All data in transit uses TLS encryption. At-rest encryption policies are configured per institution and confirmed during the security review phase.
What compliance certifications do you have?
We do not publish certification claims we have not independently verified. Our security architecture, access controls, and any compliance roadmap are reviewed in detail with your institution during the security review.
How are backups handled?
Backups are maintained for disaster recovery. Backup retention, restore procedures, and RTO/RPO expectations are confirmed as part of the service agreement and rollout planning.
Can we audit access logs?
Yes. Audit logging is built into the platform. Institutional admins can access logs for their institution's data. Detailed audit export and retention policies are configured based on compliance needs.
How is student data protected?
Student data is protected through tenant isolation, role-based access control, and audit logging. Parents and students see only their own data through role-restricted portals.