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
- 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
- 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
2.How We Use Your Information
3.Data Security
4.Data Retention & Database Storage
5.Passkey & Biometric Authentication Security
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"
}_idis your student ID, andexpiresAtis when the record deletes itself.datais your NetID and password after encryption.ivis the random value used for this one encryption,tagis the tamper-detection code, andkeyIdnames the key, so keys can be replaced over time.- Neither
MyPass@123nor your NetID appears anywhere in the record. Without the server's key,datais 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.