Your applicants' data, provably safe.
Isolation, authentication, payment integrity and data durability are built into the platform, not bolted on.
Every institute sees only its own data.
Multi-tenancy enforced in the data layer, not just the UI — no institute can reach another's applicants.
Role-based access
Capabilities gated by role — form design, applicant review and payment operations stay separated.
institute_id scoping on every query
Every query scoped by institute_id at the data layer — structural isolation, not a filter you can forget.
JWT with silent refresh
JWT with refresh tokens keeps sessions alive; concurrent 401s dedupe into one refresh — no token stampede.
Rate limiting + Turnstile
Auth endpoints rate-limited and fronted by Cloudflare Turnstile — blunts credential-stuffing and signup abuse.
Money is verified, snapshotted and reconciled.
A candidate who paid and got nothing is the worst failure — every layer here prevents it.
Razorpay signature verification
Every webhook is signature-verified — a payment status is accepted only when it provably came from the gateway.
Fee-breakdown snapshot per application
A JSON snapshot of the fee breakdown at payment — an immutable record of what was charged and why.
Payment loss-recovery reconciliation
Reconciliation recovers payments with dropped callbacks — a captured transaction is matched back to its application.
Encrypted in transit, durable at rest.
TLS everywhere, encrypted credentials, resilient storage and daily backups — retention archives, never deletes.
HTTPS everywhere
HTTPS via Traefik with Let's Encrypt wildcard certificates — every institute subdomain encrypted end to end.
Encrypted Eklavvya credentials
Connected Eklavvya exam-account credentials are stored encrypted, never in plain text.
iDrive E2 with local fallback
Documents stored in iDrive E2 (S3-compatible), with local-disk fallback — an upload never fails on a storage blip.
Archive, not delete
Records are archived, not hard-deleted — history stays for audits while the working console stays clean.
Daily live-DB backup with rotation
Automated daily live-DB backup with rotation — recovery points stay recent, storage stays bounded.
Optional Sentry error tracking
Enable Sentry to surface and triage runtime errors fast — shorter path from incident to fix.Configurable
The AI Counseling Suite can add DocuExprt verification for identity and fraud checks — extending these controls to submitted documents. See the Suite →
Role-based access, institute_id scoping, JWT auth, Razorpay verification, HTTPS, iDrive E2 storage, reconciliation and daily backups are native. DocuExprt verification is an optional add-on within the AI Counseling Suite.
Questions IT and compliance teams ask.
Is our applicant data secure on ePravesh?
Yes — isolation, authentication, payment integrity and durability are built into the platform rather than bolted on. Every institute's data is scoped by institute_id at the data layer, access is gated by role, sessions run on JWT, and traffic is HTTPS end to end. Uploaded documents live in iDrive E2 storage and the live database is backed up daily with rotation.
Can another institute see our applicants?
No. Multi-tenancy is enforced in the data layer, not just the UI — every query is scoped by institute_id, so isolation is structural rather than a filter someone could forget to apply. Each institute runs on its own branded subdomain, and there are no shared spreadsheets between tenants.
How do you know a payment is genuine?
Every Razorpay webhook is signature-verified, so a payment status is accepted only when it provably came from the gateway. At payment the engine also stores a JSON snapshot of the fee breakdown against the application — an immutable record of exactly what was charged and why, available whenever a charge is questioned later.
What happens if a candidate pays but the callback is lost?
Reconciliation recovers it. A captured transaction with a dropped callback is matched back to its application, so the candidate is not left having paid for nothing. This is treated as the worst possible failure on an admission portal, which is why recovery is a built-in layer rather than a manual support process.
Where are documents stored, and what about backups?
Uploads go to iDrive E2, an S3-compatible store, with local-disk fallback so an upload never fails on a storage blip. Traffic is encrypted over HTTPS with Let's Encrypt wildcard certificates on every institute subdomain, and connected Eklavvya exam credentials are stored encrypted. The live database is backed up daily with rotation, and records are archived rather than hard-deleted.
How do you stop credential stuffing and signup abuse?
Auth endpoints are rate-limited and fronted by Cloudflare Turnstile, which blunts credential-stuffing and automated signup abuse. Sessions use JWT with refresh tokens, and concurrent 401s dedupe into a single refresh so there is no token stampede. Access to form design, applicant review and payment operations stays separated by role.
Walk through the security model with our team.
We'll show isolation, JWT sessions, payment reconciliation and backups on a live portal — and where DocuExprt verification fits.