Privacy Policy

Last updated: 7 October 2026

Who controls your data: For pupil and staff data in the Send Signals platform, your school or trust is the data controller and Send Signals Limited is the data processor, acting only on the school's documented instructions under a UK GDPR (Article 28) Data Processing Agreement. Send Signals Limited is the controller of a small amount of data it keeps for its own purposes: enquiries you send us through this website, school billing records, and the record of who accepted our agreements on a school's behalf (see section 1).

1. What We Collect

We collect the minimum data necessary to provide our service:

• Student name and the identifier their school already uses for them. Depending on what the school turns on, a pupil signs in with a login card, MyLogin, or a school Microsoft, Google or Apple account. Many pupils never need an email address at all.
• Lesson check-in responses (green/amber/red)
• Pre-set message selections. Pupils cannot type their own messages.
• Timestamps of interactions, and welfare alerts raised from check-ins with how staff responded
• Device push-notification token, only if notifications are turned on, used to deliver check-in reminders and alerts
• An audit log of key actions taken by staff accounts, and the IP address and browser used for sign-ins and some staff actions, to keep the service secure

Where pupil and staff details come from: your school chooses how to set us up. If it connects its management information system (MIS) through Wonde, a school data service, we receive from that system: pupil names, dates of birth, unique pupil numbers, year groups, classes and timetables, attendance marks, SEND status and need type, and pupil premium and EAL indicators; and staff names, work email addresses and employment details. We only receive the data sets the school approves in Wonde. Schools that do not use Wonde can upload the same kind of details from an export of their MIS instead, or enter them by hand. A school may also record a pupil's diagnosis, which is health information.

When you request a demo or contact us through this website, we also collect the details you provide (your name, work email, school and role) so we can respond to your enquiry.

When someone accepts our School Subscription and Data Agreement and Data Processing Agreement on a school's behalf, we keep a record of that acceptance: the school's name and the details the agreements were filled in with, the person's name, email address, role and job title, the version they accepted, the date and time, and the IP address and browser they used, so that the school and we can show who agreed to the terms and when. The record holds no pupil data. We keep it for six years after the school's data is deleted, and then delete it. The IP address and browser are deleted sooner, when the school's data is deleted.

2. How We Use It

Pupil check-in data is used solely to support student wellbeing and SEND provision within the student's school. We never sell pupil data, use it for advertising, or use it to train AI models. Demo-enquiry details are used only to respond to your enquiry, never for advertising, and never sold. Alerts only prompt school staff to look and decide; no decision about a pupil is made by automated means alone.

3. Children's Data

Our service is designed around the principles of the ICO Age Appropriate Design Code. Data minimisation is a core principle. Students never see other students' data. All data is processed with the child's best interests as the primary consideration.

4. Data Storage

Pupil data is stored at rest in the UK (Supabase, London). The application runs in Vercel's London region, and pages are delivered over Vercel's global network. Some service providers (email, push notifications, billing and the staff help assistant) process limited data outside the UK, as listed in section 5, under UK adequacy regulations or appropriate UK transfer safeguards. We use Supabase with Row-Level Security to enforce data isolation at the database level. Data is encrypted in transit (HTTPS) and at rest.

5. Service Providers

We don't sell data, use it for advertising, or allow third-party tracking. To run the platform we use a small number of data processors, acting only on our instructions:

• Supabase: database and sign-in. United Kingdom (London).
• Vercel: application hosting. United Kingdom (London), with pages delivered over a global network.
• Resend: email, including alerts and sign-in emails. European Union (Ireland).
• Stripe: billing. School contact details only, no pupil data. United States and European Union.
• Google Firebase Cloud Messaging and Apple Push Notification service: delivering push notifications to devices. United States.
• Anthropic: a help assistant that answers school staff's how-to questions. It is on by default, and a school can switch it off in Settings, Audit and governance; when it is off, nothing is sent to Anthropic for that school. Questions that appear to contain pupil details are refused, and no pupil data is sent. United States.

This website is hosted by GitHub Pages (GitHub, United States). On our public demo forms we use Cloudflare Turnstile to block automated abuse; it never sees school or pupil data, and it is not used in the Send Signals platform's sign-in.

Where a school connects its MIS through Wonde, Wonde passes the school's data to us. Wonde is appointed by the school under its own data processing agreement with the school and acts for the school, not for us, so it is not one of our sub-processors.

6. How Long We Keep It

• Pupil check-ins, messages and welfare alerts: for as long as the school chooses in its settings (3 years by default, 30 days at least), then deleted automatically each night.
• When a school leaves: when its subscription ends, whether it is cancelled, lapses for non-payment or ends in any other way, off-boarding starts automatically that day. We email the school's billing contact and administrators to tell them, and offer the school an export of its data; the school can ask for the export or tell us it does not need it. We then delete the school's data within 30 days of the subscription ending; deletion is a deliberate action by us, which becomes possible from day 23. If data must be kept for a legal reason, for example a legal claim, we place it on legal hold, which pauses deletion until the hold is lifted.
• School name and contact details: while the school is a customer and for six years after it leaves, for our legal and accounting purposes.
• Billing records and invoices: for at least six years, for tax purposes. Our copies of invoices are not deleted.
• The record of who accepted our agreements on a school's behalf: for six years after the school's data is deleted, and then deleted (see section 1).
• Security and email-delivery logs: 90 days. App error reports: 30 days.

7. Data Breaches

If a personal data breach affects a school's data, we tell the school without undue delay and in any event within 48 hours of becoming aware of it, so that it can meet its own obligations, including telling the ICO within 72 hours where required.

8. Your Rights

Under UK GDPR, you have the right to access, rectify, erase, restrict processing, and port your data, and to object. For pupil data, the school is the data controller: requests about a pupil's data should go to the school, and we assist the school in responding. If you contact us directly at privacy@sendsignals.co.uk we will pass your request to the relevant school promptly. For details you have given us directly (for example a demo enquiry), contact privacy@sendsignals.co.uk. You can also complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.

9. Contact

Data protection contact: Nicola Youngman (Data Protection Lead), privacy@sendsignals.co.uk. General enquiries: hello@sendsignals.co.uk. Send Signals Limited, a company registered in England & Wales (company no. 17147174), registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. ICO registration ZC138681. VAT registration number GB527441102.