The UK analogue phone network is retired by 31 January 2027.

Compliance

Call recording law in the UK: a compliance checklist for businesses

UK businesses can record calls for defined purposes if they meet the conditions in the regulations, tell callers and staff, and follow data protection and card rules. This guide includes a checklist. General information, not legal advice.

Last reviewed 21 November 2026 · 8 min read

UK businesses can record calls for the business purposes listed in regulations, but only if the recording meets the conditions in those regulations, people who may use the system have been told, and the recordings are handled lawfully under data protection law. The ICO says callers must be told that the call is being recorded and why, and that a recorded message is good practice. Card security codes must never be kept once a payment is authorised.

This is general information, not legal advice. The rules depend on your sector, what you record and why. If you are unsure, take advice from a qualified solicitor or your regulator. All sources are cited below so you can read the primary text.

Key takeaways

  • Recording is allowed for specific business purposes set out in regulations, and only if you have made all reasonable efforts to inform people who may use the system.
  • Data protection law applies to recordings that contain personal data. The ICO expects recording to be necessary, proportionate and transparent.
  • Tell callers and staff: a recorded announcement is good practice, and your privacy information must cover it.
  • Do not store card security codes. PCI DSS prohibits storing sensitive authentication data after authorisation, even if encrypted.
  • Write down your purpose, retention period and who can listen, and review them.

The legal framework in plain English

Three layers sit on top of each other.

1. The interception rules. The regulations that deal with business call recording treat it as interception of a communication in the course of its transmission, and authorise it only in defined circumstances. The current set is the Investigatory Powers (Interception by Businesses etc. for Monitoring and Record-keeping Purposes) Regulations 2018. Regulation 3 says conduct is authorised "for the purpose of section 46(1) of the Act" if it meets the conditions in that regulation and regulation 4.

2. Data protection law. Where recordings contain personal data, UK data protection rules apply as well. The ICO's guidance on monitoring workers states that data protection law does not prevent workplace monitoring, but it must be lawful, transparent and fair. It treats call recording as monitoring.

3. Sector and card rules. Some regulated sectors have their own recording rules, and card payments are covered by the PCI DSS industry standard. Check with your regulator and your card acquirer.

Which purposes are allowed

Regulation 3(2) of the 2018 Regulations lists the purposes for which businesses may monitor or keep a record of communications. Paraphrasing the regulation text:

  • To establish the existence of facts, for example what was agreed on a call.
  • To check compliance with regulatory or self-regulatory practices or procedures that apply to the business.
  • To ascertain or demonstrate the standards achieved or that ought to be achieved by people using the system in the course of their duties, which covers training and quality.
  • In the interests of national security.
  • To prevent or detect crime.
  • To investigate or detect unauthorised use of the telecommunication system.
  • To secure, or as an inherent part of, the effective operation of the system.

Regulation 3(3) also allows monitoring to decide whether communications are relevant to the business, and 3(4) covers free, anonymous confidential counselling services.

Regulation 4 sets the conditions that must also be met. Regulation 4 says the recording must be made solely to monitor or keep a record of communications relevant to the business's activities, the system must be provided for use in connection with those activities, and the system controller must have made all reasonable efforts to inform every person who may use the system that communications may be intercepted. For some purposes, regulation 4(2) adds that conduct is authorised only to the extent permitted by Article 5 of Directive 2002/58/EC, as the regulation was written.

What about the 2000 Regulations?

Older guidance often cites the Telecommunications (Lawful Business Practice) (Interception of Communications) Regulations 2000. The legislation.gov.uk page for those Regulations shows only the original version and describes them as authorising certain interceptions that section 1 of the Regulation of Investigatory Powers Act 2000 would otherwise prohibit. We could not confirm from that page whether they are still in force, so treat references to them as dated and rely on the 2018 Regulations, which authorise conduct for the purpose of section 46(1) of the Investigatory Powers Act. A solicitor can confirm the current position for your circumstances.

What the ICO expects

The ICO's monitoring guidance has a section on telephone calls. Key points, quoting the ICO:

The ICO's wider monitoring guidance says employers should set a clear purpose, use the least intrusive means, make workers aware in plain language, have a lawful basis, keep only relevant information, consider a Data Protection Impact Assessment where there is a likely high risk, and provide recordings on a subject access request. It adds that monitoring must be necessary, proportionate and respect workers' rights.

The ICO pages we read did not set a fixed retention period. Set your own, justify it and apply it.

Card payments over the phone

