This privacy policy describes how information is handled in the local admin portal (browser-based) used for student and fee management.
1. Scope & Purpose
This portal is a local, browser-based administrative tool. All data (student records, sibling details, fee slips) is stored locally in the user's browser localStorage.
There is no default remote transmission of data to our servers unless the user explicitly exports or shares data from their browser.
Purpose of data processing: to manage student enrollment, sibling relationships, fee calculations and maintain records of payments for administrative use.
Only authorized administrative staff should use this portal; visitors should not change settings or data without permission.
Manage your local storage by creating your account in our Local Storage Manager. It is safe to use and created by me . View my Repository in Github for more detail .
Settings: Admin password (if changed locally) stored on the same device/localStorage as plain text by design (per admin request).
Usage metadata: No analytics or telemetry is implemented by default.
3. How Data Is Used
To display and manage registered students and their sibling relationships.
To calculate monthly totals and support fee collection and record keeping.
To allow authorized staff to view past payments and balances when resolving queries.
4. Storage Location & Security Considerations
All data is stored in the browser's localStorage on the device where the portal is used. This is client-side only.
LocalStorage is accessible to anyone with access to the device or user profile. Do not store highly sensitive personal data in this demo portal.
Administrators should back up data (export or copy) before clearing browser storage or changing devices.
If a device is lost, stolen or a browser profile is compromised, data stored in localStorage may be exposed; administrators must take appropriate steps (change local passwords, secure device, restore from backup when possible).
5. Admin Password & Requests
The portal includes a settings area protected by a hashed admin password embedded in the application. Only a person with the correct password can change settings.
If a local admin password has been set on the device, that local value must be used for authentication on that device.
If you do not have the hash/password, use Settings → Request Admin Hash. That action opens your email client prefilled to send a manual request to akshatpsd2005@gmail.com. The portal does not send requests automatically.