Nelsah

What we do with your information

Written to be read by the people it is about — workers, agencies and the companies who hire them — rather than by lawyers.

Last updated 31 October 2026 · Version 1.6

Who we are

Nelsah is software that contractors and labour-supply agencies use to run their work: bookings, compliance records, attendance, hours, pay runs and invoices, on iPhone, iPad and the web.

Nelsah is made and run by N&Q Technology, the business of its two founders, Martin Quansah and Terry Nelson. N&Q Technology is not yet a registered company. We will add its registered details, and our registration with the UK’s data protection regulator, the Information Commission (still known as the ICO), here when they exist. [FOR MARTIN: confirm who is named as the controller of our own records and the processor of companies’ records until the company is registered, and whether the data protection fee has been paid.]

Write to us about anything on this page at privacy@buildforce.im. For anything else, hello@buildforce.im.

Whose records these are

Records a company keeps about its workers. When an agency or contractor uses Nelsah, what it keeps about its workers — right to work, SIA licences, screening, documents, shifts, hours, pay, incidents and welfare checks — are that company’s records. The company is the controller: it decides why they are kept and for how long. We are its processor: we hold and handle them for it, on its instructions, under our data processing agreement, and for no purpose of our own.

Our own records. For the sign-in account itself, for people who write to us or ask about Nelsah, for people at businesses we write to, for our customers’ business contacts and billing, and for this website, we are the controller.

So if you work through an agency or contractor that uses Nelsah, the company you work for is the first place to go with a question about your work records, and it should give you its own privacy notice. If you ask us instead, we pass your request to that company promptly and help it answer.

The short version

Nelsah holds what a company needs to offer you work, keep a record of the checks it makes, record the hours you worked and pay you for them.

We do not sell it. We do not track you across other apps or websites. There is no advertising identifier in Nelsah, no third-party analytics, and no advertising profile of you. We do not follow your location around — the app asks for it once, when you record attendance. There is one thing beyond that, you switch it on yourself, and it is described below.

What a company keeps about its workers

This is what a company can keep about you in Nelsah, and why. The company chooses its own lawful basis; the last column is the one we expect it to rely on. Some of it you enter yourself. The rest is entered by people at the company, or by a company you are booked to work for — a client approving your hours, say.

InformationWhy the company has itUsual lawful basis
Name, email, phone, town To identify you, offer you work and contact you about it Contract
Emergency contact So somebody can be reached if you are hurt on a shift Legitimate interests — and your vital interests if it is ever used
Trade, skills, availability To match you to work you can actually do Contract
Right to work record An employer must check you may lawfully work in the UK before you start. Nelsah keeps the record of the check the employer made: the method, the date, who checked, the documents seen, and when a time-limited permission runs out. That record shows your nationality or immigration status Legal obligation
SIA licence details Supplying an unlicensed person to a licensable role is a criminal offence Legal obligation
Licence re-checks A licence has to be checked again, not only when it is first recorded — each check records who looked, when, and what the answer was Legal obligation
Security screening Only where a security company screens you to BS 7858: five years of addresses and of what you were doing, references, your declaration of unspent convictions, the result of a criminal record check and of a financial check, and the company’s decision. This includes information about criminal offences Legitimate interests, with a condition from Schedule 1 to the Data Protection Act 2018 for the criminal offence information
Cards and certificates To show a site you are qualified for the work Contract, and legal obligation where a site requires it
Shifts, hours, timesheets To pay you correctly and to show a client what was worked Contract, and legal obligation for pay records
Holiday and availability Holiday you ask for or are paid, and days you are not available Contract, and legal obligation for holiday pay
Late drop-outs If you give up a shift inside the company’s notice period, it is recorded on your record (the shift, the notice you gave, any reason you add) and the office is told. A person at the company can withdraw it Legitimate interests
Pay rates, pay runs, payslips To pay you, and to keep the pay records the law expects Contract and legal obligation
What happened on a shift The site’s occurrence book: anything you report, in your own words, with the photographs you attach to it. A site, an insurer or an assessor asks for this, and a shift where nothing happened is recorded too. An entry can describe an injury, or an allegation of a crime Legal obligation, and legitimate interests
Briefings Which site briefings and must-read documents you confirmed, and when Legal obligation for health and safety
Welfare checks and alarms So somebody knows you are alright when you are working alone, and knows quickly when you are not. An alarm carries your number, your emergency contact and where you were last known to be Legal obligation for health and safety, and your vital interests
Patrol rounds To show a client the site was walked, which stops you being asked to prove it afterwards Contract
Attendance location To confirm you were on site when you clocked in Legitimate interests
Agreements you sign Your agreement with the company, as signed Contract
Messages and notices What you and the company send each other in the app Contract, and legitimate interests
Profile photo So a site supervisor can recognise who is arriving Consent — it is optional and you can remove it. Once removed, nobody can open it through Nelsah; the stored copy is deleted when you ask us to (see below)
Notification address The address your phone gives so it can be told about your work — see below. It is kept with your account in the company’s workspace. If you refuse notifications, there is none Legitimate interests
Audit trail A record of who changed what, and when, so the company can show how a decision was made Legitimate interests

