Recruitment operations
GDPR Audit Trail for Recruiters: What to Log and Keep
By Andre · · 15 min read
GDPR Audit Trail for Recruiters: What to Log and Keep

An audit trail for GDPR is a time-ordered record of who did what to personal data, and when. For a recruitment team it means you can show, record by record, who opened a candidate’s CV, who changed a profile, who exported a list and when something was deleted. The GDPR does not use the phrase “audit trail” as a rule on its own, but it asks you to be able to demonstrate compliance, and this record is the most practical way to do that when CVs arrive in a shared inbox.
This guide is for small business owners, agencies and HR teams who receive applications by email. It covers what regulators actually say, what to record, how to make entries traceable to one person, and how long to keep candidate data. It also shows where software that builds the trail for you saves the most time.
TL;DR
- The GDPR does not literally order an audit log, but regulators treat access logging as a necessary security measure in most cases, and the accountability principle means you must be able to prove what you did.
- A useful recruitment audit trail records who, what, which candidate record, when and from where, for views, edits, exports and deletions.
- Entries only help if each one points to a named person: shared logins and shared inbox passwords break attribution.
- Candidate data has a short shelf life. Regulators in France and Poland set clear limits for rejected candidates, so your trail should also show when and why data was deleted.
- The GDPR can apply to a US company that handles EU candidates’ data, so a US-based agency may still need this.
Table of Contents
- Does the GDPR require an audit trail?
- Audit trail, processing record and security log: three different things
- What a recruitment audit trail should record
- Making every entry traceable to a person
- Retention: the audit trail’s other job
- Using the trail for candidate requests and deletion
- What an auditor will ask for
- Our view: the trail should be a by-product, not a project
- Setting it up: a practical order of work
- Where RecrutFlo fits
- FAQ
- Sources
Does the GDPR require an audit trail?
Not in so many words. The Dutch data protection authority states that the GDPR does not explicitly say that logging who accessed personal data is mandatory, but that in most cases logging access is a necessary security measure. It adds that logging is compulsory in some sectors that handle sensitive data, such as healthcare, financial institutions and central government.
Two parts of the regulation do the real work. The first is the security duty: you must protect personal data with measures that fit the risk. The second is accountability: you are responsible for compliance and must be able to demonstrate it. Both are in the text of Regulation 2016/679 on EUR-Lex. A CV contains a name, contact details, work history and often a photo, date of birth or nationality. If a candidate asks who has seen their file, or a regulator asks how you protect it, an audit trail is the evidence that answers both.
Does it apply to a US company?
It can. The regulation covers organizations outside the EU that process personal data of people in the EU in certain situations, for example when they offer services to or monitor people there. The scope rules sit in Article 3 of the regulation’s official text. A staffing consultancy in Texas placing candidates in Berlin, or a startup recruiting remote engineers from Portugal, should check this with a privacy lawyer rather than assume it does not apply.
Audit trail, processing record and security log: three different things
These get mixed up, and the mix-up leads to gaps.
| Record | What it answers | Who uses it |
|---|---|---|
| Record of processing activities (RoPA, Article 30) | What kinds of personal data you process, why, on what legal basis, how long you keep it, and who receives it | Your team, and the regulator on request |
| Audit trail | Who did what to which record, and when | You, when investigating an incident or a candidate request |
| Technical security log | System events such as logins, failed logins and errors | IT or whoever runs your systems |
The Irish Data Protection Commission explains that a RoPA may usefully include the legal basis, the basis for special category data, retention periods by data category and transfer mechanisms. It must be made available to the supervisory authority on request, and it can help demonstrate accountability, according to its guidance note on Article 30. The same guidance says the record should be a living electronic document that is continuously updated, and that responsibility should not rest only with one person such as the data protection officer.
In practice the RoPA is the map and the audit trail is the footprint. The UK regulator’s audit framework says an organization should keep a formal, accurate, electronic RoPA and review it regularly against what actually happens. The audit trail is how you check what actually happens.
If you have not yet built the foundations, our GDPR recruitment compliance guide for small teams walks through the legal basis, notices and retention decisions that come first.
What a recruitment audit trail should record
There is no official template for recruiters. What follows is a practical standard that answers the questions a candidate, auditor or regulator is most likely to ask. Record each of these for every event that touches candidate data:
- Who: the individual user, never a shared account.
- What action: viewed, created, edited, downloaded, exported, shared, merged or deleted.
- Which record: the candidate profile or document affected.
- What changed: the field, with the old and new value for edits.
- When: a timestamp in a single time zone, ideally UTC.
- Where from: the application or integration that triggered the event, and the IP address if you need it.
The events that matter most in recruiting
Not every click deserves an entry. Focus on events with real privacy consequences:
- Intake: a CV arriving by email and being added to the database. This shows when you first received the data, which starts your retention clock.
- Access to full profiles and documents: especially for senior roles or sensitive records.
- Edits to contact details, notes and status.
- Exports: a CSV of candidates leaving the system is the highest-risk event in most small teams.
- Deletions and merges: including duplicate removal, so you can show nothing was lost or kept by accident.
- Permission changes: who was given or lost access, and when.
Log with restraint
Logging is itself processing of personal data, including data about your own staff. The Dutch regulator warns that logging must pass proportionality and subsidiarity tests before you decide what to record, as set out on its access to personal data page. Record the events above, not every keystroke, and do not copy whole CVs into the log. Reference the candidate record by ID instead.
Making every entry traceable to a person
The most common failure is not a missing log but a useless one. If three recruiters share one inbox login, the log says “recruitment@company.com opened this CV” and nobody can say who. Shared mailboxes are normal for hiring, so the fix is to separate the mailbox from the people who work in it.

