Skip to main content
Back to articles
Published 29 April 2026Updated 3 min readCall recording

How to Record Customer Calls Without Breaking GDPR

A practical checklist for companies: recording notices, purpose, legal basis, retention, access control, transcription, and deletion.

R
Robert Mater

TL;DR: business call recording can be lawful, but a recording app is not enough. You need a purpose, notice, legal basis, access control, retention, and a deletion process.

Define the purpose

Start with why you record:

  • confirming customer agreements,
  • handling complaints,
  • quotes and appointments,
  • transaction security,
  • team training,
  • capturing missed inquiries.

Do not record "just in case" without a clear purpose.

Inform the caller

A practical notice can be simple:

"This call may be recorded to handle your inquiry, confirm arrangements, and improve service quality. Details are available in our privacy policy."

It should say that recording happens, why it happens, and where the caller can find more information.

Companies commonly consider consent, legitimate interest, or necessity connected with a contract. Do not copy another company's answer blindly. Training, complaints, and proof of arrangements can require different analysis.

Set retention

Do not keep recordings forever by default. Define a retention period, such as 30, 90, or 180 days, depending on the purpose. Complaints may justify longer retention than ordinary inquiries.

Limit access

Use:

  • named accounts,
  • access only for people handling the customer,
  • access logs,
  • deletion/export procedures,
  • no recordings stored on private employee phones.

Transcripts are personal data too. Treat them like recordings.

Implementation checklist

  1. Write down the purpose.
  2. Prepare the notice.
  3. Update the privacy policy.
  4. Define retention.
  5. Restrict access.
  6. Sign a DPA with the vendor.
  7. Prepare deletion and export procedures.
  8. Test that the notice actually plays.

Why a business system helps

A phone app can record, but the company may lose control over files. A business system makes it easier to manage notice, access, retention, and deletion.

Heilo never talks to the caller. New numbers start in the “Announcement before the call” mode, and you can change the wording; the other modes are “You tell them during the call” and “No announcement”, and in every mode recording starts when the call is answered. Heilo gives you the tools to inform the caller (a notice, your own wording, a call label). Your company, as the data controller, provides the legal basis and meets the duty to inform. Heilo keeps a recording for 365 days by default and then deletes it; the transcript stays, and the period cannot be changed in the dashboard. A call moved to the trash is erased 30 days later together with its recording, transcript and summary; an entry with the number, date and notes remains. Heilo uses the subprocessors listed in the terms, including Twilio (telephony, a US company), Supabase (database in the EU), Vercel (hosting) and Google Gemini (transcription and analysis).

Conclusion

GDPR does not automatically ban call recording. It requires transparency, proportionality, and control. Treat recording as a business process, not a private phone feature.

Need call recording with notice, transcription, and access control? See Heilo business call recording. For more detail: business call recording laws.