Skip to content
Spark

Your system and your data, looked after properly

Every system we build keeps your data in places we name, behind sign-ins you control, with backups we test and a record of who did what. This page sets out how we build and run it, what happens if something goes wrong, and how you’d take it all with you if you left.

Your data lives where we say it does, and it’s encrypted there

We keep your data inside the accounts you already run where we can, otherwise with an established cloud provider in the UK or EU, and it’s encrypted while it moves and while it’s stored.

  • Where it can, the system keeps your data inside the Microsoft 365 or Google Workspace account you already have, under the controls you already run.
  • Anything we host sits with an established cloud provider in the UK or EU, and we name the provider and the location in writing before we build.
  • Data is encrypted while it moves between systems and while it’s stored.
  • Passwords and keys for your connected tools are kept in a secure store that only the system can read, out of the code and out of everyday view.
  • Each system holds only the data it needs, and we document where your data flows so you can check it.
  • If you need data kept somewhere specific, tell us at the start and we’ll be straight about what that changes.

Your data is backed up automatically, and we test the restore

Backups run on a set schedule and sit apart from the live system for an agreed period, and we prove on a regular schedule that we can restore them.

  • Backups run automatically, on a schedule written into your agreement.
  • Backups are stored separately from the live system, so one problem can’t take out both.
  • We keep them for an agreed period, so we can go back to a point before a mistake was made.
  • We test restoring from backup on a regular schedule and keep a record of each test.
  • Where your data lives in Microsoft 365 or Google Workspace, we check what those services keep and add our own backup where they fall short.

Only the right people get in, through single sign-on and multi-factor sign-in

Your team signs in with the work accounts you already manage, with multi-factor sign-in on and a role for each person that sets what they can see and do.

  • Single sign-on with Microsoft or Google wherever your tools support it, so one work account controls access.
  • Multi-factor sign-in is on as standard, so a stolen password alone won’t get anyone in.
  • Each person has a role that decides what they can see and change, and you decide who has which.
  • When someone leaves, switching off their work account locks them out of the system too.
  • We review who has access with you on a regular schedule and remove what’s no longer needed.

Every change is recorded, so you can show who did what and when

The system keeps an audit trail of who created, changed, approved or deleted each record, and you can search it and export it.

  • Each record carries its history: who created it, who changed or approved it, and when.
  • Sign-ins, and changes to access and settings, are logged as well.
  • Everyday users can’t edit or delete the trail, so it stays a record you can rely on.
  • You can search it and export it for an auditor, a regulator or a dispute with a client.
  • The system keeps the records, and your business stays responsible for its own compliance.

Every change is reviewed and tested before it reaches your live system

We review every change, test it in a separate environment, release it in a controlled way and keep the software underneath up to date.

  • Every change to the code is reviewed by a second person before it’s released.
  • Changes are built and tested in a separate test environment, away from your live system and your live data.
  • Releases are planned and logged, and we can roll one back if something isn’t right.
  • We keep the software libraries your system depends on up to date and apply security fixes promptly.
  • We can work to your security questionnaire, and arrange independent penetration testing with a specialist firm on request.
  • We fix what testing finds and show you what changed.

At Spark, only the people working on your system can reach it, and every access is logged

Our own people get the least access the work needs, we log it, and confidentiality is in writing before we start.

  • Only the people working on your system get access, and only to the parts their work needs.
  • Our own accounts use multi-factor sign-in, and every access to your system is logged.
  • Access is removed as soon as someone no longer needs it.
  • Everyone at Spark, and anyone we bring in to help, is bound by a confidentiality agreement, and we tell you before anyone outside Spark works on your system.
  • We sign an NDA with you before we see anything sensitive, and a data processing agreement before we handle any personal data.

AI only sees what the task needs, and a person approves anything that matters

Where a system uses AI, we write down what it does, what data it sees and who checks it, and your data isn’t used to train anyone’s models without your written agreement.

  • We use AI providers on business terms that don’t use your inputs for training, and we check those terms for each tool.
  • Each AI step sees only the data its task needs, and that’s set out in your system’s documentation.
  • A named person in your team approves anything that matters before it goes out.
  • Very sensitive data can be kept out of AI steps altogether, or kept inside your own environment.
  • You can switch any AI step off.

If something goes wrong, we tell you quickly and help you put it right

We follow a written incident plan, keep you informed from the start and help you decide whether to report it to Jersey’s data protection regulator.

  • Our written incident plan covers finding out what happened, containing it, fixing the cause and keeping a record.
  • We tell you without undue delay once we know your system or data is affected, and keep you updated until it’s resolved.
  • If personal data is involved, we give you the facts you need to decide whether to report it to the Jersey Office of the Information Commissioner (JOIC), or the ICO in the UK, and help you prepare the report.
  • The law expects a reportable breach to reach the regulator within 72 hours of you becoming aware of it, where feasible, so we move fast.
  • Afterwards we write up what happened and what we’ve changed so it doesn’t happen again.

If you leave, you take everything with you

Your data, code and documentation are yours, and if you move on we hand them over properly and delete our copies.

  • You can export your data at any time, in formats other software can read, such as CSV or Excel.
  • Everything is documented in plain English, so another capable team could pick it up.
  • We build in accounts you own wherever we can, and transfer any we hold for you when you go.
  • On the way out we hand over the code, admin access and a full data export, and walk your new team through how it fits together.
  • Once the hand-over is done, we delete our copies of your data and confirm it in writing.
  • The notice period and hand-over steps are written into your agreement.

The system keeps the records and controls your business needs; your business stays responsible for how it uses them, and for its own regulatory duties. If you have a security questionnaire, send it over and we’ll work through it with you.

Questions about security and data

  • Yes, and we’ll show you how instead of asking you to take it on trust. Every system gets the same basics: multi-factor sign-in, access by role, encryption, backups we test and a record of who did what. We sign an NDA before we see anything sensitive, and our security page sets out the detail.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.