Before you write the email anyway.

Your institution. Under the DPDP Act you are the Data Fiduciary; we are the processor. We do not use your students' data for our own purposes — no cross-tenant benchmarking, no model training on it, no analytics on minors. You can export it, and if you ever leave, we help you take it with you.

Yes. Onboarding starts with a one-time import of your student, staff and fee-head data. For a mid-year migration we bring last year's results and ledgers across as read-only history, so a transcript from before the switch still verifies correctly.

The parent and student portal is built mobile-first for exactly this: it is server-rendered for a fast first paint on a mid-range Android phone, and works on a patchy connection rather than assuming fibre.

Most systems check a job title. NexusGrade checks a capability scoped to an actual appointment — so a Head of Department three years into a five-year professorship holds exactly what that appointment grants, and nothing more, and it lapses on its own when the appointment ends. See Security & compliance for the full model.

Cash, cheque and DD collection at the counter never depend on the payment gateway. Card and UPI payments queue and reconcile against Razorpay's settlement report once it is back — nothing is double-counted, because every entry is a signed row in an append-only ledger, not a balance anyone edits by hand.

No setup fee for a standard onboarding. Pricing is quoted against your student count and campus structure, not per staff or parent login — see Pricing, or write to us with your numbers.

Yes — that is a DPDP rights request, and it is a real workflow in the product (the Compliance module), not an email to a developer. Retention schedules and legal holds are respected automatically, so a request cannot accidentally destroy a record your institution is required to keep.