# The Data Protection (Jersey) Law 2018 and your systems: what it asks, and how a good system helps

Published 20 October 2026 by Spark · Security and data · 6 min read
Canonical: https://hellospark.co.uk/writing/data-protection-jersey-systems

> Jersey’s data protection law expects every business to know what personal data it holds, why and where, and to act quickly on requests and breaches. A well-built system keeps the records that make that easier. Your business stays responsible.

The Data Protection (Jersey) Law 2018 expects every business that handles personal data to know what it holds, why it holds it, where it’s kept and who can see it, and to act quickly when someone asks for their data or something goes wrong. Most small businesses find that hard because their data is spread across inboxes, spreadsheets and several tools. A well-built system makes it much easier by keeping that information in one place, with a record of what happened to it. It won’t make you compliant on its own: the system keeps the records, and your business stays responsible.

A note before we start: this is our practical reading, not legal advice. The Jersey Office of the Information Commissioner (JOIC) publishes guidance for businesses, and that’s where to check the details, which do change.

## Jersey’s law follows the same pattern as the GDPR

Jersey’s law came into force in May 2018, at the same time as the EU’s GDPR, and follows the same broad shape: the same core principles, similar rights for individuals and similar duties for businesses. If you’ve worked with UK GDPR, most of it will feel familiar. There are local differences, though, so don’t rely only on UK material. One example: Jersey treats information about a person’s criminal record or alleged criminal activity as special category data, which matters if you run background checks on staff.

The regulator is the JOIC. Businesses established in Jersey that handle personal data generally need to register with it, so if you’re not sure whether yours has, check the JOIC’s website.

In the law’s terms, your business is usually the controller: you decide what personal data you hold and why. Anyone who handles it on your behalf, including whoever builds and runs your system, is a processor, and should sign a data processing agreement with you before handling any of it.

## You need a lawful basis for each way you use personal data

For each purpose you use personal data for, you need a lawful basis. Common ones are that it’s needed for a contract with the person, that the law requires it, that you have a legitimate interest that isn’t outweighed by theirs, or that they’ve consented. Special category data, such as health information, needs an extra condition on top.

**How a system helps:** when a system is designed properly, each piece of personal data is there for a stated reason. The customer’s address is there so you can do the job and invoice it. An engineer’s qualifications are there because you need to show they’re certified. Writing those reasons down during design gives you much of what you need for your own records, and it stops the system collecting data just in case.

## You should be able to show what you hold and why

The law expects you to be able to demonstrate how you handle personal data. In practice, the clearest way to do that is a written record of what personal data you hold, what it’s for, where it’s stored, who it’s shared with and how long you keep it.

**How a system helps:** if your client and job records live in one system instead of six, that record is far easier to write and to keep accurate. The system’s own documentation lists every tool it connects to and what data passes between them. Retention can be built in too, so old records get flagged for review or deletion once they pass the period you’ve chosen.

## People can ask for their data, and you have to find all of it

Individuals have rights over their personal data, including the right to see what you hold about them (a subject access request), to have it corrected, and in some circumstances to have it erased. There’s a time limit for responding. Check the JOIC’s guidance for the current deadline and the cases where it can be extended.

For most small businesses, the hard part is finding everything. A customer’s details might be in the CRM, the job app, Xero, three email inboxes, a WhatsApp chat and a spreadsheet on someone’s laptop.

**How a system helps:** with one record per customer, linked to their jobs, documents and messages, a search starts in one place and shows you where else their data lives. Exporting it takes minutes. Erasure is controlled: the system can remove or anonymise what should go while keeping what you still have a reason to hold, such as invoices you need for your accounts, with a record of what was done.

## Breaches have to be reported to the JOIC quickly

If personal data is lost, stolen, sent to the wrong person or seen by someone who shouldn’t have it, that’s a personal data breach. You must report it to the JOIC without undue delay, and where feasible within 72 hours of becoming aware of it, unless it’s unlikely to put anyone at risk. Where the risk to people is high, you also need to tell them. Check the JOIC’s guidance on how to report.

That isn’t long when you first have to work out what happened.

**How a system helps:** an audit trail shows who saw or changed what, and when, so you can work out quickly what was affected. Access by role means one compromised account can only reach what that person needed. Signing in through your Microsoft 365 or Google Workspace accounts with multi-factor sign-in makes a breach less likely in the first place. The [security questions to ask your builder](/writing/is-a-bespoke-system-secure) cover these in more detail.

## Data held outside Jersey needs the right protection

Many of the tools Jersey businesses use store data in the UK, the EU or the US. The law restricts sending personal data outside Jersey unless the destination gives adequate protection or the right safeguards are in place, usually through your contract with the provider. The JOIC’s guidance sets out which countries count and which safeguards work, and it can change, so check there before you rely on a provider.

**How a system helps:** a good builder tells you in writing where each part of the system runs and where your data is stored. Your documents can stay in your own SharePoint or Google Drive, anything hosted can sit in a location you’ve agreed, and you get a list of every outside service that touches personal data, which is what you need to check your transfers.

## Some duties stay with you whatever the system does

A system keeps records, controls access and makes requests quicker to answer. It can’t choose your lawful basis, write your privacy notice or decide whether a breach needs reporting. Those stay with your business. Someone on your team should own data protection, know where the system’s records are, and know when to ask for advice. If you use AI tools as well, the same rules apply, as we set out in [AI and data protection](/writing/ai-data-protection-uk-gdpr-jersey).

## Our recommendation: design data protection in from the start

The cheapest time to make data protection easier is when the system is designed. Decide what data each part needs and why, where it will be stored, who can see it and how long it’s kept, and build those decisions in. Adding them afterwards costs more.

If you’d like to talk through how your current tools handle personal data, and what a joined-up system would change, [book a review](/book-a-review). It’s a free 30-minute call with Mark or me. We’re not lawyers, so for legal questions we’ll point you to the JOIC or your adviser, but we can show you where your data lives and how to keep track of it.
