Student and family data, treated like it matters
Karkaye handles attendance, fees, and contact details for real students and families — here’s how that’s protected.
Encrypted in transit
Every connection — web, mobile, and API — is encrypted over HTTPS/TLS. There’s no unencrypted path to your data.
Isolated per institute
Each institute’s data lives in its own isolated schema — not just a shared table with a filter. One institute can never query another’s data.
Modern authentication
Password login with industry-standard hashing, plus one-time-code login over email or SMS — short-lived access tokens and secure refresh.
Rate limiting
Login, signup, and OTP requests are rate-limited per account and per IP to blunt brute-force and abuse attempts.
Audit logging
Sensitive actions — payments, student changes, permission changes — are logged with who did what and when.
Signed integrations & protected secrets
Payment and messaging webhooks are signature-verified, connector credentials remain server-side, and readiness responses never return access tokens or secrets.
Role-based access
Every account only ever sees data for its role and institute — students and guardians can’t see other families’ records.
Service health visibility
Health checks surface API, database, and Redis readiness, while platform-only operations keep service checks separate from institute data.
Owner trust console
Review the institute access register, member roles, account status, site scope, recent authentication activity, and failed-sign-in totals in one owner-only view.
Emergency session revocation
Owners can revoke active refresh sessions for any institute member when a device, credential, or account relationship needs immediate containment.
Versioned data agreements
Owner designation and Data Processing Agreement acceptance are recorded with the accepted version and timestamp; enrolment is blocked when required acceptance is missing.
Separate platform operations
Platform administration has its own authorization boundary for service health, institute lifecycle, plan tiers, orders, coupons, announcements, and platform audit review.
How we think about it
Principles that shape every decision on this side of the product.
Access is scoped as narrowly as possible by default — a teacher can’t see another batch’s fee records, and a parent can’t see another family’s child, by construction, not by convention.
Backups run on a schedule with point-in-time recovery, and infrastructure health is actively monitored with alerting — catch problems before they become incidents.
Encryption, isolation, rate limiting, audit logs, and monitoring work together — so one gap doesn’t become the whole story.
Questions about security?
If you need more detail for your institute’s due diligence, get in touch — we’re glad to walk through it.