Privacy Policy

Last Updated: October 3, 2026

SRM VERSE is designed with student privacy as our top priority. We operate strictly as an on-demand proxy bridge for your official SRM Academia portal.

Database Storage Transparency

Clear distinction of what is stored vs never stored

Never Stored in Database
  • Raw or plaintext SRM passwords (Academia or Student Portal)
  • Biometric data (Touch ID / Face ID stays on device)
  • Attendance records & academic history
  • Internal and semester marks
  • SRM Academia login session tokens
  • Your SRM VERSE Student Portal sync token (only its SHA-256 fingerprint)
  • Timetable & course schedules
  • Phone numbers & personal contacts
Only Stored in Database
  • Account Name & Email
  • Passkey Public Credentials (AES-256-GCM encrypted for biometric login)
  • User Interface Theme & Color Preferences
  • Community Feed posts, questions & comments
  • Student Portal NetID, password & session (opt-in only, AES-256-GCM encrypted, auto-deleted after 7, 15 or 30 days)

1.Information We Collect

SRM VERSE collects only the information necessary to provide you with a seamless academic experience. When you log in, we use your SRM Academia credentials to authenticate your session directly with the official SRM servers. We never store your Academia password. If you choose to use Student Portal sync (section 6), we store your Student Portal NetID and password in encrypted form for the number of days you select, and never in readable form.

2.How We Use Your Information

The information collected is used solely for the purpose of displaying your academic data in a user-friendly interface. We act as an on-demand bridge between you and the SRM Academia portal, presenting the same data in a modern format. We do not sell, trade, or rent your personal information to any third parties. Your data is never used for advertising or marketing purposes.

3.Data Security

We employ industry-standard security measures to protect your data during transmission. All communications between your browser and our servers are encrypted using HTTPS/TLS protocols. Session tokens are handled securely in memory and are never exposed to unauthorized parties.

4.Data Retention & Database Storage

We strictly do not store your attendance, marks, timetable, phone numbers, or academic records in our database. All academic data is fetched in real-time on-demand from the official SRM portal and discarded once your request completes. The only data stored in our database is your account registration details (Name and Email), user UI preferences, interactive Community Feed posts, encrypted passkey credentials if you opt in to biometric login, and, only if you opt in to Student Portal sync, your encrypted Student Portal credentials and session for the period you choose (see section 6).

5.Passkey & Biometric Authentication Security

When you register a Passkey for biometric login (Touch ID, Face ID, Windows Hello, or security keys), SRM VERSE utilizes the modern W3C WebAuthn / FIDO2 cryptographic standard. Your biometric data is processed entirely within your device's secure hardware enclave and is never transmitted to or stored on our servers. To enable seamless re-authentication with university systems, authentication payloads are encrypted using military-grade AES-256-GCM encryption with unique initialization vectors (IV) and authentication tags before being stored in the database. You have full autonomy to inspect or permanently delete your registered passkeys at any time from your Security Settings.

6.Student Portal Sync & Credential Encryption

If SRM Academia cannot load your attendance or marks, you can choose to log in with your SRM Student Portal NetID and password. This is optional, and we only ask when Academia is unavailable. You also choose how long to stay logged in: 7, 15 or 30 days.

What we store, and why

  • Your NetID and password, encrypted together. We use them only to log in to the Student Portal for you again when SRM ends its session, so you are not asked to log in every day.
  • The Student Portal session ID issued by SRM, also encrypted.
  • A SHA-256 fingerprint of your SRM VERSE sync token, never the token itself. It lets us confirm a request uses the exact token we issued to you.
  • Your student ID number and the expiry date, in readable form, so we know which records to delete and when.

Attendance and marks fetched this way are never stored. They are loaded fresh from SRM on every request.

How it is encrypted

  • AES-256-GCM with a 256-bit key. GCM also detects any tampering: altered data fails to decrypt instead of producing a wrong value.
  • A new random IV for every value, so encrypting the same password twice gives two completely different results.
  • Each value is locked to its own record. Encrypted data copied to another student's record cannot be decrypted.
  • The key is kept apart from the database, in the server's secret configuration. A copy of the database alone cannot reveal any password.
  • Never shown or logged. Your password is never returned by any API, written to logs, or shared with anyone.

Example: what our database actually holds

Suppose you log in with the password MyPass@123 and choose 30 days. The stored record looks like this (illustrative values):

{
  "_id": 679812,
  "credentials": {
    "keyId": "v1",
    "iv":   "q3Xk9P2mVt7Lr0Ab",
    "tag":  "Zr8sXo1Kp3VbQw7eLmN2aA==",
    "data": "8kJx0pQ2vT9wYc4LmZs1Rf6HdA3uBn7Ke5GiOq=="
  },
  "expiresAt": "2026-11-02T06:56:02Z"
}
  • _id is your student ID, and expiresAt is when the record deletes itself.
  • data is your NetID and password after encryption. iv is the random value used for this one encryption, tag is the tamper-detection code, and keyId names the key, so keys can be replaced over time.
  • Neither MyPass@123 nor your NetID appears anywhere in the record. Without the server's key, data is meaningless.

When it is deleted

  • Automatically, when the 7, 15 or 30 days you chose run out.
  • Immediately when you tap “Logout SP” or log out of SRM VERSE. This removes your credentials and every Student Portal session for your account.
  • Immediately if SRM rejects the stored password, for example after you change it.

Why encrypted and not hashed? A hash cannot be reversed, which is ideal for passwords we only need to check. To log in to SRM on your behalf, our server must be able to recover the password, so it is encrypted with a key that only the server holds. If you prefer not to have it stored at all, simply do not use Student Portal sync.

7.Third-Party Services & Analytics

SRM VERSE interacts with the official SRM Academia portal and, if you use Student Portal sync, the official SRM Student Portal to fetch your academic information. We use privacy-compliant Google Analytics solely to understand website traffic, monitor performance, and improve user experience. We do not use third-party advertising networks, and your personal academic records are never tracked or shared with external parties.

8.Your Rights

You have the right to access, correct, or delete any personal data associated with your account. You may revoke passkeys, remove your Student Portal credentials instantly with “Logout SP”, or choose to stop using the service at any time. If you have any questions or concerns about your data privacy, please reach out to us via email at admin@srminsider.in.

9.Changes to This Policy

We may update this privacy policy from time to time. Any changes will be reflected on this page with an updated revision date. We encourage you to review this policy periodically to stay informed about how we protect your information.