For IT and data protection
Nothing installed.Nothing connected.An agreement first.
In a shadow run and the first pilot, a file goes in and a file comes out. Nexar Schedule will work on candidate numbers under a data processing agreement signed before anything is sent, with hosting planned in London and a written list of who can see the files.
Being built now by Nexar Labs. No security certificate is held yet, and none is claimed.
What you would be approving
- Installednothing
- Connected to your systemsnothing
- Personal datacandidate numbers, treated as personal data
- Before a file movesa signed data processing agreement
The reason for an accommodation or access arrangement is never asked for.
What you are usually asked to approve.
Before anyone knows whether the tool is worth it.
An integration first
A connection into the student record system, as the price of a trial.
More data than the job needs
Names, dates of birth and reasons, sent because the template had a column for them.
Vague answers
No written list of who can see the files, or from where.
What it is being built to.
Each line has its own page.
- The commitments
- What we ask for, what we never ask for, where it is kept and who can see it. Your data and security
- Files in
- A spreadsheet or CSV export, read back to the exams office before anything is scheduled. Bring any file
- Files out
- A timetable file in the layout that was sent. Nothing is installed. Export to your system
- Plain code decides
- An optimiser builds and one checker decides. The AI reads and understands; it never sets a verdict. Conflict checking and proof
enrolments.csv, as a shadow run would receive it
- Candidate numberExam code
- 20401BUS101
- 20402ECO201
- 20403ECO201
- 20404BUS101
- and 366 more rows
What a shadow run would receive.
The first rows of the sample’s enrolments file: a candidate number and an exam code on each row. No names.
An accommodation or access arrangement is sent as the adjustment, never the reason for it.
Sample data, invented for this site.
Questions you would ask.
Are candidate numbers personal data?
Yes. A candidate number can be linked back to a person by your institution, so it is pseudonymised personal data and we treat it as personal data. That is why a data processing agreement comes first.
Is our data used to train a model?
That is not what the data is for, and the data agreement will say what it may and may not be used for. The timetable is produced by a solver and judged by a checker, both ordinary code that learns nothing from your files.
Do you hold a security certificate?
No. No security certificate is held yet, and none is claimed. The list of sub-processors will be written down for you before a pilot starts.
Written for your kind of institution.
The job is the same everywhere; the words are not.
Start with last season.
It costs nothing.
Send the files from last season and the timetable you published. We check it candidate by candidate, rework it on the same days and rooms, and send one page back.
Free. No purchase, no switch, no installation. Being built now by Nexar Labs.
What a shadow run needs from you
- Examscode, title, length
- Enrolmentscandidate number, exam code
- Roomsname, seats
- The timetable you publishedexam, date, time, room
As your system exports them. Candidate numbers, not names. The adjustment, never the reason for it.