Build an access matrix
The Dutch regulator expects an authorization matrix: a record of access rights for every system, based on what each employee needs for their job, kept detailed and up to date. Details are on its access guidance. For a ten-person agency a simple table is enough: each person, the role they hold, which candidate records they can see and whether they can export or delete.
Typical splits that work:
- Recruiters: view and edit candidates on their own searches.
- Team leads: the same, plus export.
- Administrators: user management and deletion.
- Hiring managers or clients: view a shortlist only.
Our article on shared inbox permissions recruiters must check goes through the mailbox side of this. For the principle of limiting access down to individual fields, role-based access control down to protected fields shows how fine-grained the rules can get in a business database.
Three habits that keep attribution clean
- Give each person their own login to the candidate database, even if the inbox itself is shared.
- Remove access the day someone leaves or changes role, and let the permission change appear in the trail.
- Review the access matrix on a schedule. The UK regulator says accountability measures should be reviewed at appropriate intervals.
Retention: the audit trail’s other job
An audit trail is not only about who looked. It should also show that you let go of data on time. Regulators are consistently strict about candidates who were not hired.
| Authority | Position on unsuccessful candidates |
|---|---|
| France (CNIL) | Keeping rejected candidates’ CVs for a five-year talent pool is in principle excessive. For this purpose, retention should in principle not exceed two years from the last contact, per its recruitment guide. |
| Poland (UODO) | Set the period in advance. As a rule, delete an unsuccessful candidate’s data immediately after the process ends. Any extension must be specially justified, per its workplace data protection guide. |
| European Union institutions (EDPS) | Files of unsuccessful candidates should not be kept as long as those of successful ones, and conditions of recruitment such as criminal records should not be kept after recruitment, according to its recruitment guidance. |
The periods differ by country, so pick the rule of the country where your candidates are, document your choice and apply it consistently. The EDPS adds that applicants must be told their rights and the purposes of processing before selection starts and again on recruitment.
Two practical points follow. First, write down a retention period per category: active applicants, talent pool with consent, hired employees. A data retention policy is the document that holds those decisions. Second, make sure the trail shows the deletion actually happened, with the date, the record and the person or rule that triggered it.
Using the trail for candidate requests and deletion
Under Article 17, a person can have personal data erased where, among other grounds, the data are no longer necessary for the purposes they were collected for or consent is withdrawn. When a candidate writes to you asking for deletion, the audit trail is what lets you reply with confidence.
A proportionate deletion record answers six questions:
- When did the request arrive, or what retention date triggered the deletion?
- Which candidate record and documents were in scope?
- Which places did you check: the database, the mailbox, exports, spreadsheets?
- What did you do, and who did it?
- When was it completed?
- Was anything kept on purpose, and why?
The fifth place people forget is the email inbox itself. A CV deleted from a database but still sitting in a shared mailbox is not deleted. That is why teams that receive applications by email need a clear picture of where copies live, and why a database tied to the inbox is easier to reconcile than loose attachments. Duplicates matter here too: a candidate who applied three times may exist as three records, and a deletion that removes one leaves two.
Our guide to tracking applicant emails without losing a CV covers keeping that intake under control.
What an auditor will ask for
Auditors and regulators come in several forms: your own internal reviewers, a client conducting due diligence, a supervisory authority. The questions repeat:
- Show me your record of processing activities and prove it matches reality.
- Who has access to candidate data, and how do you know?
- What happened to this candidate’s file between application and today?
- If you use a software provider to process CVs, what does your contract with them say?
On the last point, the CNIL’s recruitment guide says that when you use a subprocessor, the contract must require them to provide the information needed to show compliance, allow audits and permit checks of certifications. The same guide says recruiters must register the recruitment file in their record of processing activities, inform candidates and carry out an impact assessment where required, per the CNIL guide. So the audit trail is one of several pieces of evidence, and it works best when the others are in place.
A quick self-check before anyone asks:
- Can you name who viewed a given candidate’s profile last month?
- Can you list every export in the last quarter?
- Can you show the deletion of a candidate who was rejected more than your retention period ago?
- Does the access list match the current staff list?
If any answer is “not without digging through email”, that is the gap to close first.
Our view: the trail should be a by-product, not a project
Most small teams we talk about do not fail at GDPR because they ignore it. They fail because the evidence lives in too many places: a shared inbox, a folder of downloaded attachments, a spreadsheet someone started in 2022. An audit trail cannot fix that if it is a separate chore to maintain.
That is why RecrutFlo is built around the inbox you already use. It connects to Microsoft 365, Outlook and IMAP mailboxes (Gmail is coming soon), spots CV attachments, extracts the candidate details and keeps them in one searchable database. Because intake, profiles and exports sit in a single workspace, an audit trail and team access control sit alongside them, and workspace isolation keeps one team’s candidates apart from another’s. We designed it around EU data protection principles.
We also think automation should not take decisions away from recruiters. It handles the repetitive typing and duplicate flagging; people stay in control of who is shortlisted and what is deleted. And since duplicates are flagged, the same person is less likely to sit in your system as three untracked copies.
Pricing and limits are published, with no sales call and no implementation project, so a five-person team can test the workflow on the free plan before committing.
Marco
Setting it up: a practical order of work
You do not need to do everything at once. A sensible sequence for a small team:
- Map where CVs enter and live. Inbox, database, shared drives, personal downloads.
- Write the retention periods for each category of candidate and note them in your RoPA.
- Give everyone an individual login and set roles using the access matrix.
- Switch on or build the audit trail for views, edits, exports, deletions and permission changes.
- Schedule a quarterly review: access list against staff list, a sample of exports, a sample of deletions.
- Rehearse a candidate request. Pick a past applicant and time how long it takes to show their full history and delete it.
A clean data structure makes step 4 far easier. Our article on candidate database design covers fields and rules, and the one on candidate data quality explains how to check a database stays accurate, which matters because an accurate record is also a data protection duty.
Where RecrutFlo fits
If your CVs arrive by email, RecrutFlo gives you the database and the trail in one place. It connects to your existing inbox, extracts structured candidate profiles from PDF, DOC and DOCX attachments, flags duplicates, supports CSV export and includes an audit trail, team access control and workspace isolation. Setup needs no onboarding call.
The Free plan lets you test the workflow first. Paid plans are Starter at €19 per month, Professional at €49 per month and Business at €149 per month, and extra processing runs are a one-off purchase: €9 for 100, €29 for 500 or €49 for 1,000. See the current limits on the pricing page, or look at the product overview.

