1. What the GDPR is and why it also concerns small companies
The GDPR, Regulation (EU) 2016/679, is the European rule governing the processing of personal data. Processing means any operation on such data: collecting, recording, storing, consulting, sending it to someone. The Regulation makes no distinction by size: if your company processes data about customers, employees, candidates or suppliers who are individuals, it must comply. What changes is the quantity of documentation and the complexity of the measures, not the basic principle.
Many companies stop at the privacy notice on the website and believe they are covered. In reality the Regulation requires you to know which data you process, why, for how long and who has access to it. Without this knowledge no compliance measure holds. The good news is that much of the work is orderly and repeatable: once the map is drawn, subsequent updates take little time and few steps.
2. The obligations in order: where to start
The obligations should not all be tackled together. They follow a logic: the map of processing comes first, because every other choice depends on what you process. Following the order below avoids writing notices or contracts on the basis of a wrong picture. Each step produces a document or evidence that you then use in the others, so it is worth keeping everything in a single folder, with the date and owner of each document.
- Map the processing: list the data you collect, the purposes, the systems that hold it and who has access.
- Complete the record of processing activities and keep it up to date with every new service or supplier.
- Verify the legal bases and prepare clear notices for customers, employees and candidates.
- Identify the suppliers that process data on your behalf and sign with each the agreement the Regulation requires.
- Assess whether a data protection impact assessment is needed for the riskiest processing.
- Define security measures, role-based access and a procedure for handling breaches.
- Establish how to respond to individuals' requests and how long to keep data.
3. The record of processing activities: the map you start from
The record of processing activities is the document describing each processing activity: which data, for what purpose, on what legal basis, with which suppliers, for how long and with which measures. In many cases it is mandatory, but the obligation depends on size and the type of data processed: check your position with an adviser. Even where it is not mandatory, it is the most useful tool for understanding what actually happens in the company.
The record should not be written once and filed away. It must reflect reality: when you change software, activate a marketing service or take on a new supplier, the record must be updated. An outdated record of several years is often worse than no record, because it gives a false impression of control. The detail of how to complete it is covered in a dedicated guide on the record of processing activities.
4. Legal bases, notices and data minimisation
Every processing activity must rest on a legal basis: a contract with the individual, a legal obligation, the company's legitimate interest, consent and the other bases provided by the Regulation. Not all of them apply to every processing, and consent is not the default choice: for many business activities it is the wrong basis. Choose the basis case by case and note it in the record, because the question you will always be asked is the same: why do you process this data?
The notice explains to the individual who you are, which data you process, why, for how long and what rights they have. It must be written in an understandable way, not copied from a generic template. The principle of data minimisation requires collecting only what is needed: if a form asks for a field that is never used, remove it. Reviewing contact and sign-up forms is often the quickest and most useful piece of work.
5. Security: technical and organisational measures
The Regulation requires measures appropriate to the risk, both technical and organisational. There is no single list that suits every company: it depends on which data you process and how much harm it could do if it fell into the wrong hands. For most small and medium-sized enterprises the basics are these: personal, non-shared accounts, strong authentication for email and for systems holding sensitive data, separate and tested backups, regular updates and staff training.
The organisational side matters as much as the technical side. You need to know who can grant and revoke access, what to do when a colleague leaves the company and how to report a suspicion. A written procedure of a few pages, read and known by everyone, is worth more than a long document nobody opens. Use the table as a guide to check your current state. Note the answers and the date on which you received them.
| Area | What to check | Question to ask the supplier |
|---|---|---|
| Access | Personal accounts, role-based permissions, revocation at the end of the relationship | How are access rights granted and revoked, and by whom? |
| Authentication | Strong authentication for email and for systems holding sensitive data | Which sign-in methods are supported and enabled? |
| Backups | Separate, protected copies that are restore-tested | When was a full restore last tested? |
| Updates | Systems and devices kept up to date through a clear routine | Who applies updates, and how often? |
| Training | Staff able to recognise phishing and unusual requests | Which exercises or materials are provided? |
6. Suppliers that process data on your behalf
If a supplier accesses personal data on your behalf, for example the provider that runs your systems, payroll, email or management software, the Regulation requires a written agreement defining what it may do with the data, which measures it applies and how it behaves in the event of an incident. This agreement must be signed before the supplier starts work, not afterwards. A supplier without a written agreement is a risk both for you and for it. If you sign afterwards, the processing has already taken place without rules.
Check sub-suppliers as well: if your supplier uses others for part of the service, it must tell you and make them comply with the same rules. A dedicated guide explains the minimum content of this agreement. In the meantime, ask your main suppliers whether they already have an agreement of this type and who signed it for your company. Anyone who cannot answer needs to be followed up.
7. Individuals' rights, retention and breaches
Individuals have rights over their own data: to access it, correct it, request its erasure or object to certain processing. Requests must be handled within a time limit set by the Regulation, which may be extended in complex cases. The exact time limit and the exceptions must be checked case by case with an adviser: an improvised reply from whoever receives the email is not enough. You need a procedure with a clear point of contact and a way of recognising requests when they arrive.
Two further topics complete the picture. The first is retention: data cannot be kept forever, and for each category a period and a criterion for deletion must be defined. The second is data breaches, meaning an incident that compromises data: the Regulation requires every breach to be documented and, in some cases, notified to the authority and the individuals concerned. Preparing this process before an incident makes a difference to response times.
8. Internal roles: who signs, who checks, and when a DPO is needed
Every compliance task has an internal owner. The controller, meaning the company in the person of its legal representative, remains responsible for what happens. In practice it is advisable to nominate a person who coordinates privacy, supported by the adviser and the IT lead. Writing down who does what prevents every deadline from becoming nobody's problem and makes it easier to reconstruct the decisions taken.
The data protection officer, the DPO, is not always mandatory. Where it is, the DPO must have independence and cannot be the same person who decides on processing, such as the IT lead or the HR lead. Even where it is not mandatory, a clear point of contact greatly improves management. The question of appointment is covered in a dedicated guide.
9. How to start
The useful first step this week is simple: choose one process that handles personal data, for example recruitment or customer invoicing, and describe it on a sheet by answering five questions: which data you collect, why, where it is stored, who accesses it and for how long it is kept. The answers will tell you which part of the record is missing and which supplier should be checked first. Also note who completed the form and when.
Then arrange a meeting with your data protection adviser and your IT supplier, bringing the completed form. Do not aim for perfection on the first round: a partial but up-to-date picture is already a solid starting point and lets you set priorities on an informed basis. Repeat this check every time an important process changes.
Frequently Asked Questions
Does the GDPR apply if my company has few employees?
Yes. The Regulation applies to anyone who processes personal data, regardless of size. Small organisations often have less data and simpler processes, so the obligations are proportionate. Even a small company processes data about employees, customers and suppliers, and must be able to explain how it uses it. An adviser can define a realistic scope for your business.
Do I need every customer's consent to process their data?
Not always. Consent is one of the legal bases, but many processing activities needed for a contract or a legal obligation do not require consent. The point is to choose the right basis for each processing activity and state it in the notice. Using consent where it is not needed can create problems, because the individual can withdraw it at any time and the activity risks stopping.
Is the record of processing activities mandatory for everyone?
Not for everyone in the same way. The obligation depends on size, type of data and frequency of processing. It is worth checking with an adviser. Even where it is not mandatory, the record remains the most useful tool for knowing your data and responding in an orderly way to customers, suppliers or authorities.
What must I do if an IT supplier processes our data?
You must have a written agreement with it that sets out the purposes, data, security measures, sub-suppliers and what happens at the end of the service. Ask the supplier for a copy of its template agreement and check that it suits your case. If the supplier does not have one, that is a warning sign to look into before continuing with the service.
How long do I have to respond to an individual's request?
The Regulation sets a time limit, which may be extended in complex cases, but the exact duration and the conditions must be checked with an adviser. In practice it is advisable to have a procedure that records the date of receipt, identifies the requester and tracks the response. A delay caused by the absence of a procedure is harder to justify.
Is a notice on the website enough to be compliant?
No. The notice is an important document, but on its own it proves nothing. You need to know what happens to the data internally, who accesses it, which suppliers receive it and for how long it is kept. The notice must describe reality: if it does not match how you work, it is badly written even if it is well presented.
Where should I start if nobody in the company handles privacy?
Assign the role to one person, even an internal one, and have them work with an adviser on a first round of checks. Start with one process at a time and document the answers. You do not need a huge project: you need a point of contact, a map of processing and a written procedure that everyone knows.