01What a data protection policy is for, and who it covers
The policy fixes how the company treats the personal data of candidates, employees, the family members registered in medical insurance, and people who have left, from the moment of collection to destruction. It applies to everyone who processes that data: HR, finance, managers, technology staff and the service providers the company contracts.
HR writes it with the technology lead and the authorised body approves it. It connects with the acceptable use of IT resources policy for protecting devices and accounts, and with the confidentiality and social media policy for what the employee owes in respect of the company's and its customers' data.
02The data protection policy text and the request and incident forms
[Company name] Personal Data Protection Policy Version: [number] Effective date: [date] 1. Purpose and scope 1.1 This policy governs how [Company name] collects, uses, keeps, shares and destroys the personal data of candidates, employees, their families and people who have left. 1.2 It applies to everyone who processes this data inside the company and outside it on its instruction. 2. Principles 2.1 We collect only what we need, for a stated purpose. 2.2 We use the data for the purpose it was collected for, and do not change it without telling its owner as the law requires. 2.3 We keep the data accurate and up to date. 2.4 We keep it only as long as needed. 2.5 We protect it from unauthorised access, loss and tampering. 3. What we collect and why 3.1 Identity, contact, address and emergency contact: to manage the employment relationship. 3.2 Bank account data (the IBAN): to pay wages. 3.3 Job, pay, leave, penalty and appraisal data: to manage the work and payroll. 3.4 Attendance data, including the geographic location at the moment of the punch: to prove attendance. 3.5 Official documents (identity, residence permit, passport, work permit, health certificates): for the company's legal obligations. 3.6 Medical insurance and dependants data: to cover them. 3.7 Medical information in sick leave: only as much as proves the leave. 3.8 Candidate data (CV and interview results): to take the hiring decision. 4. Access to the data 4.1 A user sees only what his task needs, within the branch and department he is responsible for. 4.2 Permissions are granted on a written request approved by the employee's manager and HR. 4.3 Permissions are reviewed every [__] months, and withdrawn at once when their holder changes task or leaves. 4.4 Changes to sensitive data are logged with who changed them and when. 5. Sharing 5.1 The company shares data with the bodies the law requires it to, and with providers needed for the employment relationship such as the insurer and the bank, only as far as necessary. 5.2 The company does not sell data, and does not share it for marketing. 5.3 Every provider that processes data is bound by protection obligations written in its contract. 6. Retention and destruction 6.1 Each category of data is kept for the following period: [category — period]. 6.2 What has passed its period is destroyed safely or anonymised, except what the law requires to be kept. 6.3 A candidate who is not hired has his data kept [__] months and then destroyed, unless he agrees to its being kept for future jobs. 7. The data owner's rights 7.1 The employee may know what the company collects about him, see it and ask for its correction, and has the other rights the law provides. 7.2 He submits his request in writing and the company replies within [__] days. 7.3 What is proved wrong in the file is updated and the employee told of the correction. 8. Location tracking and monitoring 8.1 An employee's location is collected only to prove attendance or for a field task he knows about. 8.2 A field employee is asked to consent to tracking during working hours before the field shift starts. 8.3 Location is not tracked outside working hours. 8.4 [If there are cameras: where they are, how long recordings are kept and who may see them.] 9. Security 9.1 Each user has a personal account and passwords are not shared. 9.2 The number of login attempts is limited, and a device is bound to its owner's account. 9.3 Backups are kept encrypted in a separate place. 9.4 Data is taken out of the system only as far as needed, and export copies are deleted after use. 10. Data incidents 10.1 Whoever learns of a leak, loss or unauthorised access tells [responsible person] at once and within [__] hours. 10.2 He assesses the incident, contains it, decides on notifying the competent authority and the data owners within the period the law sets, and records it. 11. Responsibilities 11.1 [The person responsible for data protection] is appointed and trains users every year. 11.2 A breach of this policy is dealt with under the penalty regulation. Policy approval [Name and title of approver] Signature: ________ Date: [date] -------------------------------------------------- Request for access to personal data Name: [employee name] Employee no.: [number] Date of request: [date] What I ask for: [to see my data / to correct an item / other] The item or the error: [__] Date of reply: [date] Action: [__] HR signature: ________ -------------------------------------------------- Data incident log Date and time discovered: [__] Discovered by: [__] Description of the incident: [__] Data affected and the number of owners: [__] Containment: [__] Date the competent authority was notified: [__] Date the data owners were notified: [__] Corrective action: [__]
03The policy clause by clause
Clause 3: every category has a written purpose
The list that says why each category is collected is what the employee needs when he asks and what the auditor needs when he visits. If you cannot find a purpose for a category, remove it from the recording form rather than keep it "just in case".
Clause 4: the rule is need to know
A sales manager does not need the IBAN of an employee in another branch, and an attendance officer does not need a medical report. Tie permission to the task and the branch and department scope, review it every quarter and withdraw it on the day of leaving. For the detail see user permissions by branch and department and the employee data audit log.
Clause 3.7: medical information only as far as proof
A sick leave needs what proves it, not the whole diagnosis. Write that HR keeps the leave certificate and its length and does not ask for the details of the illness, and that whatever goes beyond proof goes back to its owner.
Clause 6: each category has its period, not one period for all
A candidate who was not hired is not kept as an employee's file is, and attendance data differs from payroll data. Write the table with periods you set after a legal review, because retention periods are checked legally for each kind of record, and we give no figure here.
Clause 8: tracking is declared, consented to and kept within working hours
Location tracking is what worries employees most. Write when it starts and ends and why, that it does not run outside working hours, and that the field employee consents before the shift begins. The employee location tracking policy is set out in detail.
Clause 10: an incident is reported before it is fully understood
Do not wait for the investigation to finish before telling the responsible person. The period the law sets for notifying the competent authority and the data owners should be shown to a legal adviser and written into the clause, so that nobody improvises it who finds the incident at three in the morning.
04A worked example: the reply period to an access request and the periodic permission reviews
HR received an access request from an employee on 2027-06-06, and the company set 30 days for the reply (an illustrative input, and the period is for legal review). So the last day to reply is 2027-07-06. The company reviews user permissions every 3 months from 2027-01-03:
| Review | Date |
|---|---|
| First | 2027-01-03 |
| Second | 2027-04-03 |
| Third | 2027-07-03 |
| Fourth | 2027-10-03 |
At each review the list of users and each one's permissions is pulled out, confirmed by the direct manager, and the permission of anyone who changed his task or left is withdrawn. The dates use the add-months function in the product, and the period is set by the company.
05When not to apply this policy
Customer and supplier data
Data of those the company deals with outside the employment relationship has a customer privacy policy, not this one.
Disclosure the law requires
A request by a competent official body for an employee's data on a legal basis is put to a legal adviser, carried out according to that basis, and recorded.
Anonymised data that identifies no one
General statistics, such as the number of employees in each department, are not personal data unless they identify an individual.
06Hard cases and common mistakes
A manager who asks for the data of an employee in another branch
It is not given except on HR's authority for a stated purpose, and the rule is that the scope of a permission does not go beyond his branch and department.
A former employee who asks for an experience certificate two years later
The company keeps what is needed to issue it according to the retention table, and destroys the other categories when their period ends.
Exporting a payroll file to a spreadsheet
The export copy is sensitive data in full. Give it an owner, a safe place and a deletion period, and do not leave it in "Downloads".
Common mistake: keeping everything "in case we need it"
Every item with no purpose is a protection obligation with no benefit. State the purpose or delete it.
Common mistake: a manager's permission after his post changes
He leaves his department and still sees its data for months. Tie withdrawing permissions to the transfer and promotion decision.
07Steps to adapt the policy to your company
- 1
Draw the data map
Write each category of your data, where it is kept, who sees it and for what purpose.
- 2
Make the retention table
A period for each category after a legal review, the way of destruction, and the exception for what the law requires to be kept.
- 3
Name the responsible person
Someone who receives requests and incidents, a deputy, and a number every employee knows.
- 4
Prepare the request and incident forms
The request form within the employee's reach, the incident log with the responsible person, and a short yearly training.
- 5
Review the providers
Every provider that processes your data has a written protection clause in its contract.
08Data protection policy checklist before approval
9 items
09Official source
- Authority
- Bureau of Experts at the Council of Ministers
- Law and articles
- Personal Data Protection Law
- Last reviewed
10Frequently asked questions
Yes. The policy provides for his right to know what the company collects about him, to see it and to ask for its correction. The detail of the rights and periods is set by the law, so check it with a specialist.
The company sets a period for each category after a legal review. We give no figure here because retention periods are checked legally for each kind of record.
In the template, only to prove attendance or for a field task he knows about, with the field employee's consent before the shift starts and within working hours.
The responsible person is told at once, assesses the incident and contains it, decides on notifying within the period the law sets, and records it.
Only as far as needed to cover them, and under a contract with written protection obligations.
Whoever HR has granted that permission, within his branch and department and for a need of his task, and it is reviewed from time to time.
