Security

Why Payroll Data Should Never Leave Your Browser

GDPR, client confidentiality and the case for browser-only payroll processing for UK accountants and bookkeepers.

Updated 14/06/2026 · 5 min read

Payroll files contain some of the most sensitive personal data your practice handles: names, NI numbers, salaries, pension contributions. Any tool that ingests them becomes a data-processing risk.

The browser-only principle

MS Payroll Bridge parses payroll files locally in your browser. No payroll CSV is uploaded to a server. No copy is retained. The only thing that leaves your machine is the journal CSV you download — and only you ever see it.

What this means for GDPR

  • No third-party data processor for payroll content — fewer DPIA considerations.
  • No data-breach exposure for files we never received.
  • Client confidentiality preserved by default.

Frequently asked questions

How can I verify the file isn't uploaded?

Open your browser's network tab during a conversion — you'll see no upload of the CSV body. Only standard page assets are fetched.

Are you a data processor for payroll content?

No. We never receive payroll content, so we cannot process or store it.

Convert your next pay run in seconds

MS Payroll Bridge turns Moneysoft CSVs into balanced Xero, QuickBooks, Sage and FreeAgent journals — all in your browser.

Or browse more guides in the Resources hub.