Trust

Security and data handling

This page is maintained by ExperLogbook to answer common questions institutions ask before piloting. It describes the app-visible controls in place today — not a third-party certification.

Role-based access

Residents, faculty, HOD, dean, MEU, platform admin — every action scoped by role. Row-level security in the database enforces access, not just the UI.

Audit trail

Every entry create, edit, sign-off, role grant and configuration change is logged with actor, timestamp and change details.

Encrypted in transit and at rest

TLS 1.2+ in transit; disk-level encryption at rest through the underlying cloud provider.

India-region hosting

Application data hosted on India-region infrastructure. Backups retained per institution policy.

Authentication

Email/password with strength enforcement. Optional social sign-in. Password reset with expiring tokens.

Responsible disclosure

Report a security issue via security@experlogbook.com. We acknowledge within one working day.

This page describes controls enabled in the app today. Statements here are not, and should not be read as, a certification of compliance with any regulatory or industry standard. For institutional due diligence, contact us for a security questionnaire response.

See ExperLogbook in your college

30-minute walkthrough for HODs, deans and MEUs. NMC-ready reports, competency dashboards, faculty e-sign-off.