Regulation · Albania
Albania Personal Data Protection Law
At a glance
- Jurisdiction
- Albania
- Supervisory authority
- Commissioner for the Right to Information and Personal Data Protection (IDP)
- In force
- Approved 19 December 2024 · in force since early 2025, some duties from early 2027
- Official name
- Law No. 124/2024 on Personal Data Protection
What Albania’s data protection law asks of you, article by article
How GovernID fits: Albania’s new law follows the GDPR closely: know your processing, explain it, keep records and prove it. GovernID builds that proof into collection. Your RoPA covers the items in Art. 27, privacy notices are generated from it, and each record collected through GovernID carries the notice, consent, legal ground and retention period that applied on the day it arrived.
Timeline: Law No. 124/2024 replaced Law No. 9887/2008 in early 2025. A few duties start two years after publication, in early 2027: telling people about high-risk breaches, impact assessments, prior consultation, and some codes of conduct and certification rules.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Scope. The law applies to controllers and processors established in Albania, and to those outside Albania that offer goods or services to people in Albania or monitor their behaviour there. | Art. 4 | GovernID hosts each company’s data in the country where it is registered, and each company in a group works in its own portal. | Deciding whether and how the law applies to you. |
| Principles and accountability. Process lawfully, fairly and transparently, for specified purposes, with only the data needed, kept accurate and no longer than necessary, and be able to show it. | Art. 6 | Each processing activity in your RoPA records its purpose, data categories, legal basis and retention period. Every field is classified before the first record arrives, and each record keeps the terms it was collected under. | Deciding purposes and judging what is necessary. |
| Legal grounds. Every processing needs one of the grounds the law lists, such as consent, contract, legal obligation or legitimate interest. | Art. 7(1) | Legal bases come ready in the Privacy Taxonomy. Each activity records its basis, and each record keeps the basis that applied on the day it arrived. | The legal assessment, including the legitimate interest test. |
| Consent. You must be able to show that consent was given, the request must be clear and separate, and people can withdraw at any time. For online services, children can consent from 16. | Art. 8 | The approved consent text is shown at collection, one purpose per box, never pre-ticked. GovernID keeps the version on the record with the dates consent was given and withdrawn. People withdraw in the Privacy Center. | Deciding when consent is the right ground, approving the text and checking age. |
| Sensitive data and criminal records. Processing is prohibited unless one of the listed exceptions applies. Criminal records data has its own rules. | Art. 9, 10 | Sensitive fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Choosing the exception and the safeguards. |
| Transparency. Give people clear information about the controller, purposes, legal ground, recipients, transfers, retention and their rights when you collect their data. | Art. 12(1), 13 | Privacy notices are generated from the RoPA with these items and served as a link at the moment of collection. Each record keeps the notice version the person saw. | Approving the notice and keeping it accurate. |
| Data subject rights. Access, rectification, erasure and the right to be forgotten, restriction, portability, objection, and safeguards for automated decisions. | Art. 14–20 | In the Privacy Center, people see the records that contain their verified contact details, withdraw consent, object to processing and get an instant preliminary report. DSAR Automation finds every record of a person across connected collection points. | Handling access, rectification, erasure, restriction and portability requests, and requests made through other channels. |
| Response time. Reply within 30 days, extendable to 60 days for complex or numerous requests. Tell the person within 30 days if you extend or refuse, and that they can complain to the Commissioner. | Art. 12(4) | Requests made in the Privacy Center reach your team at once, with their date, and consent withdrawals are tracked until handled. | Deciding on each request and replying in time. |
| Responsibility, by design and by default. Put measures in place to show compliance, build protection into how processing is designed and collect only what each purpose needs. | Art. 22, 23 | Forms connect to GovernID so the notice, consent and classification are set before collection starts. Each field is linked to a data category approved for that activity. | Designing systems and choosing the measures. |
| Joint controllers, representatives and processors. Joint controllers set out their roles in writing. Controllers outside Albania in scope appoint a representative there. Processors work under a contract. | Art. 24, 25, 26 | Processors and other recipients are recorded in each activity and shown as processing flows. | Signing the agreements and appointing the representative. |
| Records of processing activities. Keep a written and electronic record of each activity with the details the law lists. | Art. 27 | The RoPA covers the items Art. 27 lists. Process owners confirm their activities and every confirmation is logged. Compliance Reporting exports the record with its version history. | Keeping the record complete for processing outside GovernID. |
| Security of processing. Apply technical and organisational measures appropriate to the risk, and keep personal data confidential. | Art. 28, 30 | Safeguards are recorded for each activity and storage location, and Corporate Privacy Memory keeps how each activity looked on any past date. | Implementing and testing the measures. |
| Breach notification. Notify the Commissioner within 72 hours unless the breach is unlikely to endanger people, and document every breach. Telling affected people when risk is high applies from early 2027. | Art. 29(1), 29(3), 29(6); Art. 101(2) | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach, notifying and documenting it. |
| Impact assessment and prior consultation. Assess processing likely to result in a high risk before it starts, and consult the Commissioner when risk remains high. These duties apply from early 2027. | Art. 31, 32; Art. 101(2) | GovernID recommends a DPIA for activities with sensitive data or transfers abroad. The assessment opens with the facts from your RoPA, ends with a risk map and report, and can be exported as PDF and JSON. | The risk judgement and any prior consultation. |
| Data protection officer. Appoint a DPO for public bodies, large-scale monitoring or large-scale sensitive data. A group of companies can share one DPO. | Art. 33, 34 | Your DPO works from one RoPA, sees which activities are confirmed and which have changed, and can export reports for management. | Appointing the DPO. |
| Transfers abroad. Transfer to countries the Commissioner finds adequate, or with appropriate safeguards such as binding corporate rules or standard clauses published by the Commissioner. | Art. 39–42 | Transfers are recorded in each activity, appear in the privacy notice built from it, and GovernID recommends a DPIA when data is sent abroad. | Choosing the transfer tool and signing it. |
| Direct marketing. Marketing can rest on legitimate interest, but sensitive data needs express consent and people can object at any time. | Art. 46 | Marketing consent is its own box with its own text, never pre-ticked, and people withdraw it in the Privacy Center. | Deciding the ground for each campaign. |
| Storage limitation. Keep data no longer than its purpose needs, then erase it. | Art. 6, 15 | Retention periods are set in the RoPA. Each record gets its own end date, records past it can be listed at any time, and GovernID’s own copy is marked for destruction when its period ends. | Deleting the data in your own systems. |
This page summarises the law to show where GovernID supports your work. It is not legal advice; your legal counsel decides how the law applies to your company.
Right of access: what a response must include
Under Article 14 of Law No. 124/2024, the data subject can obtain confirmation, access to their personal data and the following information.
| The response must include | Article |
|---|---|
| Confirmation of processing and access to the data | Art. 14(1) |
| Purpose of processing | Art. 14(1)(a) |
| Automated decision-making and profiling: logic and consequences | Art. 14(1)(b) |
| Retention period, or the criteria used to set it | Art. 14(1)(c) |
| Legal basis for the processing | Art. 14(1)(ç) |
| Categories of data, and the source if not collected from the data subject | Art. 14(1)(d) |
| Recipients, especially abroad, and how transfers are protected | Art. 14(1)(dh) |
| Other rights and the right to complain to the Commissioner | Art. 14(1)(e) |
| A free copy of the list of data categories | Art. 14(2) |
Deadline: 30 days. Extension: up to 60 days when necessary, notified within 30 days (Art. 12).
What GovernID does: Every record collected through GovernID is stored with its purpose, legal basis, the notice version shown, consent scope, retention end date and collection point. These are the answers an access response has to give. In the Privacy Center, the individual sees their records instantly as a preliminary report and can export it, and your team finds a person's records across every GovernID collection point with PII Search.
What stays with you: Data held in systems outside GovernID and a copy of it, the formal response letter, identity checks beyond the verified e-mail, redaction of third-party data, and tracking the deadline.
Rectification, erasure and objection are separate rights and are handled separately; this section covers access only.
Frequently asked questions
Does the law apply to companies outside Albania?
Yes, when they offer goods or services to people in Albania or monitor their behaviour there (Art. 4). Those companies appoint a representative in Albania (Art. 25).
How close is it to the GDPR?
Very close. It was written to align Albania with the GDPR, so a company already running a GDPR programme can reuse most of it. Check the local points: the Commissioner, Albanian transfer rules and the 2027 start dates.
Which duties start in 2027?
Art. 101(2) delays some articles by two years from publication, including notifying data subjects of high-risk breaches (Art. 29(3)), impact assessments (Art. 31) and prior consultation (Art. 32).
Where is our data hosted?
GovernID hosts each company’s data in the country where it is registered.
Is this page legal advice?
No. It summarises the law to show where GovernID supports your work. Your legal counsel decides how it applies to your company.
The law and its regulations: official sources
Links go to the issuing authority's own website. Some government sites restrict access from outside their country.
- Law No. 124/2024 on Personal Data Protection – idp.al, Albanian
- 124/2024: English translation – idp.al, English