Is My College Data Safe
in CampusAlly?

The right data for the right role — no more, no less.

• Pre-built roles: Professor, Head of Department, Registrar, Finance Officer, Warden and more, each scoped to what the job needs — plus custom roles you define.
• Separation of duties: A professor can enter marks but not finalise them; a finance officer can handle billing but not academic records.
• One-step revocation: When someone leaves, their access can be switched off across the system in one action — no lingering logins.

Existing campus credentials, with an extra check on sensitive actions.

• Single Sign-On: Works with SAML 2.0, LDAP and Active Directory, including Microsoft Azure AD and Google Workspace — no separate password to remember.
• Second factor where it matters: Publishing results, processing a refund or editing a finalised record can ask for a second-factor confirmation.
• Sensible sessions: Auto-logout after inactivity and alerts on unusual sign-ins.

Every change leaves a time-stamped trace that's hard to alter quietly.

• What's recorded: The user, role, time, old and new values, and a reason note — captured the moment a change is saved.
• Tamper-evident: Later edits to a log entry would be apparent, so the trail is designed to make quiet tampering hard to hide rather than to promise it's impossible.
• Evidence goes to its owner: The change history feeds the modules that produce the reports — see the boundary note below.

Protected whether data is moving, stored, or being recovered.

• Encrypted connections and storage: Data is encrypted in transit between the app and the servers, and encrypted at rest in the database.
• Hosted in India: Student data stays on servers in India, in line with DPDP data-residency expectations — not sold, not used for ads.
• Regular backups: Backed up on a schedule with point-in-time restore, plus your own self-service export whenever you want a copy you control.