A Divyarshi AI product family

Security & DPDP: Security, audit trails and DPDP tools for every institution

Sign-in, roles, audit trails and DPDP tools shared by every module and every institution.

30 of 38 features live

Admissions log change recorded; the integrity check confirms nothing was alteredIllustration · fictional data
  1. Enquiry
  2. Applicant
  3. Student
  4. Supported
  5. Graduate

Security & DPDP belongs to no single stage: it runs under every stage of the student record.

  • Aadhaar never stored: detected and removed automatically
  • Tamper-evident audit logs with a one-click integrity check
  • Built for DPDP: consent per purpose, guardian consent, erasure

What you'll see

Security & DPDP at work

IT · Data protection

Record consent per purpose and act on data requests

Consent is recorded per purpose against the notice version, and minor applicants need guardian consent by one-time code. Applicants can download, correct or erase their data, and erasure reaches the student account.

Guardian consent recorded by one-time code for a minor applicantIllustration · fictional data
IQAC · Activity log

Prove that no log entry was altered

The activity log records who did what, when and from where. Activity and admissions logs are tamper-evident, and a one-click check confirms no entry was changed.

One-click integrity check passed on the admissions logIllustration · fictional data
IT · Roles and access

Give each office exactly the access it needs

Ready roles cover admin, staff, teacher, student and parent, and access follows the org chart. Lend a post's access for set dates, and review who holds admin access and why.

Dean's access lent for set dates; it ends by itselfIllustration · fictional data

Who uses it

Part of these solutions

Try it yourself

Security & DPDP in 7 steps, on your own

This is the tour your sandbox opens with. Each step says which login to use; in the sandbox it also says exactly where to click. No call needed.

  1. Admissions HeadOpen the Consent section.The consent history on every lead, Given or Refused / withdrawn, against the privacy notice in force at the time.
  2. Admissions HeadClick 'Put on hold', then 'Lift hold'.A record on legal hold cannot be erased: the 'Erase PII (irreversible)' button is disabled while the hold is on. Please do not erase demo leads.
  3. Admissions HeadFilter by Open and open a request.Applicants' requests to download, correct or erase their data, each with a due date and a recorded answer.
  4. Admissions HeadLook at the retention schedule, then the branding settings.How long each kind of record is kept, and the university's own logo and colours (the Sumeru University marks printed on every PDF).
  5. Admissions HeadLook at the two-step sign-in options and the devices signed in now.Two-step sign-in with an authenticator app. Please don't switch it on in a sandbox login, or you may lock yourself out.
  6. StudentOpen the page.A student sees their own sign-ins, devices, AI use and who opened their record.
  7. StudentClick 'Sign out everywhere else'.Anyone can end sessions on other devices they don't recognise.

Try Security & DPDP yourself 10 days, fictional data, your institution email.

All features

38 features in 7 groups, 30 live in production today.

Secure sign-in5 of 7 live · 2 ready
  • Strong password rules; common passwords refused
  • Account lockout and CAPTCHA after repeated failures
  • Two-step sign-in with an authenticator app
  • Password change signs the account out everywhere
  • See your signed-in devices and sign out any of them
  • Mandatory two-step sign-in for admin staffReady
  • Forced password change at first sign-inReady
Single sign-on and passkeys0 of 3 live · 3 ready
  • Google Workspace and Microsoft 365 single sign-onReady
  • SAML single sign-on (Okta, ADFS and similar)Ready
  • Passkeys: fingerprint, Face ID or security keyReady
Roles and access5 of 6 live · 1 ready
  • Ready roles for admin, staff, teacher, student and parent
  • Access follows the org chart: deans see their school only
  • Lend a post's access for set dates; it ends by itself
  • Read-only 'see what they see' view, with a logged reason
  • Access review: who holds admin access and why
  • Custom roles with an editable feature-by-action matrixReady
Multi-institution and white-label5 of 5 live
  • Several institutions in one system, data kept separate
  • Switch each module on or off per institute
  • Dedicated servers for an institute that wants its own
  • White-label: name, logo, colours, login images, email sender
  • Runs on the institute's own web address, with HTTPS
Data protection and DPDP7 of 9 live · 2 ready
  • Consent recorded per purpose, against the notice version
  • Guardian consent by one-time code for minor applicants
  • Applicants can download, correct or erase their data
  • Erasure reaches the student account; reports still total
  • Aadhaar never stored: auto-detected and removed
  • Security alerts on bulk exports and sign-in attacks
  • Incident plan for CERT-In and the Data Protection Board
  • Retention schedule with preview and legal holdReady
  • Field-level encryption for guardian contacts and private notesReady
Audit trail and records5 of 5 live
  • Activity log: who did what, when and from where
  • Tamper-evident activity and admissions logs
  • One-click check that no log entry was altered
  • Uploaded documents open only for people allowed to see them
  • Export to CSV and Excel; PDFs for receipts and certificates
Releases and backups3 of 3 live
  • Automated tests and human approval before every release
  • Every release tried on a separate test copy first
  • Nightly backups, with a locked copy kept separately

Items without a tag are live: in production use today. Ready means built and switched on per institution when needed.

Questions we get asked

Is Intelversity designed for the DPDP Act?

Yes. It records consent per purpose, takes guardian consent for minor applicants, lets applicants download, correct or erase their data, and has an incident plan for CERT-In and the Data Protection Board.

Does it store Aadhaar numbers?

No. Aadhaar is never stored: if it turns up in an upload, it is detected and removed automatically.

Can we use our own name and web address?

Yes. White-label covers name, logo, colours, login images and email sender, and the system runs on the institute's own web address with HTTPS. Several institutions can share one system with data kept separate, or an institute can have dedicated servers.

What sign-in options are there?

Strong password rules, lockout after repeated failures and two-step sign-in with an authenticator app are live. Google Workspace and Microsoft 365 single sign-on, SAML, passkeys and mandatory two-step sign-in for admin staff are available to switch on.

Can each module be switched on separately?

Yes. Each module is switched on or off per institute. Releases run automated tests and are tried on a separate test copy with human approval first, and backups run nightly with a locked copy kept separately.

See Intelversity with your own programmes.

Book a guided demo on a sample institution with fictional data. You pick the time yourself from our email.

See it with your own programmesBook a demo