School Class Management System
Privacy Policy
How the School Class Management System handles account, teacher, and learner information.
This draft describes the data types and integrations visible in the current application. The operator must verify the complete hosting, access, retention, and deletion practices before relying on it.
Information in the app
The app processes account details such as a teacher's name and email address, and information the teacher chooses to enter. Depending on the features used, that information can include school and class details; learner names, Learner Reference Numbers, sex, birth dates, addresses, guardian contact details and photos; attendance, grades, remarks, lesson plans, schedules, and report data.
Do not enter information that is not needed for your legitimate teaching work. In particular, use care with learner information and only enter it when you are authorized to do so.
How information is used
The app uses account information to authenticate teachers and associate their records with their account. Teacher-entered information is used to provide class management features, including attendance, grade calculations, lesson planning, reports, and exports.
The current codebase has no advertising or analytics SDK integration. This does not describe infrastructure-level logs or services enabled by the deployment operator.
Service providers and storage
The application connects to Supabase for authentication and database operations. Records are designed to be scoped to the signed-in teacher through database access policies. Student photos may be stored using Supabase Storage. The deployed hosting provider, storage region, backups, and operational access depend on the deployment configuration and must be confirmed by the operator.
The app may generate downloadable reports or files when a teacher requests an export. Review exported files before sharing or storing them elsewhere.
Sign-in providers
Email and password sign-in are supported. Google sign-in is available when enabled for the deployment. When used, Google and Supabase process the authentication information needed to complete sign-in under their respective policies.
Access, security, and sharing
The app is designed so each teacher can access records associated with their account. No security measure can guarantee that information is never exposed. The operator must document who can administer the infrastructure and how access, backups, incidents, and data requests are handled.
The codebase contains no advertising integration. Information entered into the app should not be used to target advertisements. Teachers remain responsible for handling learner records in accordance with their school's rules and applicable requirements.
Retention and deletion
The current application does not provide a self-service account deletion workflow. This draft does not establish a retention period or guarantee deletion. The operator must publish how users can make access, correction, or deletion requests, how those requests are handled, and how long records and backups are retained.
Children's information
This is a teacher-facing tool that may contain information about school-age learners. Learners should not be invited to create accounts or use the teacher sign-in flow. The operator and teachers must determine and follow the applicable school, guardian, and privacy requirements before entering learner information.
Changes and contact
The operator should review and update this policy when the app, providers, or data practices change, and publish a valid contact address for privacy questions and requests. No operator contact address is configured in this repository.