1. Who this notice covers
Safetycodx is the name used for this school safety project. This notice covers this public website, demo requests and the partner application and workspace where a Django deployment makes them available. The interactive school operations screens are demonstrations with fictional records; they are not a live student service. A school deployment needs its own school agreement, documented roles and a notice for students, guardians and staff before real school records are processed.
For public enquiries and partner applications, the organization operating Safetycodx determines the purposes of processing. In a future school deployment, the school may determine the purposes of student processing and Safetycodx may act on its documented instructions, subject to the actual agreement and law. The legal entity, registered address and privacy contact must be confirmed before accepting real personal data in production.
2. Information and sources
A Django demo request can collect your name, role, school, school type, work email, phone, location, approximate student and bus counts, selected interests, message, submission time and a possible partner referral candidate. A Django partner application can collect contact and professional details, territory, experience, school network, photograph, optional CV or business profile, declarations, application history and account activity. Staff may record school lead and correspondence details. Authentication, security and server logs can contain IP address, time, browser information and account events.
Information may come from you, an authorized school or organization representative, a partner introducing a school, or an authorized staff member. We ask you not to put a child's name, health details, live location or other sensitive student data into public forms. The public website is not intended for direct use by children.
3. Why we use information
- Respond to requested demonstrations and manage a possible school relationship, including deduplication and reviewing partner introductions.
- Assess partner applications, administer approved accounts and maintain records of actions and correspondence.
- Secure the service, investigate misuse and meet applicable legal obligations.
Depending on the activity and applicable law, the grounds may be steps requested before a contract, performance of a contract, a legitimate interest in responding to business enquiries and securing the service, legal obligation, or consent where specifically required. Form consent to contact is for the stated enquiry or application; it is not consent to unrelated marketing or to process children's school records. You may withdraw consent where processing relies on it.
4. Children and school data
Real attendance, identification, transport, camera or safety data must only be introduced after a school-specific agreement, privacy and risk assessment, access controls, lawful basis, guardian information and any required child or guardian authorization have been established. Schools and authorized personnel must verify identity and relationships before access. A missing device signal must not automatically become an absence or an emergency conclusion. The current public prototype does not connect to live readers, buses or cameras and does not send real parent alerts.
6. Retention and security
In Django, submitted enquiries, applications and related review records are stored until deleted under an operational retention schedule; the present implementation does not automatically erase them after a fixed period. The final schedule must reflect the purpose, any contract, legal obligations and disputes, with deletion or de-identification when no longer needed. The static demonstration stores some entered prototype data in this browser's local storage, where it may remain until you clear site data. Do not enter real personal or student data in the static demo.
The Django foundation includes account permissions, CSRF protection and private application file storage, but no system can promise absolute security. Production hosting, access review, backups, incident procedures and vendor controls require separate verification. If a personal-data breach occurs, applicable notification duties will be assessed under the relevant law.
8. Your choices and rights
Subject to applicable law, you may ask for access, correction, deletion, restriction, objection or portability, withdraw consent, and challenge solely automated decisions where relevant. We may need to verify your identity and may be unable to disclose another person's data. To request help with a public enquiry or partner record, use the contact page and mark the request “Privacy”. Do not include identity documents or child records in a public message. If your request concerns a school record, contact the school first; we will route a request to the appropriate controller when possible. You can complain to the Nigeria Data Protection Commission or a competent local authority.
9. Changes and jurisdiction
This notice reflects the described prototype and Django foundation as of 28 October 2026. We will publish a new date and explain material changes when the service or processing changes. Rights under laws that apply to you are not removed by this notice. Additional regional notices and operational controls may be required before serving people outside Nigeria.