Safeguarding Policy

1. Commitment to Student Safety

Project Designer is committed to protecting the safety, welfare, and privacy of all students. We implement robust safeguarding measures in accordance with UK Keeping Children Safe in Education (KCSIE) and international best practices.

2. What We Protect Against

• Child sexual exploitation and abuse (CSEA)
• Grooming and inappropriate contact
• Cyberbullying and harassment
• Exposure to harmful content
• Data breaches and privacy violations
• Unauthorized access to student data

3. Platform Safeguards

3.1 Access Control

• Students may sign in, but access to class projects and learning content requires teacher enrolment
• Schools must decide the lawful basis, age-appropriate notice and any consent or authorisation required for their students
• Role-based access prevents student accounts from using teacher and administrative functions
• Authorised teachers can review submissions and progress for students within their permitted scope

3.2 Privacy Protection

• Student work is restricted to the student and authorised school staff
• Class roster email addresses are not delivered to student clients
• School-scoped access rules are applied to student records and staff access
• There is no student-to-student direct messaging feature

3.3 Content Controls

• Student submissions are not published to a public gallery
• Authorised teachers can review student submissions within their school scope
• Schools must apply their own safeguarding review and escalation procedures
• Concerns can be reported to the contact listed below

3.4 Communication Control

• Students cannot send direct private messages through Project Designer
• The current product does not provide student chat or conversation channels
• Student collaboration outside the platform remains subject to the school's own systems and policies

3.5 File Upload Safety

• Schools should upload only files needed for the educational purpose
• Users must not upload executable code, malware or unlawful content
• Upload limits and storage protections are governed by the active platform configuration
• Project Designer does not currently claim independent antivirus or explicit-image scanning

4. Teacher & School Responsibilities

Schools and teachers using Project Designer must:

• Determine and document the lawful basis and any consent or authorisation required for student use
• Provide age-appropriate privacy information and acceptable-use rules
• Manage enrolment and review student submissions within the school's safeguarding framework
• Report concerns to the school's designated safeguarding lead and authorities where required
• Assess applicable education, privacy and child-protection requirements in each jurisdiction
• Train staff on the school's process for safe platform use

5. Audit Logs & Monitoring

Teachers can access student submissions, progress and assessment records where their role and school scope permit. Project Designer does not currently claim a complete log of every login, read, download or interaction. Schools should not rely on the product as their sole safeguarding-monitoring or evidential logging system.

6. Reporting Safeguarding Concerns

If you suspect a safeguarding issue:

• Students: Tell a trusted teacher or school safeguarding lead
• Teachers: Report to your school's safeguarding team and/or local authorities
• Project Designer: Email safeguarding@projectdesigner.app with details

Reports are triaged promptly according to severity. Immediate danger or suspected abuse should be reported through the school's emergency and safeguarding channels rather than relying only on email to Project Designer.

7. Data Retention & Deletion

• Active Students: Data retained during enrollment
• Former Students: Retention follows the school's documented instructions and applicable legal requirements
• Deletion Requests: Processed after verification, subject to legal restrictions and the agreed DPA
• Backups: Residual copies expire under the hosting provider's documented recovery lifecycle

8. Third-Party Integrations

Where a school enables an optional third-party integration, it must review the provider, scopes, data flows, age requirements and contractual safeguards before student use. Integrations not listed in the current sub-processor or integration schedule should not be assumed to be active.

9. Safeguarding Training

Project Designer recommends schools provide:

• Annual safeguarding refresher training for all staff
• Age-appropriate online safety education for students
• Parent information sessions on platform safety features

10. Breach of Safeguarding Policy

Any adult who violates safeguarding standards may face:

• Account suspension
• Termination from the platform
• Reporting to local safeguarding authorities and law enforcement

11. Contact & Escalation

Safeguarding Officer: safeguarding@projectdesigner.app

Legal & Compliance: legal@projectdesigner.app

For emergencies: Contact local police or child protective services immediately.