If staff take card details by phone, recording can capture them. The PCI Security Standards Council FAQ says that PCI DSS Requirement 3.3.1 prohibits storing sensitive authentication data after authorisation, even when encrypted, and that recording card validation codes such as CVV2 or CID in audio files is therefore a violation. It says:

  • Try to prevent the data being recorded, using audio suppression or redaction where available.
  • If it cannot be prevented, delete it securely straight after authorisation.
  • If that is not possible, compensating controls are required and are validated in annual assessments.
  • PCI DSS does not override local audio retention laws.

In practice, many businesses use a pause-and-resume feature or an automated payment line. Ask your provider and card acquirer how they handle this. See call recording for what to look for in a system.

Compliance checklist

Use this as a starting point and adapt it to your sector.

StepWhat to doWhy
1. Define the purposeWrite down why you record (evidence, training, quality, compliance)Regulation 3 purposes; ICO proportionality
2. Decide what to recordRecord only the lines or roles that need it; avoid blanket recordingICO says recording all calls is not usually proportionate
3. Choose a lawful basisRecord it in your data protection documentationICO expects a lawful basis
4. Assess riskDo a DPIA if recording is likely to be high riskICO monitoring guidance
5. Tell callersPlay a short announcement at the start of the callICO: tell callers you are recording and why
6. Tell staffUpdate contracts, policies and your privacy informationRegulation 4: all reasonable efforts to inform users; ICO
7. Protect card dataPause or mask card details; never store security codesPCI DSS Requirement 3.3.1
8. Limit accessRestrict who can listen and log accessData protection; PCI compensating controls
9. Set retentionPick a period, justify it, and delete on scheduleKeep only relevant information
10. Handle requestsBe able to find and provide recordings on a subject access requestICO monitoring guidance
11. Choose a provider carefullyCheck where recordings are stored and what the contract saysYour responsibilities remain with you
12. Review yearlyRe-check purpose, retention and scriptsRules and risks change

Example call announcement

A short script works better than a long one. For example: "Calls may be recorded for training and quality purposes. Our privacy notice is on our website." Adapt the wording to your real purpose and make sure the notice it points to is accurate.

Common mistakes

  • Recording everything by default without a stated purpose.
  • No announcement on inbound lines, or one that only appears on the website.
  • Forgetting staff and their rights as well as callers.
  • Capturing card numbers and security codes and leaving them in storage.
  • Keeping recordings indefinitely because storage is cheap.
  • Relying on provider defaults for retention and access.
  • Treating consent as the only thing that matters. The regulations and the ICO guidance set out purpose, transparency and proportionality conditions as well.

Buying a system with recording

When comparing providers, ask whether recording is included or an add-on, where recordings are stored, how long they are kept, who can access them, whether announcements and card-pause are supported, and how you export or delete a recording. Some plans include it only on higher tiers; BT's Extra package, for instance, lists call recording with one-year storage. See business phone system cost, the law and accountancy page and quote tool to compare options.

Related terms: PBX, IVR.

Sources

All pages fetched and read on 21 November 2026.

This is general information, not legal advice.

Related solutions and terms

Glossary: PBX, IVR, VoIP.

Frequently asked questions

Can a UK business record phone calls?

Yes, for the purposes listed in regulation 3 of the Investigatory Powers (Interception by Businesses etc. for Monitoring and Record-keeping Purposes) Regulations 2018, such as establishing facts, checking compliance, training and quality, or preventing crime, provided the regulation 4 conditions are met. This is general information, not legal advice.

Do I have to tell callers I am recording?

The ICO says you must tell people that you are recording the call and why, and that a recorded message is good practice. Regulation 4 also requires all reasonable efforts to inform every person who may use the system.

Do I need consent from staff?

The regulations require reasonable efforts to inform users, and the ICO says workers must be told in your privacy information and that monitoring must be lawful, transparent, necessary and proportionate. Which lawful basis applies depends on your circumstances, so take advice.

Can I record card details taken by phone?

Not if it means storing the security code. The PCI Security Standards Council says PCI DSS Requirement 3.3.1 prohibits storing sensitive authentication data after authorisation, even when encrypted. Use pause-and-resume, redaction or an automated payment line.

How long can I keep recordings?

The ICO pages we read set no fixed period. Choose a retention period linked to your purpose, justify it, document it and delete on schedule.

Are the 2000 Lawful Business Practice Regulations still the rule?

The legislation.gov.uk page shows only the original 2000 version and we could not confirm its current status from that page. The 2018 Regulations authorise conduct for the purpose of section 46(1) of the Investigatory Powers Act, so rely on those and take advice.

Before you sign anything

Compare total cost over the contract term, confirm number porting in writing, and check what happens if you add or remove users. Our quote form sends the same requirements to up to three providers so the answers are comparable.