ChamberOne

Sri Lanka: the Personal Data Protection Act and AI tools in law firms

By the ChamberOne team 5 minute read

Sri Lankan law firms hold large amounts of personal data: names, addresses, identity numbers, financial records, medical details and family circumstances. When a firm sends some of that text to an AI service, the data leaves the firm's own systems and may leave the country. The Personal Data Protection Act is the main statute that bears on this. This article explains in general terms how a careful firm should think about it. It is not legal advice, and the law and its commencement should be checked against official sources.

Key points

  • Check which provisions of the Personal Data Protection Act, No. 9 of 2022 are in force and read the official sources, not summaries.
  • A firm remains answerable for client data it passes to an AI supplier, including data sent abroad.
  • Keep an approved-tools list, ban free public tools for client material and minimise identifiers before text leaves the firm.
  • Record your reasoning, plan for incidents and follow the Authority's guidance as it develops.

What the Act is, and what to confirm yourself

Sri Lanka enacted the Personal Data Protection Act, No. 9 of 2022. According to the website of the Data Protection Authority, the Act provides a framework for the processing of personal data in the private and public sectors and established the Authority to oversee its implementation and enforcement.

Two things need checking by the reader. First, which provisions are in force now, since a statute can be brought into operation in stages. Second, whether any amending legislation or regulations have changed the text. Look at the official gazette notices and the Authority's own website, and take advice if your firm's position turns on the answer. Nothing in this article states what the Act requires of you.

Why law firms are in scope as a practical matter

A law firm decides why and how it processes client and third-party personal data. In data protection language that role is often called a controller. Whatever the label in the Act, the practical consequence is that the firm is answerable for what happens to the data, including when it hands text to a supplier.

Law firms also hold categories of information that are especially sensitive in most data protection systems: health, criminal allegations, family matters and financial detail. Treat those with more care than ordinary correspondence, and check how the Act treats such categories.

What happens when client data goes to an AI service

Using an AI service usually means sending text to a provider, often outside Sri Lanka. That raises the questions a careful firm should ask every time.

  • Which provider receives the text, and which companies does it use to process it?
  • In which countries is the text processed and stored?
  • Is it kept after the request, and for how long?
  • Can it be used to train models, and under what contractual terms?
  • Who at the provider can read it, and under what conditions?
  • What happens in a security incident, and how will the firm be told?

Transfers outside the country

Many AI services are hosted abroad. Data protection statutes often have specific provisions on transfers of personal data to other countries, and the PDPA may do so as well. Read the relevant provisions and any rules or guidance issued under them, and check whether they apply to the way your firm uses a given tool.

Because guidance is still developing, a prudent firm records its reasoning. A short note saying what was assessed, what was decided and why is useful if the question is later asked by a client or the Authority.

Controls that make sense now

Whatever the final shape of guidance, several controls are sensible and cost little. They also fit the duty of confidentiality that lawyers owe clients, which exists apart from the Act. Check the guidance from your professional body on confidentiality and technology.

  1. 1

    Keep a list of approved tools and ban the use of free public AI tools for client information.

  2. 2

    Decide what may never be entered: identity numbers, medical records, privileged advice and anything under a court restriction.

  3. 3

    Minimise: remove names and identifiers or replace them with placeholders before text goes to a tool, wherever the task allows it.

  4. 4

    Use contracts or terms with the provider that address retention, training use and security, and keep copies.

  5. 5

    Prefer tools that let you choose or switch off AI features, and that log who used them.

  6. 6

    Restrict access, so that sensitive matters are visible only to those who need them.

  7. 7

    Train staff, including support staff, on what may be pasted into which tool.

Do
  • Keep a list of approved tools
  • Decide what may never be entered
  • Remove names and identifiers where the task allows
  • Train staff, including support staff
Don't
  • Use free public AI tools for client information
  • Enter identity numbers, medical records or privileged advice
Controls for AI tools and client data

Client information and consent

Think about what you tell clients. Your engagement terms and privacy notice should say, in plain words, how the firm uses technology with their information. Some clients, particularly institutions, will ask for restrictions, and you should record those on the matter file in a place every fee earner can see.

Where the Act or your professional rules call for consent or notice in particular circumstances, check them before you rely on a general statement. If in doubt, ask the client, and keep the answer.

Incidents, records and rights of individuals

Plan for the day something goes wrong. Who decides whether a leak has occurred, who informs the client, and who deals with the Authority or the person affected? Write a short response plan and practise it once. Check the Act for any duty to report incidents, and for the rights that individuals have over their data, such as access and correction, so that you can handle a request without improvising.

Keep records of what personal data the firm holds, where it is stored and which suppliers see it. A simple register, kept up to date, answers many questions at once and makes assessment of a new tool far quicker.

Watching the guidance

Assign someone to follow the Authority's publications and any gazette notices. When new guidance appears, review your policy against it and note the date. Join your bar association's discussions, since collective questions to regulators tend to get answers.

The honest position is that some points are unsettled. A firm that has a clear policy, sensible controls and written reasons is in a far better position than one that has not thought about the issue, whichever way the guidance turns out.

Keep the policy short enough that people read it. Two pages with a one-page checklist will be used; twenty pages will not. Date every version and keep the old ones, so you can show what the firm's position was at the time a particular piece of work was done.

Sources

  1. Data Protection Authority of Sri Lanka

This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.

Read next

Sri Lanka PDPA and AI tools in law firms | ChamberOne