Nelsah
Data processing agreement
How Nelsah handles the personal data a customer puts into it, on the terms UK GDPR Article 28 requires.
Last updated 31 October 2026 · Version 1.1
1. Who this agreement is between
1.1 This agreement is between N&Q Technology, trading
as Nelsah (“we”, the processor), and the
business that uses Nelsah under our
terms of service (“you”, the
controller). N&Q Technology is not yet a registered
company; we will add its registered details here when they exist. [FOR MARTIN:
confirm who the processor is until the company is registered.]
1.2 It forms part of the terms of service and applies whenever we process
personal data for you. Where the two differ about personal data, this agreement
wins.
1.3 Words such as personal data, processing,
controller, processor, data subject and personal
data breach mean what they mean in the UK GDPR and the Data Protection Act
2018 (“data protection law”).
2. The processing
2.1 Subject matter. Providing Nelsah to you.
2.2 Duration. For as long as the terms of service last, and
afterwards until your data is returned or deleted under section 9.
2.3 Nature. Storing your records in a shared workspace;
keeping them in step between your users’ phones, tablets and browsers;
working out, record by record, what each of your users may receive; storing the
files your users add; sending service emails; preparing notifications for your
users’ phones; and producing the reports and exports your users ask for.
The processing is automated.
2.4 Purpose. To provide Nelsah to you as the terms of
service describe, and for no purpose of our own.
2.5 People the data is about.
- your workers and people applying to work for you, including workers a
sub-contractor supplies to you;
- your office staff and other users;
- your clients’ and sub-contractors’ contacts and users;
- emergency contacts named by your workers;
- people named in incident reports, such as members of the public.
2.6 Kinds of personal data.
- identity and contact details: name, email, phone number, town;
- work profile: trades, skills, availability, travel radius, transport, how
the person is engaged for tax, payroll number, start and leaving dates;
- right-to-work records: the method of the check, its
date, who checked, whether the person said they are a British or Irish
citizen, the documents seen, the provider’s reference, when a
time-limited permission ends, a copy of the evidence, and a share code while
a check is in progress. These reveal nationality or immigration status;
- SIA licence records: licence number, type, role,
status, expiry, and each check recorded against it, with who looked, when and
what the answer was;
- security screening (BS 7858), where you use it: five
years of addresses and activity, references, a declaration of unspent
convictions, the result of a criminal record check and of a financial check,
and your decision;
- cards, certificates and other documents, with their files;
- bookings, offers, shifts, attendance with a location rounded to roughly a
hundred metres at clock-in, and, where a worker switches it on, the time they
crossed out of a site’s boundary;
- timesheets, hours, pay and charge rates, pay runs, payslips and
invoices;
- holiday asked for or paid, and days a worker is not available;
- late drop-outs: a shift a worker gave up inside your notice period, the
notice given and any reason added, and whether it was withdrawn;
- which site briefings and must-read documents a worker confirmed, and
when;
- agreements and signatures, including any address typed into an
agreement;
- incident records: the occurrence book, in the
reporter’s words, with photographs;
- welfare records: lone-working check-ins, missed checks
and alarms, carrying the worker’s phone number, emergency contact and
last-known place in words;
- emergency contacts: the name, phone number and email a worker gives for
them;
- patrol rounds, messages, notices and profile photos;
- the audit trail of who did what, and when;
- each user’s role and access in your workspace, and the notification
address of their phone. The sign-in account itself (email, password and
sign-in records) is ours as controller.
2.7 Special category and criminal offence data. Screening
files contain criminal offence data. Incident and welfare records can contain
health information, such as an injury, and allegations of crime.
2.8 What we do not receive. Some information is kept only in
a protected store on the device it was typed on and is never sent to us:
workers’ bank details, dates of birth, home addresses (except as part of a
screening file or typed into an agreement) and referees; National Insurance
numbers, CIS Unique Taxpayer References and other payroll identity details,
which stay on the device that prepares your payroll file; and any key for a
model account. This agreement does not
cover that information, because we never hold it.
3. Your instructions and your duties
3.1 Your instructions to us are the terms of service, this agreement, and
what your users do in Nelsah — the records they keep, the settings they
choose and the exports they make. You can give further instructions in writing.
Your instructions must comply with data protection law.
3.2 As controller, you are responsible for having a lawful basis for the
processing, for giving the people concerned a privacy notice, for any data
protection impact assessment the law requires, and for the accuracy of the
records your users keep.
4. Our duties
4.1 We process your personal data only on your documented instructions,
including about transfers outside the UK, unless UK law requires us to do
otherwise. In that case we tell you before we do, unless the law forbids
it.
4.2 We tell you straight away if, in our opinion, an instruction breaks data
protection law.
4.3 Everybody we authorise to process your personal data is bound to keep it
confidential.
4.4 We keep the security measures in Annex B in place,
and we keep them appropriate to the risk, as Article 32 of the UK GDPR
requires.
4.5 We do not sell your personal data, and we do not use it for our own
purposes.
4.6 We keep the record of processing that Article 30(2) of the UK GDPR
requires of a processor.
5. Sub-processors
5.1 You authorise us to use the sub-processors listed in
Annex A.
5.2 We will tell you by email at least 14 days before we add or replace a
sub-processor, and update Annex A. If you object on reasonable data protection
grounds within that time, we will discuss it with you in good faith. If we
cannot resolve it, you may end the terms of service without penalty, and we
will refund any fee you paid in advance for the time after the end.
5.3 Each sub-processor is bound by a written contract with data protection
obligations that give your personal data the same protection as this
agreement. We remain responsible to you for what our sub-processors do.
6. Transfers outside the UK
6.1 We transfer your personal data outside the UK only with a safeguard that
data protection law accepts: UK adequacy regulations (including the UK Extension
to the EU–US Data Privacy Framework, for a US organisation certified to
it), or the International Data Transfer Agreement or the UK Addendum to the EU
Standard Contractual Clauses. Annex A shows which applies to each
sub-processor, and you authorise those transfers.
7. Requests from the people the data is about
7.1 A request a worker makes in Nelsah, under Settings → Your
data & privacy, goes to your business to decide.
7.2 If somebody contacts us directly about records you control, including
with a complaint, we pass it to you promptly and within 5 working days. We do
not answer it ourselves except to tell them we have passed it on, unless you ask
us to.
7.3 We help you answer requests to exercise people’s rights, as far as
we reasonably can given the nature of the processing.
8. Breaches and other help
8.1 We tell you without undue delay, and in any case within 48
hours, after we become aware of a personal data breach affecting your
personal data. We tell you what happened, the kinds and rough number of people
and records concerned, the likely consequences, and what we have done or plan
to do about it, with a contact for more information. Where we do not have all of
that at once, we send it as we learn it.
8.2 We help you meet your own duties to report a breach to the regulator and
to tell the people affected. We do not report a breach of your data to the
regulator or to the people affected on your behalf unless you ask us to or the
law requires it.
8.3 We help you with security, with data protection impact assessments and
with consulting the regulator, taking into account the nature of the processing
and the information available to us.
9. When the service ends
9.1 While the terms of service last, your users can download what the
app’s own exports produce, such as pay runs, payslips, invoices and
accounting files, and you can ask us in writing for a copy of your records held
on our servers.
9.2 When the terms of service end, you can ask us in writing within 30 days
for a copy of your records held on our servers, in a machine-readable format,
with the files your users stored. We then delete your personal data from the
workspace and the file store within 60 days of the end, unless UK law requires
us to keep it. Copies in our suppliers’ backups are deleted as those
backups expire.
9.3 Some records belong to more than one Nelsah customer — for
example, hours a worker of yours worked on a site another customer runs. Those
stay available to the other customer as part of its own records.
10. Information and audits
10.1 We make available to you the information you reasonably need to show
that we meet this agreement, including Annex A, Annex B and our
sub-processors’ terms.
10.2 We allow for and contribute to audits, including inspections, by you or
an auditor you appoint who is bound by confidentiality. An audit is once in any
12 months unless it follows a personal data breach or a regulator requires it,
on 30 days’ notice, during working hours, at your cost, and without access
to any other customer’s data. We will first try to answer your questions
in writing.
11. Liability and law
11.1 The limits of liability in the terms of service apply to this
agreement.
11.2 This agreement is governed by the law of England and Wales, and the
courts of England and Wales have exclusive jurisdiction.
Annex A — Sub-processors
| Sub-processor | What it does | Where | Safeguard |
| Supabase, Inc. (United States) |
The database, the sign-in service, the private file store and the server functions behind the shared workspace |
Data stored in London, United Kingdom. Supabase’s own handling of it can take place outside the UK |
UK Addendum in Supabase’s data processing agreement |
| Resend, Inc. (United States) |
Sending service emails: address confirmation, password reset, and invitations to join your workspace |
United States |
UK Extension to the EU–US Data Privacy Framework where Resend is certified; otherwise the UK Addendum in Resend’s data processing agreement |
| Netlify, Inc. (United States) |
Hosting the website and the office and client pages. It sees the address each browser connects from; the pages fetch records from the workspace directly, not through Netlify |
United States and its worldwide network |
UK Extension to the EU–US Data Privacy Framework, to which Netlify says it is certified |
Switched on by a key, not yet by default. Apple’s push
notification service receives personal data from us (a notification’s
short text and a phone’s notification address) only once the push
sending key is installed on our server; until then it receives nothing, and
we give notice under clause 5.2 before that changes. Apple distributes the
iPhone and iPad app under its own terms, and is not our sub-processor for
that. Automatic SIA licence checks through SIA Verify (siaverify.co.uk) are
built in, and a company’s Owner can switch them on from the website; a
licence number leaves our server only once it is connected to SIA Verify,
which we do only after a written data processing agreement with SIA Verify
and after adding it to this Annex, with notice under clause 5.2. [FOR MARTIN:
state whether the push sending key and the SIA Verify connection are in place
at launch; if either is, update this Annex and the privacy policy before
launch.] Our hosted assistant, Hermes, and any AI model provider for it, are
not switched on either. Before any of these is used for your data, we will
give you notice under clause 5.2.
Services you choose. If you point Nelsah’s assistant
at a computer in your own office or at your own account with an AI model
provider, or send Nelsah’s exports to an accounting or payroll
package, that service is one you chose and contract with yourself. It is not our
sub-processor.
Annex B — Security measures
A summary of the technical and organisational measures in place at the date
above.
- In transit. Everything between the app, the web pages and
the workspace travels over an encrypted connection to our own project, and
the app will not follow a redirect anywhere else. The app connects elsewhere
only when a user asks it to: to an assistant service you chose, or to a
company’s own website to fetch its logo. The website loads
no third-party code, and its security headers allow it to connect to the
workspace and nowhere else.
- On the server. Customers’ records are held in one
shared database, and the separation between customers is enforced by the
server, not by separate databases. Somebody who is not signed in can read
nothing. Signed-in users cannot read or write the workspace tables directly:
every read and write of a record goes through server functions that check who
is asking and work out, record by record, what that person may receive. A
figure a person is not entitled to comes back blank. A login that only belongs
to a client never receives lone-working records. A file can be uploaded only
to a place the server has first reserved for that record and that person.
- Inside your business. What a user sees depends on their
role. Right-to-work records, documents and licence checks go to people whose
job is compliance; pay rates go to people who handle money.
- Passwords. Handled by the sign-in service. They are never
workspace fields: the server strips them from every answer and refuses any
attempt to write one.
- Files. Kept in a private store with no public or
shareable links. Every download is checked, at the moment it is asked for,
against the record the file belongs to.
- Audit trail. Every consequential action is recorded with
who did it and when, and your Owner can read the trail.
- On devices. The app relies on iOS encryption. Bank
details, dates of birth, home addresses, referees and payroll identity details
are kept in protected stores on the device, out of the device’s backup.
Sign-in can be protected with Face ID, Touch ID or the device passcode.
- Collecting less. Location is taken once, at clock-in,
rounded to roughly a hundred metres, with no location history. The optional
site-boundary clock-out records only the time the worker crossed out.
Notifications carry no pay, addresses, licence numbers or other people’s
names.
- Our suppliers. Supabase encrypts the data it stores.
- People. Access to the production systems is limited to the
two owners of N&Q Technology, each bound by a written
confidentiality undertaking.