FAQ
Is an audit trail mandatory under the GDPR?
The regulation does not name it explicitly. The Dutch regulator says logging access is a necessary security measure in most cases and mandatory in some sectors handling sensitive data. Because you must also be able to demonstrate compliance, treating it as required is the safe approach.
How long should we keep audit logs?
Keep them long enough to investigate incidents and answer requests, and no longer than you can justify. Write the period into your retention policy and your record of processing. Keep logs lean, since they contain personal data about both candidates and your staff.
Does the audit trail have to include the CV itself?
No. It should reference the candidate record, not copy the contents. Storing full CVs in logs creates a second copy of the same personal data that you would also have to find, protect and delete.
How long can we keep rejected candidates’ CVs?
It depends on the country. France’s regulator says the talent pool retention should in principle not exceed two years from the last contact, while Poland’s regulator says unsuccessful candidates’ data should in principle be deleted right after the process. Check the rule for the country your candidates live in and record your choice.
Sources
- Regulation (EU) 2016/679, EUR-Lex
- Access to personal data, Autoriteit Persoonsgegevens
- Guidance note on records of processing activities, Irish Data Protection Commission
- Records of processing and lawful basis, ICO
- Guide to accountability and governance, ICO
- Guide recrutement, CNIL
- Ochrona danych osobowych w miejscu pracy, UODO
- Selection and recruitment of staff, EDPS
- Data retention policy guide, Guardiso
- Role-based access control without code, SoftEXIT