Skip to content

Last updated: 14 September 2026 · ICO registration: ZB378294

Plain-English summary. We are SLT AI, the people behind School Assistant. Schools are the controllers of the data in their assistant; we are the processor. We log the text of parent questions for 30 days (no names, no IP addresses). When a question is routed to a person, the verbatim message is emailed to the school in real time - that email, in the school’s own inbox, is its safeguarding record. Sub-processors are listed in section 11 below.

1. Who we are

School Assistant is operated by SLT AI, a UK partnership. We are registered with the Information Commissioner’s Office under registration ZB378294. You can reach us at info@schoolassistant.co.uk. Postal correspondence for data-protection queries: email first and we will reply with a postal address.

2. What data we collect

Schools (our customers)

Website visitors (parents, carers and other visitors)

3. How we use data

4. Multilingual processing

The chat widget detects the language of each visitor question and replies in the same language across eleven supported languages (English, Polish, Romanian, Urdu, Punjabi, Arabic, Bengali, Somali, Portuguese, Spanish and French). To do this, the question text is sent to OpenAI, which performs language detection, translation and answer generation under our data-processing terms. Non-English question counts are aggregated to drive the school’s “% non-English” EAL dashboard; individual non-English text is treated identically to English text and retained for the same 30-day window.

5. Safeguarding data

The widget recognises parent questions that should be handled by a person rather than AI - for example questions about reporting bullying, raising a concern about a member of staff, or a child’s wellbeing, as well as language consistent with self-harm, abuse or mental-health crisis. In these cases the assistant does not attempt an answer: a classifier short-circuits the LLM and the visitor sees a canned response signposting the school’s designated safeguarding contact and, where appropriate, external services such as NSPCC and Childline. In parallel, a transactional email containing the verbatim message and timestamp is sent to the school-designated contact (Designated Safeguarding Lead address or office address, as the school configures). The lawful basis for this processing is vital interests (Article 6(1)(d) UK GDPR) and the substantial public interest in safeguarding under Schedule 1 of the Data Protection Act 2018. Schools are required to maintain a current routing email address and to handle these notifications under their KCSIE policy.

No automated classifier can guarantee it will recognise every safeguarding-relevant message. As a safeguard against a missed detection, schools should keep their normal safeguarding-reporting channels (posters, staff briefings, the DSL’s published contact details) visible on their site independently of the assistant, and can use the portal’s chat log at any time to review conversations, including ones the classifier did not flag.

6. Portal activity logging

Actions taken by school staff inside the portal (document uploads and deletions, settings changes, template approvals, access grants, exports and safeguarding triage decisions) are logged so the school can review account activity. These logs are kept while the subscription is active and are deleted, along with all other school data, within 30 days of cancellation (see section 13). The school’s own safeguarding record is the real-time routing email sent to its DSL or office address under section 5, held in the school’s own systems under its KCSIE policy.

7. GIAS data

We ingest data from the Department for Education’s Get Information About Schools (GIAS) register, which is published under the Open Government Licence v3.0. During onboarding, we use the school’s URN/DfE number to pre-populate school metadata (name, address, phase, headteacher, pupil count and similar fields). We refresh this data periodically so the school’s record stays current. Schools can edit any pre-populated field, and inaccurate GIAS data should be corrected through DfE channels.

8. Email-to-knowledge

Each school is allocated an inbound email address (e.g. docs-TOKEN@inbound.schoolassistant.co.uk). Documents emailed to this address are ingested into the school’s knowledge index. We log the sender email address, subject line and arrival timestamp; spam and attachments above size limits are rejected without ingestion. The Postmark inbound service is the sub-processor for this pathway (see section 11).

9. Knowledge-gap analysis

To produce the weekly knowledge-gap digest and the “top questions” report, we group anonymised visitor question text into topic clusters and present aggregates to school staff. The text shown in these aggregates may include the original wording of parent questions, with no identifiers attached. Schools can opt their portal display out of question-text aggregation in the settings panel; the aggregated counts continue regardless.

10. Security

11. Sub-processors

Last reviewed: 14 September 2026. We use the following sub-processors to deliver the service. Each is bound by data-processing terms equivalent to those we offer schools.

Our AI sub-processors (OpenAI, Anthropic) are contracted under API/business-tier terms, not consumer product terms: none of them use documents, website content or visitor questions submitted through School Assistant to train or improve their underlying models.

Sub-processor Purpose Region
SiteGround Web hosting for the marketing site, portal and widget API UK / EU
Pinecone Vector database for school knowledge embeddings US (SCCs in place)
OpenAI Embeddings, language detection, answer generation US (SCCs in place)
Anthropic Template synthesis and page classification during onboarding US (SCCs in place)
Firecrawl School website scraping with the school’s consent US (SCCs in place)
Postmark Transactional email and inbound email-to-knowledge US (SCCs in place)
Google Cloud Vision OCR for image-based PDFs, on demand US (SCCs in place)

We notify schools by email before adding or removing a sub-processor. Schools may object within 14 days; if a substitute cannot be agreed, the subscription can be terminated with a pro-rata refund.

12. Cookies

The marketing site (schoolassistant.co.uk) uses a small number of cookies, grouped as follows:

You can manage your cookie choices via the banner that appears on first visit. Withdrawing consent at any time will not affect the lawfulness of prior processing.

13. Data retention

14. Accessibility

We aim to make schoolassistant.co.uk and the embedded widget conform to Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. The widget supports keyboard navigation, screen-reader landmarks, language switching to match the detected reply language, and high-contrast colour pairs. Issues can be reported to info@schoolassistant.co.uk; we aim to respond within five working days. This statement is published in line with the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 for the benefit of public-sector buyers.

15. Your rights (UK GDPR)

As a school, you are the data controller for the documents you upload and the visitor questions logged against your namespace. School Assistant acts as a processor. You have the right to access, rectify, erase, restrict, port and object to processing. To exercise any of these rights, contact us at info@schoolassistant.co.uk. You also have the right to complain to the Information Commissioner’s Office at ico.org.uk.

16. Data Processing Agreement

A Data Processing Agreement is available at /dpa/ and is auto-applied at checkout. Schools may also countersign their own DPA template, subject to review.

17. Changes to this notice

We update this notice when our processing changes. The last-updated date at the top reflects the most recent material change. Schools are notified by email of material changes that affect processing of their data.

18. Contact

For privacy-related queries, email info@schoolassistant.co.uk.