Skip to content

SECURITY & DATA

How CampusOS
keeps your data safe.

A shared student record needs clear boundaries. Institution isolation, permissions and encryption are part of the platform’s foundation.

  • Institution boundaries

    Every record belongs to one institution, and only its members can reach it.

  • Sensitive records

    Admissions, clinical, leave and wellbeing details are stored in encrypted fields.

  • Role-based access

    Permissions decide which modules, records and actions each person can use.

  • Accountability

    Audit logs record important actions, who took them and in which institution.

ENCRYPTION

Protection where it matters.

At rest

Sensitive module fields use AES-256-GCM encryption. Module-specific data and index keys keep the encryption boundaries separate.

In transit

The public service uses HTTPS with TLS. Authenticated requests are checked against the user’s institution membership and permissions.

HOSTING & RESIDENCY

Where your data is hosted.

The current service is hosted on AWS in Mumbai, India. Discuss your institution’s residency and contractual requirements with us before rollout.

Institution separation is enforced through tenant scoping and access checks. A shared deployment does not imply a dedicated database or account for every institution.

CARE & CONFIDENTIALITY

Confidential records stay confidential.

Clinical and counselling information has its own permission boundaries. Being an institution administrator does not automatically grant access to confidential wellbeing case notes.

Teams can share the operational context their work requires while protected records remain restricted to authorised staff.

CONSENT & DATA HANDLING

Make the responsibilities clear.

Admissions and alumni workflows record consent, including the wording accepted at the time. Available export and data-handling workflows vary by module; we’ll walk through your requirements during evaluation.

We’ll review retention, access, consent and contractual requirements with your institution. Specific legal obligations depend on your location and use of the service.

For institutions in India, we'll walk you through how CampusOS supports your obligations under the Digital Personal Data Protection (DPDP) Act.

SEE CAMPUSOS

Tell us one workflow
you wish worked better.

Admissions. Leave approvals. Medical records. Attendance.
We’ll focus on the parts of CampusOS that matter to you.

The live product. Your workflows. A focused conversation.