What Nelsah keeps for itself

For these we are the controller, and the lawful basis is ours.

InformationWhy we have itOur lawful basis
Your sign-in account Your email address and your password, and which company’s workspace the account opens, so you can sign in on the app and the web. Your role and access in that workspace are the company’s record. The password is kept by the sign-in service in scrambled form. It is not a workspace field: the server strips any password field from every answer and refuses any attempt to write one Legitimate interests — running the service your company uses
Sign-in records The sign-in service records when an account signs in and the internet address it came from, to keep accounts safe Legitimate interests — security
Emails and early-access requests What you send to hello@ or privacy@, so we can answer you, and set your company up if you ask us to Legitimate interests
Business contacts we write to The name, work email and company of somebody at a business we write to about Nelsah, taken from that business’s website or a public listing Legitimate interests — every email says how to stop them
Customers’ business contacts and billing To run our agreement with a company and, once we charge, to invoice it and keep the accounts the law requires Contract, and legal obligation
Complaints When a complaint arrived, when we acknowledged it, and the outcome Legal obligation
Website request logs Our web host sees the internet address your browser connects from Legitimate interests — keeping the site running and safe

You do not have to give us anything to use this website. To sign in you need an email address and a password; without them we cannot give you an account.

About the location

Nelsah asks for your location at the moment you record attendance. That reading is deliberately coarse — rounded to roughly a hundred metres before it is stored — and there is no location history beyond the attendance records themselves. If you refuse the permission you can usually still record attendance, and the record simply carries no location. The exception is a company that has set Nelsah to refuse an arrival it cannot match to the site: there, the app will not record your arrival without a location inside the site, and you contact your coordinator instead.

There is one exception, and it exists only if you switch it on yourself. If you turn on clocking out when you leave the site, your phone watches a single circle — that site’s boundary — while you are on the clock there, and that watching does happen in the background. It records one thing: the time you crossed out. Not a route, not where you went afterwards, and nothing at all when you are not on shift. It is off unless you turn it on, and you can turn it off again at any time.

One place you might expect a position and will not find one: when a welfare check goes unanswered or you raise an alarm, the record says where you were last known to be in words — “clocked in at the Riverside Hall, 21:58” — because the app checks a location once, at arrival, and nothing after it. Writing a co-ordinate there would imply a tracking this app does not do. The same goes for a patrol round: it records the checkpoint you confirmed and the minute you confirmed it, and takes no reading from your phone.

What stays on a phone

Some of what is typed into Nelsah never becomes part of the workspace at all. It is held in a separate protected store on the phone it was typed on, encrypted by iOS, and deliberately left out of the phone’s own backup. It does not reach us:

One exception to this list: if your company switches on collecting private details in Nelsah, your bank details, date of birth, home address, emergency contact and referee are sealed (encrypted) on our server instead, and only you and the people at your company entitled to them can open them.

What does cross over from your own profile form into the shared workspace is your name, your phone number, your town, your trade and skills, how far you will travel, how you get there, how you are paid, and your emergency contact’s name, phone number and email, as one line.

Two exceptions worth knowing about. If a contract asks you to confirm your address when you sign it, the box is filled in with your town and whatever you leave in it becomes part of that signed document, which is held in the workspace like any other signed paperwork. And if a security company screens you to BS 7858, the five years of addresses and the references that screening asks for are part of the screening file in the workspace, which only you and the people at the company that employs you whose job is compliance can see.

Who else sees it

Nelsah exists to move information between the people who need it, so some of what you enter is meant to be seen by others. Who sees what depends on their role:

We have to be precise about the difference between what a company is shown and what their device receives, because for a time the two were not the same. Every device used to download the whole workspace and the app drew less than it held. That has changed. The app now asks the server for one thing — this person’s part of the workspace — and the server works out what that is, record by record, before it answers. A record you are not entitled to is not hidden on somebody’s phone. It never arrives.

Where the record is yours to see but a figure on it is not, the figure comes back blanked rather than the record withheld: a hiring company gets the shift without your pay rate on it. No device receives anybody’s password at all — the server strips passwords out of every answer and refuses any attempt to write one into the workspace.

What we are not claiming. It is one database rather than one for each company, and the separation is the answer the server gives rather than a wall between separate stores. Your own agency’s Owner still receives nearly all of that agency’s records, because that is what being the Owner means.

Your documents and photographs

Your documents, the photographs you attach to something that happened on a shift, the evidence you attach to a timesheet and your profile photo are sent, when you add them, to a private store beside the shared workspace, so that the office can actually open the thing your record says exists. A copy stays on your own phone.

Nothing is swept up: there is no scan of files you added before, and nothing on your phone is uploaded because it happens to be there. The store is private, it hands out no public or shareable links, and every download is checked against the record it belongs to at the moment it is asked for — so removing or replacing a reference, or losing access to the record, takes the file with it.

About notifications

If you allow notifications, your phone asks Apple for an address, and that address is kept with your account in the company’s workspace, so that your phone can be told about your work: a shift offered to you, a shift about to start, a welfare check nobody answered. The server prepares those notifications for Apple’s push service and keeps them short — no pay, no addresses, no licence numbers and nobody else’s name, because a lock screen is read over somebody’s shoulder.

Whether a notification reaches your phone while the app is closed depends on one thing on our side: the sending key Apple issues to us. Until that key is installed on our server, nothing is handed to Apple: notifications appear only while Nelsah is open, and the app’s notifications screen says so, so please do not rely on your phone to tell you about something that happens while it is closed. Once the key is installed, the server hands each notification to Apple’s push service, kept short as described above, and Apple carries it to your phone. Nobody in your company is shown a list of registered phones. [FOR MARTIN: say here whether the sending key is installed at launch (docs/SWITCH_ON.md, section 5), and date this page accordingly.]

Our suppliers, and where the data goes

We use a small number of suppliers. Each handles personal data only on our instructions, under a written agreement.

Apple distributes the iPhone and iPad app through TestFlight and the App Store, under Apple’s own terms and privacy policy. It is not one of our suppliers for the workspace. Once push notifications are switched on (see above), Apple’s push service receives each notification’s short text and your phone’s notification address, and nothing else from the workspace; until then it receives nothing from it. If we invite you by email to test the app through TestFlight, Apple receives that email address from us so that it can send you the invitation. Your phone gets its notification address from Apple itself.

Emails you send to hello@ or privacy@ are forwarded by our domain provider, Namecheap, to the mailbox we read them in.

Automatic SIA licence checks are built in. A security company’s Owner can switch them on for their company from the website’s settings; the iPhone app shows whether they are on. Our server sends a licence number out only when it is connected to the checking service, and we connect it only after we have a written data processing agreement with that supplier and have added it to the list above. [FOR MARTIN: say whether the server is connected to SIA Verify at launch. If it is, sign SIA Verify’s data processing agreement first and add SIA Verify to the suppliers above and to Annex A of the data processing agreement (docs/SWITCH_ON.md, section 6).] When checks are on and the server is connected, it sends each licence number, and nothing else, to SIA Verify (siaverify.co.uk), an independent service that reads the public SIA Register of Licence Holders. It is not the SIA and not an official feed. It sends back what the public register shows for that number — name, licence type, role, status and expiry — and that answer is recorded in the licence’s history. Every worker is told in the app before their licence is first checked, and no check is made until seven days after that. An answer never changes anybody’s licence status or shifts on its own. The one thing it changes by itself: an “active” answer that matches a licence somebody at the company has already confirmed on the register moves forward the date that licence was last checked. Anything else is handed to the company’s Owners and Compliance staff to look up on the register and record what it shows.

We do not sell your data, and we do not share it with data brokers or advertisers. We share information with HMRC, the Home Office, the SIA, the police or another authority only where the law requires us to.

The assistant

