Skip to content

GDPR for law firms GDPR in the firm: what you have to do, in short.

A law firm processes personal data in every case, often sensitive data. Here are the obligations that come up in daily work and how they relate to the software you use.

In short

  • As a rule, the firm is the controller for the data of its clients and of the other people in its cases. Software vendors that process it on the firm's behalf are processors.
  • A data processing agreement is signed with every processor (Article 28).
  • Security is chosen according to the risk (Article 32): access control, encryption, backups, logs.
  • A personal data breach is notified to the authority within 72 hours at most, if it may result in a risk to individuals (Article 33).

The firm's role: controller

The controller is the one who determines the purposes and means of the processing (Article 4(7) of the GDPR). The firm decides what data it asks the client for, how it uses the data in the case and how long it keeps it. As a rule, then, it is the controller.

Vendors that process data on the firm's behalf are processors: practice software, e-mail, document storage, invoicing, AI assistants.

The bases met most often in a firm:

  • performance of the contract with the client (Article 6(1)(b));
  • a legal obligation, such as tax obligations (Article 6(1)(c));
  • legitimate interests (Article 6(1)(f)), for example for the opposing party's data.

For special categories of data, such as health data, Article 9(2)(f) allows the processing that is necessary for the establishment, exercise or defence of legal claims. Data on criminal convictions and offences may be processed only under the control of official authority or where Union or national law allows it (Article 10). For a lawyer, the basis is the law of the profession, which allows assistance and representation in criminal cases.

Vendors: the data processing agreement

Article 28 asks for two things:

  • work only with processors that provide sufficient guarantees;
  • have a contract with each of them that says what data it processes, for what purpose, with what security measures and what happens to the data at the end.

A processor may use another vendor only with the firm's authorisation. So ask whom your vendor uses, too.

Security, chosen according to the risk

Article 32 gives no fixed list. It asks for measures appropriate to the risk and names a few: pseudonymisation and encryption of data, the ability to restore access to data after an incident, regular testing of the measures.

In a law firm, in practice, this means:

  • two-step sign-in;
  • separate permissions by role, so that everyone sees only what concerns them;
  • stopping at once the access of a colleague who leaves;
  • backups that are checked;
  • a log that shows who did what, and when.

Records of processing

Article 30 requires a record of processing activities. The exemption for organisations with fewer than 250 employees does not apply where the processing is likely to result in a risk, is not occasional, or includes special categories of data or data on criminal convictions. A firm processes data all the time, so the record is kept.

Personal data breaches

A lost laptop, an e-mail sent to the wrong recipient, a hacked account: all of these can be personal data breaches.

  • Notifying the authority (Article 33): without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals. In Romania, the authority is ANSPDCP.
  • Informing individuals (Article 34): when the risk to them is high.
  • The vendor: a processor notifies you without undue delay when it becomes aware of a breach.

Every breach is documented, even if it is not notified (Article 33(5)).

How long you keep the data

Data is kept only as long as the purpose requires (Article 5(1)(e)). The firm sets its retention periods by type of document, taking into account its legal and professional archiving obligations, and applies them.

Individuals' rights and professional secrecy

People have the right to know that their data is being processed. The Regulation does take professional secrecy into account: the duty to inform a person from whom you did not collect the data directly does not apply where the data must remain confidential under a legal obligation of professional secrecy (Article 14(5)(d)).

Impact assessment

Article 35 requires a data protection impact assessment where processing is likely to result in a high risk, in particular when it uses new technologies. Recital 91 says that the processing of clients' data by a lawyer who works individually should not be considered "large scale". For a law firm with many clients, that conclusion is no longer automatic. In both cases, bringing in an AI assistant that reads case files is a good moment for such an analysis.

Checklist

Obligation Article What you have to do
Informing clients 13 A privacy notice, given when the agreement is signed
Contracts with vendors 28 A data processing agreement with each one
Records of processing 30 A register kept up to date
Security 32 Measures chosen according to the risk and checked regularly
Data breaches 33, 34 A procedure and a register of breaches
Retention 5(1)(e) Retention periods by type of document

What the software does and what stays with the firm

Practice software helps you with security. In AVODesk:

  • the server, the database and the documents belong to the firm alone, and the data is hosted in the European Union;
  • two-step sign-in can be enforced for the whole firm;
  • everyone sees only what concerns them, and the access of a colleague who leaves stops at once;
  • passwords and keys are encrypted with a key of the firm's own;
  • the audit logs show who did what, and when;
  • a backup of the data is made before every update.

More on the Security page.

Software does not take the place of the firm's decisions. The legal bases, the retention periods, the privacy notice and the contracts with vendors remain yours.

This article is for information only and is not legal advice. It refers to Romanian and EU law as in force on the date of publication.

Sources

Frequently asked questions

Is a law firm a data controller?

As a rule, yes. The firm decides why and how it processes the data of its clients and of the other people in its cases, so it has the role of controller.

Do I need a contract with the vendor of my practice software?

Yes. A vendor that processes data on the firm's behalf is a processor, and Article 28 of the GDPR requires a written data processing agreement.

How quickly must a personal data breach be notified?

Without undue delay and, where feasible, within 72 hours of the firm becoming aware of it. No notification is needed if the breach is unlikely to result in a risk to individuals (Article 33 of the GDPR).

All articles

See AVODeskat work.