Field notes on GDPR, written for people on the operations side. I am not a lawyer, and nothing here replaces your client’s legal team or your own. But operations managers are the ones who get audited on the floor, so you need the working model.

First, what it is

GDPR is the European Union’s General Data Protection Regulation, in force since May 2018. It protects personal data of people in the EU. It applies to organisations outside Europe in some situations, including when they handle such data on behalf of a European business. An Indian BPO handling support calls for a German telecom is exactly this case. You do not need an office in Europe for it to matter.

The only distinction you must get right

GDPR separates a controller from a processor. The controller decides why and how personal data is used. The processor handles it on the controller’s instructions. In a normal outsourcing deal, the German telecom is the controller and you are the processor.

My opinion: most BPO compliance confusion comes from teams acting like owners of data they only hold. A processor does not decide to keep call recordings for an extra year because “it might be useful”. It does not reuse the customer list for another client’s campaign. It does what the contract says, and where the contract is silent, it asks.

Role depends on the facts, not on what the contract is titled. If a BPO starts deciding purposes of its own, say building its own analytics product from client data, it can become a controller for that activity, with heavier duties.

What the contract must contain

GDPR requires a written agreement between controller and processor (Article 28). In practice it is called a data processing agreement, or DPA, and it sits next to your MSA and SOW. It covers what data and which purposes, confidentiality obligations on staff, security measures, rules about sub-processors, help with data subject requests, deletion or return at the end, and the client’s right to audit.

The sub-processor point catches BPOs out. If you use a cloud telephony vendor, a quality-analytics tool or a second BPO site that touches the data, the client usually must approve it, and you must flow the same obligations down. “We just added a tool” is not a minor change.

Data crossing the border

Sending EU personal data to a country outside the EU needs a legal basis. The European Commission has declared some countries “adequate”; to my knowledge India is not on that list, so verify the current position. For India the usual route is standard contractual clauses, approved by the Commission, signed between the parties, often supported by an assessment of the risks in the destination country. This is why a European client’s security questionnaire looks heavier than a domestic one.

What lands on the floor

  • Data subject requests. A customer may ask what data a company holds, ask for correction or ask for erasure. The controller must generally respond within one month. You are not the one to decide, but you must pass requests to the client quickly and support retrieval. An agent who receives such a request on a call needs a clear script: do not promise anything, log it, route it.
  • Breach notification. A controller must usually notify the supervisory authority within 72 hours of becoming aware of a breach. A processor must notify the controller without undue delay. Your client’s clock may start when you tell them, so hiding a breach for two days costs them most of their window.
  • Minimisation and retention. Collect and keep only what the purpose needs. Recordings and screen captures that pile up forever are a risk, not an asset. Agree retention periods in writing and make the deletion job real.
  • Access control. Only people who need the data should see it. Review access when someone changes process or leaves.
  • Training and records. Staff handling the data should be trained, and you should be able to show it with dates.

The penalty talk

The headline numbers are fines up to 20 million euros or 4 per cent of worldwide annual turnover for the most serious infringements, whichever is higher, with a lower tier for others. Those are ceilings. Most clients fear the practical outcomes more: a failed audit, a contract termination, or being dropped from a vendor panel. Processors can also be held directly responsible for some obligations, so “the client is the controller” is not a shield.

Mistakes I would watch for

Using real customer data in training or testing without permission. Letting agents keep notes in personal notebooks or phones. Sending a screenshot with customer details into a team chat group. Treating a recording as “ours” when the contract says it belongs to the client. Each one is common, and each is a processor acting like a controller.

One more point of friction: India has its own law now, the Digital Personal Data Protection Act, 2023. The two do not match term for term, and a BPO serving both European and Indian customers must satisfy whichever applies to each dataset. Do not assume that meeting one means meeting the other.

If you remember one sentence, make it this: find out which role you hold for each client, then do what the data processing agreement says and nothing extra.

Leave a Reply

Trending