Skip to main content
nAItives
Safety & privacy

AI literacy needs trust built in.

Schools need confidence that AI is introduced safely, responsibly and transparently. nAItives is designed around age-appropriate interaction, content moderation, teacher oversight, data minimisation and school governance — from the start.

Age-appropriate by design

Different safeguards for different ages.

Younger pupils do not need open-ended access to AI. Primary pupils use guided interactions and structured choices; older pupils have more freedom, within a moderated, school-safe environment.

Ages 5–7

Guided click & tap

No free-form text. Pupils explore AI through structured choices with full teacher support.

Ages 8–11

Structured inputs

Limited, guarded inputs with guardrails — building confidence while staying safe.

Ages 11+

Moderated text input

Text input with moderation and teacher oversight, plus structured reflection.

Moderation & oversight

Designed to prevent unsafe content reaching pupils.

nAItives uses layered moderation to check student inputs and AI outputs before content is shown. If something is flagged, pupils see a calm, age-appropriate fallback message and teachers are alerted where needed.

Input checks before AI calls
Output checks before display
Image upload checks for drawing activities
Flagged safety events visible to teachers
Normal conversation logs not stored as full transcripts

Privacy-first data handling.

Schools remain the data controller; nAItives acts as data processor. Personal data is only used to deliver the service, support learning evidence and operate safety controls.

DPA required before school go-live
DPIA support available
Data stored in UK/EU infrastructure where applicable
No student data used to train AI models by default
Clear data retention and deletion processes

Careful controls for pupil drawings.

For drawing-based activities, pupils are instructed to upload only their artwork — not faces, names or people.

"Only the drawing — no faces, names or people"
Crop / confirm step before upload
File restrictions & EXIF stripping
Private storage in production
AI vendor handling

Transparent use of AI providers.

nAItives uses trusted AI providers to generate text and images. Where student inputs are processed by AI services, this is explained clearly in the procurement pack, covered in data flow documentation and governed by appropriate contractual mechanisms.

The public website gives a plain-English summary. Full technical and data protection details are shared with schools during procurement and DPO review.

Teacher oversight

Teachers stay in control.

Teachers manage classes and access
Teachers see progress and flagged events
No student-to-student messaging
No public sharing of pupil content
Common questions

Questions school teams ask.

Is pupil data used to train AI models?

No — by default, student data is not used to train AI models via our API providers. AI vendor handling is documented in full for schools during procurement.

Who is the data controller?

The school remains the data controller. nAItives acts as the data processor, with a Data Processing Agreement (DPA) required before go-live and DPIA support available.

What happens if a pupil enters something unsafe?

Inputs are checked before they reach the AI, and outputs are checked before display. Unsafe content is suppressed, the pupil sees a calm fallback message, and the event is made visible to teachers where appropriate.

Can we review everything before adopting?

Yes. Book a demo and we'll share the DPO-ready procurement pack with full technical and data-protection detail.

Need more detail for your school team?

Book a demo to understand how nAItives approaches safety, privacy and governance.