Skip to content
SquareCampus

Trust and security

Security answers for the people who review school software.

Access control, audit history, encryption, hosting, backups and how to report an issue — stated plainly, with the evidence behind each one shared in writing during security review.

Book a demoContact security

Audit timeline

Synthetic data

Control domains

The trust posture is designed for institutional accountability

Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature.

Access control

Access is role-based and scoped by campus. Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Authorisation is always decided inside SquareCampus, never by an email domain.

Audit history

Approvals, overrides and record changes are designed to be recorded with who made them, what changed and when, in the campus context they happened in.

Encryption

Data is encrypted in transit and at rest as part of the platform's baseline design. Implementation details are shared during security review.

Hosting

Managed cloud on Microsoft Azure in India by default; Enterprise private deployment on AWS, in a private cloud or on premises as a scoped service. Hosting details and data-flow documentation are given in writing during evaluation.

Backups and recovery

Availability, backup and recovery design are documented in writing during security review. We do not publish uptime, backup or recovery figures.

Reporting a security concern

Email security@squarecampus.com with a description, steps to reproduce and the likely impact. Sensitive reports can be encrypted with our PGP key.

Identity and access

Your identity environment remains yours

The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone.

All plans

Secure sign-in and authorisation

Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding.

Available separately

Institutional single sign-on

Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation.

Enterprise

Identity governance

Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery.

Your Microsoft environment

Stays under your administration

  1. Your administrator approves SquareCampus in your Microsoft Entra ID tenant.
  2. Staff sign in with their existing institutional Microsoft accounts.
  3. Your MFA, Conditional Access and user-assignment policies continue to apply.

SquareCampus authorisation

Governed inside the School OS

  1. SquareCampus validates that the sign-in came from your approved tenant.
  2. It resolves the person's institution membership and campus scope.
  3. It applies role, record and workflow permissions defined in SquareCampus.
  4. A secure SquareCampus session is issued.
Available separately on any plan

Microsoft Entra ID verifies who the user is. SquareCampus determines what the user may access and perform. Single sign-on is chosen by the institution, never required.

Sign-in modes the institution chooses between

  1. Mode 1SquareCampus-managed credentials, subject to deployment readiness
  2. Mode 2Credentials alongside institutional single sign-on, where supported by the agreed configuration
  3. Mode 3Institution-enforced single sign-on, where the institution's policy requires it and the configuration supports it
  • Single sign-on is optional. An institution is not required to adopt it, and is not required to move between Google Workspace and Microsoft to use SquareCampus.
  • Standard sign-in authenticates identity only. It does not require access to email, files, Teams, SharePoint or other Microsoft 365 data.
  • Single sign-on authenticates users; it does not create or remove them. Automated provisioning and deprovisioning are a lifecycle requirement scoped under Enterprise.
  • Where institution-enforced single sign-on is configured, SquareCampus credentials are designed not to act as an ordinary alternative route around the institution's identity policy.

Documents on request

What we share in writing during a security review

  • Completed vendor security questionnaires
  • Hosting and data-flow documentation
  • Availability, backup and recovery design
  • Encryption and access-control implementation notes
  • The Data Processing Addendum and data retention approach
  • Identity and sign-in configuration for your plan
Data Processing AddendumData retentionInfrastructurePGP key

Security questions

What review teams ask first

Where is data hosted?

SquareCampus is designed with an India-first hosting posture. Hosting details and data-flow documentation are shared during the security review process.

How is data encrypted?

Data is encrypted in transit and at rest as part of the platform's baseline design. Implementation details are available under the security review process.

Who can access data?

Access is role-based and least-privileged by design, with administrative access logged and traceable.

Do you support vendor security questionnaires?

Yes. We provide questionnaire support and can share security documentation and summaries on request.

Can an institution use normal SquareCampus credentials?

Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding.

Can staff sign in with our own Microsoft accounts?

Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation.

What identity options does Enterprise add?

Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery.

Is baseline security included in every plan?

Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature.

Who owns institutional data, and what happens when we leave?

The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment.

Who decides what a signed-in user may do?

The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone.

Security review

Bring your questionnaire, policy concerns, or institutional requirements.

The right trust conversation covers the real product controls, the operating posture, and how the institution can stay confident after go-live.

Book a demoEmail security