JSiMS Online School Management System

This policy applies to the JSiMS Online School Management System Android app (the "App"), built and published by Soft Solutions. The App is provided to a school as a tool for running its own records — the school itself decides which students, parents, and staff are given accounts, and remains responsible for that data under its own admissions and record-keeping policies.

If you're a parent, student, or staff member using the App, your account and the records visible to you were set up by your school's administration, not created by signing up on an open registration page.

The table below is the short version — each row is explained further in the sections that follow.

Account information

To sign in, the App sends your username and password to your school's JSiMS server for verification. We don't store your password on the device — only an encrypted sign-in token is kept locally, so you can stay signed in or switch quickly between saved accounts.

School records

Depending on your role, the App displays records your school has already entered into its JSiMS system: admission and class details, daily attendance, exam results, lesson plans, homework, timetables, and date sheets. The App reads and updates these records on the school's server — it doesn't hold a separate copy of its own.

Fee and payroll records

For campus administrators, the App can show and manage fee challans, payments, discounts, and — separately — staff attendance and payroll figures. These screens are restricted to authorised admin accounts.

Photographs

Student and staff profile photos already stored on your school's server are shown in the App. Where the App lets you add or replace a photo, it opens your device's own camera or gallery app to pick one — JSiMS does not access your camera in the background.

JSiMS is built so that a campus admin, teacher, or student only ever sees the records their role and campus are entitled to:

• Campus admins see records for their own campus — attendance, fees, payroll, results — not other campuses run on the same JSiMS installation.
• Teachers see the classes and courses they're assigned to teach, and can mark attendance, lesson progress, and results for those classes.
• Students see their own attendance, results, fee status, and timetable — not another student's records.

This separation is enforced on the server, not just hidden in the App's screens.

If you turn on fingerprint or face unlock for a saved account, that check happens entirely inside your device's own operating system. JSiMS never receives, stores, or transmits your fingerprint or facial data — the App is only ever told "matched" or "not matched," the same way any app using your phone's screen lock would be. You can turn this off at any time from the sign-in screen.

• To sign you in and keep your session secure.
• To show and let you update the school records your role has access to — attendance, results, fees, payroll, and similar.
• To let staff reach a parent or guardian on WhatsApp, where a mobile number is already on file — see the next section for exactly how this works.
• To send in-app notifications your school has issued (for example, an SMS/alert your school sends through its own system).

We do not use your data to build advertising profiles, and the App carries no advertising or analytics software development kit of any kind.

School data in JSiMS travels between the App and your school's own JSiMS server — nowhere else. We do not sell data, and we do not share it with advertisers, data brokers, or analytics companies, because none are built into the App.

WhatsApp

Where a guardian's mobile number is on file, some screens offer a shortcut that opens WhatsApp with a chat pre-addressed to that number. JSiMS doesn't send anything on its own — it hands off to the WhatsApp app already on the device, and the staff member decides whether to send a message from their own WhatsApp account. Anything sent that way is then governed by WhatsApp's own privacy policy, not this one.

• All traffic between the App and the server is encrypted (HTTPS) — the App is built to refuse plain, unencrypted connections outright.
• Sign-in uses short-lived security tokens rather than repeatedly sending your password.
• Anything cached on your device for quick sign-in is stored in Android's encrypted keystore-backed storage, not as plain text.
• School records themselves live on your school's own server infrastructure, administered by or for your school.

Academic, attendance, fee, and payroll records are retained on your school's server for as long as your school's own record-keeping practices and any applicable education regulations require — this policy doesn't set that timeline, your school does. Signing out of the App, or uninstalling it, removes the encrypted sign-in token and any saved-account shortcuts from that device.

Because JSiMS is used inside a school's own relationship with its enrolled students, student accounts and records are created and managed by the school, not by a child signing up independently. The school acts as the responsible party for that data and for obtaining any consent required under local law. If you're a parent or guardian with a question or concern about your child's records, please raise it with your school's administration first — they can also route it to Soft Solutions if needed.

• Access or correction: request it through your school's administration, since they own the underlying records.
• Biometric unlock: turn on or off any time from the sign-in screen.
• Saved accounts: remove a saved account from the device to clear its locally stored sign-in token.
• Sign out: clears your session from that device immediately.

If this policy changes, we'll update the effective date at the top of this page. Continuing to use the App after a change takes effect means you accept the updated policy.

Questions about this policy, or about JSiMS generally, can be sent to Soft Solutions at the address below.