School data should stay controlled and purposeful
EduNizam is designed around role-based access, local-first operation and optional cloud services configured by the institution.
Local mode
When EduNizam is used without cloud mode, operational records can be stored in the browser on that device. Clearing browser storage can remove those local records, so institutions should use backups before relying on local mode for important records.
Cloud mode
When an institution enables cloud features, authenticated records are stored through the institution's configured Supabase project. Access is separated by account role and institution relationships. Some features, such as private school media, depend on protected cloud storage and signed access links.
Accounts and school records
EduNizam may process account identifiers and school-managed records needed for features such as students, attendance, fees, results, admissions, communication, staff, documents and learning workflows. Users should only enter information they are authorized to manage.
AI-assisted features
AI features are intended to use a server-side integration when configured. Secret API keys should never be placed in browser code. Institutions should avoid sending unnecessary personal or sensitive information to AI features.
Access, correction and deletion
For institution-managed cloud records, users should contact their institute administrator for appropriate access, correction or deletion requests. Local browser records can be managed on the device where they are stored.