AI and your data.
What a head of department needs to know before a department uses this.
What we do with what you type
Your brief, your uploaded files and your lesson are used for one thing: making and editing that lesson. They are not used to train any model, and they go nowhere beyond the services named on this page.
No pupil data, by design
The brief asks about the class, not the children: class size band, how many pupils have SEND or EAL or are working above or below, and what they already know. Type a pupil name, an email address or an ID number and the brief blocks it before it is saved. Nothing about an individual pupil belongs in DayBack, and nothing is set up to receive it.
Which AI, and where it runs
The models are OpenAI’s GPT models. We do not call OpenAI directly: every call goes through Amazon Bedrock, which does not retain the text sent to it and does not train on it. Bedrock processes those calls in the United States.
Where your lessons live
The application, the database and the files you upload are hosted in the European Union, in Amsterdam. The website you are reading is served from Vercel’s network. The AI call is the one part that leaves the EU, and nothing is kept at the other end.
What we log
Prompts and lesson content are never written to our logs. We record which model ran, how long it took, what it cost, and error codes when something breaks.
Sign-in and email
Sign-in is a link sent to your email address through Resend, in the EU, or your Google account. We keep your name, email and profile photo link from Google, never Google’s access keys. There is no password.
Cookies
Only the cookies that keep you signed in. No advertising cookies, and no analytics cookies. We measure page load speed, and nothing about you.
Read it before you teach it
DayBack checks that a lesson holds together, and checks its facts and answers. It can still get something wrong. Read the lesson before your class does.