This notice explains what personal data Nurcareer collects, why, on what lawful basis, who else sees it, and what you can do about it. It is written to be read rather than to be survived, and it is specific to how this service actually works — briefs, reviewers, evidence files and route maps — rather than a generic template.
1. Who we are
Nurcareer is the data controller for the personal data described here. Our registered office is [registered address] and our company number is [company number]. You can reach our data protection contact at nurcareertt@gmail.com.
We are a training provider. We are not an immigration adviser, a law firm or a recruitment agency, and nothing we send you is legal or immigration advice.
2. What this notice covers
It covers the Nurcareer website, the Brief Finder, route map calls, courses and briefs, the review and sign-off process, the evidence file, and the Brief Exchange. Different parts of the service collect different things, so the sections below are organised by what you are actually doing rather than by category of data.
3. The Brief Finder
The Brief Finder asks ten questions about your company and shows you the result on screen. There is no account, no sign-in and no email wall, and this is a deliberate design decision rather than a courtesy.
- Your answers are held in your browser while you work through the questions. They are not sent to our servers.
- If you generate a shareable link, your answers are encoded into the URL itself. The link carries the answers and nothing else — no name, no company, no email — and anyone with the link can see the same result. Treat it the way you would treat any link containing information about your business.
- If you close the tab without asking us for anything, we hold no record that you ran it, beyond ordinary analytics covered in our Cookies Policy.
At the end you can optionally ask for the briefs as a document. That form has two separate tick boxes and they are genuinely separate: one sends the pack you have already seen, the other opts you into occasional notes about obligations and deadlines. Ticking the first does not opt you into the second. We record which boxes you ticked and when, because we have to be able to evidence that.
4. Route maps and right-to-work information
A route map call is a conversation about your right to work, so it necessarily involves your nationality, your immigration status and sometimes your visa history. We treat this as sensitive whether or not it meets the legal definition of special category data, because getting it wrong has consequences for you that getting a marketing preference wrong does not.
- We collect only what is needed to tell you which routes are realistically open to you.
- We do not ask for, and do not want, copies of your passport, visa or biometric residence documents at this stage.
- We do not share your immigration status with employers. Where a sponsor needs it later, that is a conversation you have directly.
- You can ask us to delete our notes from the call at any point, and we will do so without asking why.
If your situation needs regulated advice we will say so and point you to a regulated adviser. We will not guess, and we will not sell you a course to work around a rule that a course cannot change.
5. If you learn with us
Once you have an account we hold:
- Account data — name, email, hashed password, and whatever you choose to put on your profile.
- Learning data — course progress, readiness gate results, submissions and the correspondence around them.
- Brief data — the briefs assigned to you, what you delivered, reviewer marks against each acceptance criterion, and revision history.
- Payment data — billing records. Card details are handled by our payment processors and never reach our servers.
- Usage data — IP address, device and browser, and sign-in events, kept for security rather than for profiling.
6. Your evidence file
The evidence file is the point of the whole service, so it gets its own rules. It contains the original brief, what you shipped, the reviewer's named and dated sign-off, a scope and responsibility letter, your decision log, and a recorded walkthrough of you explaining your own work.
- The reviewer for a given brief sees that brief and what you submitted against it. They do not see the rest of your file.
- The client who posted the brief sees the reviewed deliverable for their brief only.
- Everyone else sees it because you sent it to them. We do not publish it, index it or pass it to recruiters.
- The walkthrough recording is a recording of you. We use it as part of your file and as language evidence you can point at. We do not use it to train anything, and you can replace or delete it.
You can export the whole file at any time, and you can delete it. Deleting your file does not retract a sign-off a reviewer has already given, and it does not claw back a copy an employer already holds — we cannot un-send something you sent.
7. If you review briefs
Reviewers are practitioners, and the value of a sign-off comes from it being attributable. Your name, your current employer and the date appear on the sign-offs you give, and the learner can show that to a hiring manager or an immigration adviser. That is the arrangement you are agreeing to when you review.
We additionally hold your discipline and market, your availability, and the bank and tax details needed to pay you. Your fee does not depend on the outcome of any review, and we do not tell learners how much you were paid.
8. If you post work to the Brief Exchange
We hold your contact details, your organisation, the brief itself and the acceptance criteria you agreed. Briefs frequently contain commercially sensitive material — architecture, supplier lists, risk registers — so treat the brief you write as the scoping document it is, and tell us if any part of it should not be shown to a learner before you post it.
We share the brief with the learner delivering it and the reviewer marking it, and nobody else. We do not use the contents of your brief as teaching material without asking you first.
9. Lawful bases we rely on
Under UK GDPR and EU GDPR we need a lawful basis for each thing we do. Here is the full list rather than a summary of it.