Security
Built for the data universities are trusted with
A summary for IT, procurement and data-protection teams. For a security questionnaire or our data processing addendum, write to animwebtechnologies@gmail.com.
Data isolation
- Every institution has its own MongoDB database; no query can span institutions.
- Paid institutions can run on a dedicated deployment on their own domain and database cluster.
- Demo workspaces live in separate databases and are deleted 30 days after they end unless converted.
Identity & access
- Passwords people set are hashed with bcrypt and checked against common and breached passwords (k-anonymity lookup - the password never leaves the server). Temporary passwords must be changed at first sign-in.
- Two-factor authentication with any authenticator app (TOTP), single-use codes and recovery codes; recommended for every administrator.
- Short-lived (15-minute) access tokens; rotating refresh tokens in an httpOnly, Secure cookie. Reuse of a rotated token revokes every session.
- Accounts lock temporarily after repeated failed sign-ins, and a human-verification challenge appears after repeated failures; responses are timing-safe so valid logins cannot be enumerated.
- Self-service password reset by one-time email link (30 minutes); a reset or password change signs out every other device. Users can see and sign out their signed-in devices.
- Optional Sign in with Google: Google’s signed ID token is verified on the server (signature, audience, expiry, single-use nonce, verified email), never creates accounts, is bound to one Google account per user, and still requires two-factor where it is on.
- Session renewal requires an app-only request header, so other websites cannot trigger it (CSRF protection).
- Twenty-one roles plus institution-created offices, each with scoped data access (section, year, department, cluster, institution, campus desk, office); marks only for the Examinations department and placements only for the placement cell.
Attendance integrity
- Join codes derived with HMAC-SHA256 per session; rotating windows of 10-120 seconds.
- Location updates throughout the class, signed with per-student HMAC keys and strictly increasing nonces (replay-proof); positions from stale GPS fixes never count as inside.
- Classroom and campus location checks are performed on the server; the classroom and campus centres are never sent to student devices. Weak indoor GPS is treated as uncertain, never as leaving.
- Room sound check for classrooms stacked on different floors: a rotating near-ultrasonic signal that floors block and voice calls cannot relay.
- Fake-GPS heuristics flag frozen, unrealistically precise fixes and impossible jumps to the teacher.
- One registered phone per student, identified by a key created when the app is installed plus device signals, hashed with SHA-256 and registered on the first attendance. Students who reinstall the app or change phones ask their mentor or admin to reset it. Optional on-device face verification.
Biometric & personal data
- Face templates (128 numbers) are computed on the student’s phone; photos and video are never uploaded.
- Templates are stored encrypted with AES-256-GCM using a per-deployment key.
- Location is processed only while a student has a live class open on Mark Attendance or is checked in to it.
- The room sound check analyses audio on the phone; nothing is recorded or uploaded, and the microphone is released within seconds.
- Workspace exports are encrypted with AES-256-GCM under a one-time passphrase.
Application security
- Strict Content-Security-Policy, HSTS, frame denial and modern security headers on every page.
- Input validation on every endpoint, NoSQL-injection and XSS sanitisation, request size limits.
- Per-user and per-IP rate limiting; bot protection (Cloudflare Turnstile) after repeated failed sign-ins.
- We never handle card or bank credentials - fees are paid by bank transfer against a GST invoice.
- Audit log of finalised attendance, every per-student change (old and new status, with the reason), leave approvals, user changes and configuration changes.
Infrastructure
- Web apps served from Cloudflare’s global network; APIs run on Railway, a managed cloud platform, with TLS everywhere.
- Databases on MongoDB Atlas, encrypted at rest, with continuous backups on production clusters.
- Secrets are held in the hosting providers’ secret stores and never committed to source control.
- No default passwords, demo accounts or sample data ship with Presence. A new deployment is created once, on a setup screen protected by a one-time setup key, which then closes for good.
- This website’s accounts (Sign in with Google for enquiries) live in a separate Cloudflare database and never give access to Presence or its data. Website sessions are http-only cookies, only a hash of each is stored, and visitors can sign out everywhere or delete their account themselves.
- Website forms are protected by Cloudflare Turnstile, checked by the form service before any message is accepted, plus per-address rate limits.
Responsible disclosure
Found a vulnerability? Email animwebtechnologies@gmail.com with details and steps to reproduce. Please do not access other institutions’ data or degrade the service while testing. We acknowledge reports within two business days. See also security.txt.