Pilot procurement summary · September 2026

BullyShield school procurement pack

A concise, honest starting point for safeguarding, data-protection, IT and procurement review. Subject to school review and contract; this page is not legal advice.

Apply for the pilot

At a glance

Supplier
Fire Horse Ltd, trading as BullyShield
Pilot price
£1,500 for one term
Annual licence
£5,000 per school; pilot fee credited
Current data boundary
Synthetic or pilot data only in the secure demonstration

1. Service and pilot scope

BullyShield is a school safeguarding reporting and case-management platform. The £1,500 Founding School Pilot covers one term, up to 1,000 students, unlimited authorised staff, guided setup and an agreed success review. The fee is credited towards the £5,000 annual licence if the school continues.

  • Student reporting route configured with the school
  • Protected case workflow for authorised safeguarding staff
  • Named ownership, actions, notes and audit history
  • No automated safeguarding decisions; professional judgement remains with the school

2. Roles and responsibilities

The final controller, processor and operational responsibilities are documented with each school before live use. The school remains responsible for its safeguarding policy, lawful basis, reporting notices, escalation decisions and authorised-user approval. BullyShield is responsible for operating the agreed service and controls.

  • Named school safeguarding and data-protection contacts
  • Approved staff roles and least-privilege access
  • Agreed reporting, escalation and support process
  • Data-processing terms completed before live student data

3. Data flow and information boundaries

A report moves from the school-approved reporting route into the school-scoped workspace, where authorised staff review it, record actions and manage follow-up. Demonstrations use synthetic or pilot data. Live student information is not introduced until production assurance and the school's review are complete.

  • Marketing website does not hold safeguarding case records
  • Pilot enquiries are kept separate from safeguarding records
  • Schools agree what evidence can be uploaded and who may access it
  • No safeguarding information should be submitted through the public pilot form

4. Access and security controls

The product is designed around school-scoped workspaces, role-based permissions, encrypted connections and accountable activity records. Identity configuration, sensitive storage, monitoring and evidence-access controls are reviewed as a production gate for each live pilot.

  • Named users and role-based access
  • School separation and least-privilege design
  • Privacy-aware audit history for important activity
  • Human review of all safeguarding decisions

5. Retention, deletion and subject rights

Retention periods are not imposed by the demonstration. Before live use, BullyShield and the school document retention, deletion, export, correction and subject-rights handling in line with the school's policy and legal obligations.

  • School-specific retention schedule agreed before launch
  • Offboarding, export and deletion process documented
  • Evidence handling and access responsibilities recorded
  • Requests routed through named data-protection contacts

6. Hosting and subprocessors

The public website is hosted on Vercel and does not contain safeguarding case records. The current secure demonstration uses ChatGPT Sites/OpenAI with synthetic or pilot data only. Resend is used for commercial enquiry and transactional email, not for safeguarding case records. The production processor register and hosting design will be finalised and shared before any live student data is used.

  • Vercel: public website hosting
  • OpenAI/ChatGPT Sites: current secure demonstration, synthetic or pilot data only
  • Resend: pilot-application and transactional email
  • Production processor list subject to school review before live use

7. Incident response, continuity and support

Named incident contacts, notification expectations, backup and recovery arrangements, service levels and support routes are agreed before live operation. These are production readiness gates and are not presented as completed guarantees at demonstration stage.

  • Named security and safeguarding escalation contacts
  • School notification and incident-coordination procedure
  • Backup and recovery review before live use
  • Final support hours and service levels included in the pilot agreement

8. Accessibility and assurance status

The service is being designed for clear language, keyboard access, readable contrast and responsive use. A formal accessibility audit and school acceptance testing remain part of production assurance. Schools can use this pack to support their DPIA and request supporting data-processing material.

  • Accessibility review before live pilot
  • School-assisted DPIA information
  • Data-processing agreement available during procurement
  • Pilot launch only after agreed readiness checks

Ready for a school-specific review?

Apply for the pilot and we will confirm fit, named contacts and the assurance material your school requires before live use.

Start a pilot application