A company Owner can switch on an assistant that drafts plans and suggestions; nothing it drafts happens until a person at the company approves it. It is off unless they switch it on. Nelsah’s own planner runs on the phone and sends nothing anywhere. A company can instead point it at a computer in its own office, or at its own account with an AI model provider. Then the brief, the dates, trade names, the default charge rate and approved office instructions go to that service, which the company chose and has its own arrangement with; an explicitly requested decision review may also include the review information shown in the app. A typed brief can itself contain personal information.

We have also built a hosted assistant, Hermes. It is not switched on: the app carries no address for it. Before it is, we will name its host and its model provider on this page.

Decisions made automatically

Nelsah applies a company’s own rules before work is offered. It will not let a shift be offered to somebody whose right-to-work record, licence, screening or documents do not cover it, and it says why. It also will not let you clock in while one of those checks has lapsed, or before you confirm a must-read briefing; and where a company has chosen it, it will not record an arrival it cannot match to the site. When an office asks it for people who could fill a shift, it lists only those who are free and covered. On the phone that list is in a simple order: ten points if the town on their profile includes the word London, plus one for each skill on their profile, then by name. Where the server draws the list up — on the website, and in the app’s checked list — it is not scored at all. The decisions about you — whether to engage you, whether a check was good enough, who is offered a shift — are made by people at the company.

How long records are kept

A company’s records

How long a company keeps its workers’ records is that company’s decision, within what the law asks of it. The Home Office, for example, expects an employer to keep its copies of a right-to-work check for as long as the person works for it and for two years afterwards. We keep a company’s records for as long as it uses Nelsah, and at the end return or delete them as our data processing agreement says.

The app holds each company’s own review periods. We have to be straight about what that does: nothing is deleted automatically when a period runs out. The periods mark a record for review, and the screen that saves them says as much. A deletion, or an anonymisation, is a decision somebody at the company makes and records — and a decision recorded against a request to remove something does not itself remove anything.

Two further edges, told plainly rather than found later. When a document record goes, the file behind it stops opening for everybody straight away, because every download is checked against the current record — but its contents stay in the store until somebody clears them out by hand. And an audit entry, a signed agreement, an invoice or a message written months ago can still carry your name, so removing a profile does not remove every trace of you. An alarm you raised keeps what happened, when, and who answered it — a safety record the company may have to produce — but the phone number and the emergency contact it copied down at the time are cleared with your profile, because getting somebody to a gate that night is not a reason to hold a relative’s number for ever. Ask the company for a retention review, or ask us and we will pass it on.

Our own records

Your rights

Under UK GDPR you can ask:

For your work records, the company you work for decides, because it is the controller. You can start most of this inside the app, under Settings → Your data & privacy: ask for a copy of your information, or ask for something to be corrected or removed, and the request goes to your company. Settings → Close your account closes your account. If you write to us instead, we pass your request to the company promptly and help it answer.

For our own records — your sign-in account, what you sent us, and this website — write to privacy@buildforce.im. We answer within one month.

The copy you can get from the app holds your account and the records you are entitled to see. Source documents, checks, messages, bank details and exact locations need a separate review with your company, and the app says so on the screen rather than handing you a file that quietly leaves them out.

Closing your account takes your name, email, contact details, sign-in, trade and availability profile and emergency contact with it. It removes your document records except your right-to-work and BS 7858 screening documents, and cancels bookings you had not worked. The protected store on your own phone — bank details, date of birth, address and referee — goes at the same time. It does not take the hours you worked, the agreements you signed, your right-to-work and screening documents, your BS 7858 screening file, the checks recorded about you, or the invoices raised. The company may have to keep those, and the screen lists what will stay before you confirm.

When a photo or document is removed, nobody can open the file through Nelsah from that moment. When your account is closed, the same goes for your profile photo and the documents closure removes. The files your company has to keep (right-to-work and screening documents, timesheet evidence and incident photos) stay open to the people entitled to those records. The stored copy of a removed file is not yet deleted automatically: ask us and we delete it, apart from anything your company has to keep. We are adding an automatic clean-up.

Complaints

If we get it wrong, tell us. Email privacy@buildforce.im, or write to N&Q Technology at the postal address we will publish here once the company is registered [FOR MARTIN: a postal address for complaints until then]. Say what happened and what you would like us to do. We acknowledge every complaint within 30 days of receiving it, look into it, keep you told how it is going, and tell you the outcome.

A complaint about records a company keeps about you is best made to that company, because it decides what happens to them. If you send it to us, we pass it to the company promptly and tell you we have.

