Your data and security

Numbers in.No names.No reasons.

Written for the data protection officer and the IT lead who read this after the exams office. Each line is a planned commitment, to be put in writing before anything is sent.

enrolments.csv, as a shadow run would receive it

  • Candidate numberExam code
  • 20401BUS101
  • 20402ECO201
  • 20403ECO201
  • 20404BUS101
  • and 366 more rows

Candidate numbers and exam codes from the sample on this site. No names. An accommodation or access arrangement is sent as the adjustment, never the reason for it.

What we will hold, and how.

Nexar Schedule is being built. These are the terms it is being built to, and each will be in the data agreement you sign before a file moves.

What we ask for
Candidate numbers, exam codes, rooms and the adjustment a candidate is entitled to. The shadow run needs no names.
What we never ask for
The reason for an accommodation or access arrangement. We store an adjustment, never a diagnosis.
What it is in law
Candidate numbers are still personal data, and we will treat them as such. We do not call them anything else.
Before anything is sent
A data processing agreement, signed by both sides.
Where it is kept
Hosting is planned in London.
Who can see it
You will be given a written list of every system, company and person that can see your files, and from which country.
How long it is kept
The retention period, and how files are deleted at the end of it, will be set in the data agreement with each institution.

Security, said plainly.

What the first pilot is planned to have, and what we do not claim yet.

Planned for the first pilot

  • Nothing installed on your machines, and no connection into your student record system: a file goes in and a file comes out.
  • Files sent only after the data agreement is signed, by a route named in it.
  • Candidate numbers in place of names throughout.
  • An optimiser and a checker in plain code decide the timetable. AI reads your files and understands your requests, and you confirm what it read. It never sets a verdict.

Not claimed yet

  • No security certificate is held yet, and none is claimed.
  • Sign-in with your institution’s account, and roles, come after the first pilot.
  • Links into student record systems come after the first pilot.
  • The list of sub-processors will be written down for you before a pilot starts.

Questions a data protection officer asks.

All questions

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.

Do you need names, dates of birth or medical details?

No. A shadow run needs candidate numbers, exam codes, rooms with seats, and the timetable you published. For an accommodation or access arrangement, send the adjustment, for example 25% extra time and a separate room, and never the reason for it.

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.

Does anything connect to our student record system?

No. In the shadow run and the first pilot you export a spreadsheet or CSV and receive a timetable file back. Links to student record systems are planned for later and would be agreed separately.

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.