Last Updated: January 31, 2026
App Name: SchoolOS
Developer: Siji Technologies Pvt Ltd
This Privacy Policy explains how SchoolOS ("we," "our," or "us") collects, uses, stores, and protects personal information when you use our multi-school management platform (the "App" or "Service"). SchoolOS is a comprehensive school administration system that includes modules for attendance management, fee tracking, homework distribution, messaging, circulars/announcements, and profile management. By using SchoolOS, you consent to the practices described in this policy.
SchoolOS serves educational institutions and processes data for school administrators, teachers, and parents/guardians. The platform stores student information (including children under 13 years of age or under 16 in certain regions); however, students do not directly access or log in to the SchoolOS application. Student login credentials are provided exclusively to parents/guardians to access their child's academic and attendance information.
All student data is collected and managed by authorized school administrators on behalf of the educational institution.
Parents/guardians access their child's information through parent-assigned credentials; students themselves do not interact directly with the application.
Schools are responsible for obtaining all necessary consents from parents/guardians before collecting and processing student data.
Parents/guardians may contact their school administrator to review, correct, or request deletion of their child's information.
SchoolOS complies with the Children's Online Privacy Protection Act (COPPA) principles by ensuring that children's data is processed only under school and parental authority without direct child interaction with the service.
We collect information necessary to provide school management services. Collection practices vary based on user role (Admin, Teacher, Parent) and enabled school features.
Note: Face recognition attendance is an optional feature that schools may enable at their discretion for staff (teachers/administrators). This feature is not used for students.
When you register your face for attendance, the System captures a facial image.
Crucially, we do not store your raw facial image. Instead, the System instantly converts it into a unique mathematical representation called a "face encoding" or "template." This template is a string of numbers that cannot be reverse-engineered to recreate your actual photo.
This face encoding is stored securely in our database and is used solely for verifying your identity during check-in and check-out.
Users may opt out of biometric attendance and use alternative methods (PIN/password) where available.
Note: Location verification for attendance is an optional feature that schools may enable for staff attendance validation. This feature is not used for student tracking.
To verify physical presence on school premises during attendance submission, the System may request access to your device's precise location (GPS).
This data includes latitude and longitude coordinates and is used only to calculate distance from the officially registered school location.
Location access is requested only at the moment of attendance submission and is not continuously tracked.
Users may decline location access and use alternative attendance methods where available.
For administrators and teachers: Name, staff ID, role, school affiliation, contact information, subject/class assignments
For parents/guardians: Name, relationship to student, contact information, linked student account(s)
**Student information **(stored but not directly accessed by students) Name, class/grade, roll number, admission details, academic records, attendance history
Optional: Profile photos for staff and parents (stored only if uploaded)
Attendance records: Daily status (Present/Absent/Late/Half-day/Holiday) for staff and students, timestamps, verification method used (face/PIN/manual)
Fee management: Fee structures, payment history, pending amounts, payment modes (Cash/Online/Cheque/Card)
Homework: Assignment details, submission status, teacher remarks, grades/marks
Communication: Internal messages between authorized users (admin ↔ teacher, teacher ↔ parent), circulars/announcements with attachments
System activity: Login timestamps, module access logs (for security and troubleshooting)
IP address (for security and session management)
Browser type, operating system, and device information (for responsive interface rendering)
Session cookies and authentication tokens
We use collected information strictly for educational administration purposes:
To verify staff identity securely using face recognition or backup PIN (where enabled by school)
To validate staff physical presence on school premises during attendance (where location feature enabled)
To generate and manage attendance records for administrative and payroll purposes
To process fee payments and maintain financial records
To distribute and track homework assignments
To enable secure communication between authorized users within the same school ecosystem (administrators, teachers, and parents)
To allow parents/guardians to view their child's academic progress, attendance, and school communications through parent-access accounts
To maintain complete data isolation between schools in our multi-tenant architecture
To ensure system security, prevent unauthorized access, and detect fraudulent activity
To comply with legal and regulatory obligations related to educational record-keeping
We will never:
Sell, rent, or share your biometric data or personal information with third parties for marketing or advertising purposes
Allow students to directly log in to or interact with the application
Use student data for behavioral advertising or profiling
Collect data beyond what is necessary for school administration functions
SchoolOS employs a secure multi-tenant architecture where each school's data is completely isolated. Users from one school cannot access data from another school, even though they share the same application infrastructure.
Face Encodings: Stored in encrypted format as mathematical templates (not photographs); cannot be reverse-engineered to recreate images
All Data: Stored on secure servers with industry-standard protections including firewalls, access controls, and TLS 1.2+ encryption for data in transit
Passwords: Hashed using bcrypt (cost factor 10)
Database Access: Parameterized queries (PDO) to prevent SQL injection
Session Security: Token-based authentication with expiration and regeneration
Personal data is retained only as long as required by school policy and applicable laws
Upon account termination, data is securely deleted or anonymized within 30 days unless legal retention requirements apply
Biometric templates are deleted immediately upon user request or when biometric attendance feature is disabled for that user
SchoolOS is a self-contained platform. We do not integrate third-party advertising SDKs or analytics services that collect personal information for advertising purposes. We may use trusted hosting providers who access data only for infrastructure purposes under strict confidentiality agreements.
Depending on your location and role, you may have the following rights:
Access: Request a copy of personal information we hold about you (staff/parents) or your child (parents)
Correction: Request correction of inaccurate information
Deletion: Request deletion of your face encoding and personal data (subject to legal retention requirements)
Withdrawal of Consent: Withdraw consent for biometric data use at any time; you will then use alternative attendance methods (PIN/manual) if available
Opt-out of Location: Decline location access during attendance submission and use alternative verification methods
To exercise these rights: Contact your school administrator. Parents may contact the school directly regarding their child's data. Schools may contact us at help@juria.in for institutional data management requests.
Parents/guardians have full control over access to their child's information:
Review all student information through the parent portal using parent-assigned credentials
Request correction of inaccurate student information
Request deletion of their child's account and data by contacting the school administrator
Refuse further collection or use of their child's information (school may determine implications for enrollment)
We may update this Privacy Policy periodically. Material changes will be:
Posted on this page with an updated "Last Updated" date
Communicated to school administrators via email
Notified to users upon next login to the App
We encourage regular review of this policy. Continued use of SchoolOS after changes constitutes acceptance of the updated policy.
This App complies with Google Play Developer Policies:
Biometric data collection is optional, disclosed transparently, used solely for staff attendance verification within the app, and never collected from children
Location data collection is optional, limited to staff attendance moments, not continuously tracked, and never used for student tracking
No personal data is sold to third parties
No ads or ad-based SDKs are included in the core application
Children's data is processed under school and parental authority without direct child interaction, with appropriate safeguards per COPPA principles
All data practices are disclosed in this policy as required by Google Play Families Policy and User Data policy
For privacy-related inquiries, data requests, or concerns:
Developer: Siji Technologies Pvt Ltd
Email: help@juria.in
Address: House No 132, Kadamoni Pather, Juria, Nagaon, Assam - 782124
School administrators should contact us directly for institutional requests. Parents should contact their child's school administrator regarding student data matters.