You also have the right to complain to the UK’s data protection regulator, the Information Commission — still known as the ICO, the Information Commissioner’s Office — at ico.org.uk/make-a-complaint or on 0303 123 1113. Complaining to them does not cost anything.

Keeping it safe

Cookies and storage

This website sets no cookies and runs no analytics or advertising code. Its fonts are served from the site itself, so opening a page tells no font company that you visited. It does keep a few small things in your browser’s own storage, listed here. None of them is sent anywhere, except the sign-in session, which goes only to our workspace when you use the office, client or worker pages, and anything the worker pages saved with no signal, which goes only to our workspace once the signal is back.

In plain words, your browser keeps:

The table names each one.

What is storedWhat it is forHow long it lasts
buildforce-web-session Your sign-in session, so you stay signed in to the office, client and worker pages. It is only there if you sign in Until you sign out, which removes it
bf-theme Light, Dark or System, if you chose one. With nothing chosen the site is Light Until you clear this site’s data
bf-single-keys That you turned single-key shortcuts off Until you turn them back on, which removes it
bf-hours-layout
bf-bookings-order
bf-fill-plan-days
How you like the Hours page laid out, the order of your bookings, and how many days a fill plan covers Until you clear this site’s data
bf-today-prefs:<your account> Your choices on Today (whether the day at a glance is folded, which shows you pinned, and when you last looked), kept here so the page opens as you left it before the server answers; the server keeps the same record for your other devices Until you clear this site’s data
bf-desk-setup-later:<your company>:<your account> That you pressed “Later” on Today’s setup card for a new company, so it stays closed on this computer Until you clear this site’s data
bf-insight-prefs:<your account> Your choices on Reports and Money’s Overview (which period you look at and whether you see every open invoice or only the overdue ones), kept here so the page opens as you left it before the server answers; the server keeps the same record for your other devices Until you clear this site’s data
bf-guide:<your account>:<seat>:v<version> Whether you have seen, skipped or finished the short tour of your pages, and which step you were on, so it is not offered again Until you clear this site’s data
bf-walk:<your account>:<seat>:v<version> For “Walk me through today”: today’s date, whether you said “Not today”, and which steps you have been through with their numbers, so it does not repeat itself. Nothing else, and it is never sent Replaced the next day; until you clear this site’s data
bf-work-shared-device On the worker pages, that you ticked “This is a shared device” when you signed in, and when the page was last used, so you are signed out after 30 minutes without use, even after a reload Until you sign out, which removes it
bf-work-offline:<your account>
bf-work-offline-last
On the worker pages, on your own phone or computer only (never on a shared device): your booked shifts for the coming week — the site, the times, the briefing and whether your checks let the shift start — so you can check in, take a break and check out with no signal. No pay, no messages and no other person Until you sign out, which removes it. It is not used once it is three days old
bf-work-queue:<your account> (the browser’s own database) On the worker pages, a check-in, break, check-out, patrol checkpoint or report made with no signal, with the location taken at the time, until it can be sent. Only your own account sends it; signing in as someone else on the same browser never sends or deletes it Until it is sent, or until you tell your coordinator about one that was not recorded and clear it
bf-closing-account That you asked to close your account from this browser, while the request is on its way, so the sign-in page can say so if the answer never came back Until the answer comes back, or you next sign in
bf-brief-draft A plan you typed on the home page, handed to the demo so it can show it to you Until you close the tab

A preference is stored only when you change that setting; leave it alone and nothing is stored for it. You can say no to any of them by not changing the setting, or by clearing this site’s data in your browser’s settings, which removes them all — the site then works with its defaults. The sign-in session is needed to stay signed in; everything else is there only because you asked for it.

The worker pages also keep their own files (the page and its code, never any information about you) in the browser’s cache, so they can open with no signal.

The office and client pages show only what the server has already decided your account may see — the same rules as the app. The iPhone and iPad app keeps your part of the workspace, your settings and any work not yet sent on the phone, so that it keeps working without a signal.

Children

Nelsah is for people of working age and is not directed at children. We do not knowingly collect information about anyone under 16. If you believe a child has given us information, tell us and we will remove it.

Changes

If we change this policy we will update the date and the version at the top. Where a change matters to you, we will tell you in the app or by email rather than relying on you to come back and check.

What changed in version 1.6 (31 October 2026), since version 1.5:

What changed in version 1.5 (5 October 2026), since version 1.4: