A dedicated database per institution
Every institution runs on its own database, not a shared one with a filter applied. A query written for one institution has no path to another's records, because the data is not in the same place. This is the strongest separation guarantee on this page.
Role-based access control
Access is granted per role — administrator, teacher, accounts, library, transport, hostel, security and more — and each role carries an explicit permission set. A teacher cannot open fee collection, and an accounts user cannot alter examination marks, unless you grant it.
Audit trail on record changes
Changes to student, staff, fee, examination and configuration records are recorded with the user who made them and the values before and after. When someone asks who changed a mark or reversed a receipt, the answer is in the system rather than in memory.
Support access is logged
When our team accesses your workspace to help with a problem, the operator, the account reached, the action, the IP address and the browser are all written to a log. Support access is not invisible to you.
Payments never touch our servers
Online fee payments run through your chosen gateway — BillDesk, Easebuzz, NTT Data or PayPhi. Card and bank credentials are entered on the gateway, not in EduTask. There is no card number field anywhere in our database.
Session and API tokens expire
Mobile and API sessions carry an expiry set at login rather than living indefinitely. Public forms are protected by reCAPTCHA, which is scored rather than a checkbox, so automated submissions are rejected before they reach a person.