Start hereAssign roles and document the processing
~56 days leftOpen step
Guide library
Regulation Europe

Andorra Data Protection Law (LQPD)

Andorra Law 29/2021: privacy compliance and APDA notifications

Work through Andorra’s personal data protection law. Map your processing, decide whether to appoint a data protection officer, review supplier access and prepare for rights requests and breach notifications.

Issuing authority
Andorran Data Protection Agency (APDA)
Timing
Article 15 gives one month to respond to a rights request, counted from the day after receipt. Article 38 requires APDA notification within ten working days after appointing a DPO. Article 36 requires qualifying breach notification without undue delay, within 72 hours of awareness where feasible.
Reviewed
Inside this guide
4 steps · 8 templates

Who it applies to

Andorran public bodies and in-scope private controllers and processors. Check Article 2 if an entity based outside Andorra uses processing means in Andorra, and Article 29 for the local representative requirement and exceptions.

What you’ll produce

A signed scope and DPO decision, an appropriate processing record, notices and rights procedures, a supplier and transfer file, and a breach response process.

APDA replaced the old file declaration system with internal processing records. Article 34’s exception for organizations with fewer than 50 workers has limits, including for non-occasional processing. APDA requires submissions addressed to it to be in Catalan.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which entities need a DPO or a representative?
Ask Legal to document the answer for each entity and activity. Resources, access to leadership, independence and applicable APDA notifications belong in the appointment decision.
Who can hold a supplier change?
Give Procurement and Security a named privacy approver and a release condition. Use the approval for new processing purposes, locations, subcontractors and sensitive data.
Can someone submit a breach notice on Sunday?
Assign a controller representative and a backup who can submit in Catalan. Have both demonstrate how to access the form and contact the DPO or equivalent contact after hours.

How to spend the first week

  1. Follow one guest or customer record and one employee record from collection through deletion. Compare the company’s notices and retention policies with what system owners can demonstrate.
  2. Ask the largest processor to show its current subprocessors, access regions, incident escalation route and deletion options.
  3. Run a timed incident drill. Have the controller record when it became aware, then prepare a first notice with facts the supplier can provide at that time.

What to review each week

Show open rights requests and dates, DPO appointment and APDA contact status, supplier changes awaiting review, impact assessments and incidents with unresolved notification decisions.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Andorra Data Protection Law (LQPD) kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Assign roles and document the processing · Executive sponsor + Legal + business owners [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Follow one guest or customer record and one employee record from collection through deletion. Compare the company’s notices and retention policies with what system owners can demonstrate.
2. Ask the largest processor to show its current subprocessors, access regions, incident escalation route and deletion options.
3. Run a timed incident drill. Have the controller record when it became aware, then prepare a first notice with facts the supplier can provide at that time.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which legal entity decides each purpose, and who can show where the data is stored and accessed?
  • Who can approve a notification in Catalan when a critical supplier reports a breach outside business hours?

Worked scenario

An Andorran hotel group outsources booking support and payroll. Its privacy lead follows bookings and former employee records across both suppliers. The group checks the systems’ actual retention settings, reviews external support access and practices a breach notice after a supplier reports an exposed export.

What to read next

  • EU GDPR

    Compare the separate GDPR duties that can apply to the same service.

FROM THE SOURCE

Cases and numbers

APDA enforcement decision · 8 April 2025

15 working daysTime ordered to supply a revised identity verification protocol

An identity check failed to stop unauthorized eSIM changes

The APDA upheld a reprimand against Andorra Telecom after investigating SIM swapping. It found weaknesses in identity verification and security measures, and a failure to notify the APDA on time.

What to check Test account changes with simulated impersonation. Give the incident lead evidence of actual process failures and a timestamp for the notification decision.

APDA resolution 002-024_B3 (opens in a new tab)

APDA annual report · 2024

63Security breach notifications handled in 2024

Breach notifications more than doubled from 2023

The APDA reported 25 notifications in 2023 and 63 in 2024. It separately reported 21 complaints received in 2024.

What to check Track incident notifications and complaints as separate measures. Assign an owner to investigate whether the same underlying problem keeps appearing in both.

APDA announcement of the 2024 annual report (opens in a new tab)

APDA inspection update · August 2025

38Notifications received in connection with the Andornet incident

One supplier incident prompted checks at many customers

In its first inspection update, the APDA said it closed 15 notifications where personal data was unaffected, made recommendations to 18 entities and requested missing information from four.

What to check Make supplier alerts detailed enough to establish what happened to your own records. Assign someone to chase missing facts and track subsequent updates.

APDA update on the first phase of the Andornet inspection (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Ten working days after appointment

    Notify APDA of the DPO

    Article 38 sets the window for reporting contact details after appointment. Communicate cessations as well.

    Official reference (opens in a new tab)
  • One month from the day after receipt

    Respond to a rights request

    Article 15 has date-counting rules, including how to handle holidays. Document any eligible extension and tell the requester within the initial month.

    Official reference (opens in a new tab)
  • Without undue delay, within 72 hours where feasible

    Notify APDA of a qualifying breach

    Article 36 starts at awareness. Preserve the facts, risk decision and any reason for delay.

    Official reference (opens in a new tab)
The whole journeyabout 56 days across 4 steps
  1. 01Assign roles and document the processing, Executive sponsor + Legal + business owners, about 7 days
  2. 02Put notices and rights requests into operation, Privacy lead + Support + system owners, about 14 days
  3. 03Review suppliers, transfers and high-risk changes, Legal + Procurement + Security, about 21 days
  4. 04Rehearse and run breach notification, Incident lead + controller + DPO or Privacy, about 14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 8 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Assign roles and document the processingExecutive sponsor + Legal + business ownersBefore starting or changing processingSet a start dateAndorra processing and DPO decision; Processing inventoryOpen
Put notices and rights requests into operationPrivacy lead + Support + system ownersAt collection and when handling requestsSet a start dateAndorra notice and rights request file; Rights workflowOpen
Review suppliers, transfers and high-risk changesLegal + Procurement + SecurityBefore supplier access or launchSet a start dateAndorra supplier and impact assessment file; Processor registerOpen
Rehearse and run breach notificationIncident lead + controller + DPO or PrivacyAt awareness of an incidentSet a start dateAndorra breach notification packet; Incident assessmentOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Assign roles and document the processing

    Who Executive sponsor + Legal + business owners When Before starting or changing processing

    Map each purpose to the legal entity, lawful basis, people, data, recipients and deletion rule. Identify controller and processor roles. Record whether Article 34 requires a register and why. Apply Article 38 and the APDA’s sector guidance to the DPO decision, then notify APDA if a DPO is appointed.

    How to do this step

    Before you start

    Entity list, data flow descriptions, any current processing record and DPO or representative records.

    1. Have each service owner show a real workflow. Record why data is needed, where it goes and when it comes out of ordinary use.
    2. Have Legal check the territorial and DPO triggers and any Article 34 exception. Record decisions and notify APDA of the appointment or cessation as applicable.

    What a reviewer should see

    A responsible owner can tie each in-scope activity and role to a signed decision and operational evidence.

    When to escalate

    Escalate missing scope evidence, conflicts in the DPO role and a notification date that may be missed.

    What to produce

    Andorra processing and DPO decisionSpreadsheet

    Gather first

    • Entity list
    • System inventory and deletion settings
    • Supplier list
    • Law 29/2021 Articles 2, 29, 34 and 38
    • APDA sector guidance

    How to prepare it

    1. Interview one person who operates each workflow. Make one row per purpose with systems, affected people, data categories, recipients, legal basis and actual retention. Indicate which details Article 34 requires for the role.
    2. Have Legal check territorial scope and whether a representative or DPO is required. For each Article 34 exception claimed, record the workforce and whether processing is occasional, risky or includes special-category or offence data.
    3. If appointing a DPO, set the reporting line and check for conflicting duties. Notify APDA of contact details within ten working days of appointment. Keep the signed decision, notice and confirmation.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Processing row
    Fictional Coma Ridge Hotels uses supplier-hosted payroll for ongoing staff administration. The payroll lead shows the current retention settings and who can export records.
    Register decision
    28 workers. Payroll happens every month. Privacy records why the small-organization exception does not apply to this recurring activity and identifies who maintains the record.
    DPO decision
    Legal checks Article 38 against the entire group’s activities and saves the facts and reasoning. If appointed, the corporate secretary adds the date of appointment and separately tracks the APDA notice.

    Check before handing it over

    The register and scope decision match operating evidence. An accountable executive can show who maintains the entries and how APDA was notified if applicable.

    Give each owner their register rows, the approved retention rules and a way to notify Privacy of changes.

    Processing inventorySpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.

    Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.

  2. 02

    Put notices and rights requests into operation

    Who Privacy lead + Support + system owners When At collection and when handling requests

    Match Articles 16 and 17 notices to how each system receives data. Publish an accessible contact route. Log receipt, identity checks, owner and deadline under Article 15. Route the search across suppliers and send the response securely. Check Article 30 data blocking when correcting or erasing data. If extending the deadline, tell the individual within one month and explain why.

    How to do this step

    Before you start

    Published notices, contact routes, collection flows, supplier directory and retention settings.

    1. Record what notice each person receives and when. Test the contact address and route messages to a staffed inbox with a backup owner.
    2. Log receipt, calculate the response date and assign searches. Check any blocking duties for correction or erasure and record the actual action, delivery and any extension.

    What a reviewer should see

    A test request can be traced to its receipt, deadline, verified system actions and response.

    When to escalate

    Raise missing processor results, a missed deadline or an unsafe way of delivering a response.

    What to produce

    Andorra notice and rights request fileSpreadsheet

    Gather first

    • Processing inventory
    • Collection screens
    • Notice versions
    • Request inbox
    • Supplier search instructions and access controls

    How to prepare it

    1. Mark each collection channel as direct or indirect and check the required Articles 16 and 17 information. Capture the notice version, contact route and publication point with a dated screenshot.
    2. Open a request ticket with receipt date, requested right, owner and first day of the Article 15 clock. Record enough identity evidence to avoid unauthorized disclosure. Ask Legal to check the date-counting rules if the end date falls on a holiday.
    3. Search systems and processors, document exceptions and check that the reply goes to the right person. For correction or erasure, have Legal verify the Article 30 blocking duties and the final destruction date. If there is an eligible extension, tell the requester why within one month and record the new date.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Notice check
    Fictional hotel booking form. The direct collection notice names the controller and explains booking purposes, storage and the working privacy inbox. Privacy checks the actual supplier and transfer disclosures.
    Request ticket
    AD-R-014. Former guest asks for access through the notice contact. Support logs the received time, assigns Reservations and the booking supplier, and sets an internal review date ahead of the statutory deadline.
    Outcome
    Privacy reviews the returned records for third-party information before secure delivery. The sent response and supporting search evidence stay in the restricted case folder.

    Check before handing it over

    A tester can find the notice and submit a request. The case file identifies the deadline, identity checks, search steps and response sent.

    Give Support the approved intake and escalation procedure, plus access to current system and supplier contacts.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

  3. 03

    Review suppliers, transfers and high-risk changes

    Who Legal + Procurement + Security When Before supplier access or launch

    Use Article 31 to review processor terms and documented instructions. Check retention, incident support, subcontractor approvals and deletion or return. Record real processing and access countries and check Chapter Five transfer requirements for each flow. Screen under Article 32 and complete the impact assessment before high-risk processing. Consult APDA under Article 33 where high risk remains.

    How to do this step

    Before you start

    Signed processor terms, data maps, hosting and access records, and impact assessment screening.

    1. Match supplier terms and subcontractor approvals to the actual data and access locations. Record the transfer basis for each external recipient as applicable.
    2. Review safeguards and residual risk before launch. Complete a required impact assessment and prior consultation when the conditions are met.

    What a reviewer should see

    The release owner has an approved scope and an evidence file covering access, transfers and the impact assessment decision.

    When to escalate

    Hold supplier access or deployment when a transfer, assessment or consultation requirement is unresolved.

    What to produce

    Andorra supplier and impact assessment fileMemo

    Gather first

    • Signed service terms
    • Processing and subprocessor inventory
    • Exported region and access settings
    • Impact assessment screening
    • LQPD Chapters Four and Five

    How to prepare it

    1. Trace the data through supplier hosting, backups and support. Record each recipient and country, who can authorize subcontractors, and what the provider will delete or return at exit.
    2. Attach the relevant contract clauses and actual security evidence. Have Legal document the transfer basis for each flow and compare it with the provider’s actual location and access settings.
    3. Screen for high risk. Document the purpose, necessity, proportionality, harms to people, safeguards and residual risk in any required impact assessment. Get the DPO’s advice where designated and check whether APDA consultation is required before launch.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Proposed change
    Fictional hotel adds supplier support for the room booking portal. IT supplies storage and support regions, export permissions and the list of subcontractors.
    Evidence and owner
    Procurement records the instructions and incident support clauses. Security produces a dated export of role permissions. Legal records the applicable transfer basis and supporting documents.
    Release condition
    Keep new access disabled until the owners verify transfer coverage and finish any required impact assessment or prior consultation. Preserve the approved settings as release evidence.

    Check before handing it over

    A reviewer can tie each supplier permission and destination to a signed instruction, the applicable transfer decision and a live configuration.

    Send approved limits to the system owner and assign rechecks for changes to locations, subcontractors or sensitive processing.

    Processor registerSpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.

    Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.

  4. 04

    Rehearse and run breach notification

    Who Incident lead + controller + DPO or Privacy When At awareness of an incident

    Record awareness time and assess the risk to people. A processor alerts the controller without delay. If Article 36 requires APDA notice, send the known facts without undue delay and within 72 hours where feasible. Explain lateness and provide missing information in stages. Assess high-risk communication to affected people under Article 37 and document every breach.

    How to do this step

    Before you start

    Incident log, source evidence, awareness time and current APDA form.

    1. Assign the controller’s decision owner and record the risk to people. Draft and send a required notification using current facts, including approximate counts, impact, mitigations and contacts.
    2. Assess affected-person communication, send any required updates and archive the receipt, decision and corrective actions. Use the same approach for incident exercises.

    What a reviewer should see

    The case file records awareness, the risk decision, notification and follow-up dates, supporting evidence and owners.

    When to escalate

    Escalate immediately if an applicable notification clock is running and the decision owner or backup is unavailable.

    What to produce

    Andorra breach notification packetMemo

    Gather first

    • Incident timeline
    • Supplier alert
    • System logs
    • Affected population and records
    • LQPD Articles 36 and 37
    • Current APDA notification channel

    How to prepare it

    1. Record what you learned and when. Assign one individual to maintain the UTC timestamp and local time. Contain exposure and collect the minimum facts needed to assess harm.
    2. Have the controller document its risk decision. For a required APDA notification, prepare the description, approximate people and records, likely effects, mitigations and contact point. Send in Catalan through the applicable APDA route and log what follow-up is due.
    3. If notice is late, document the specific reason. File missing facts in stages without undue delay. Decide whether to tell affected people under Article 37, and preserve the decision for every breach.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional timeline
    Supplier confirms an unexpectedly public booking export on Monday at 09:20 local time. The controller records awareness at 09:20 and computes Thursday at 09:20 as the 72-hour point, subject to its duty to notify without undue delay.
    Initial notice fields
    Approximate guest and booking-record totals, categories of identifiers, how access was exposed, likely impersonation risk, revoked access and the DPO contact.
    Follow-up
    Security verifies exact affected records and whether data was downloaded. Privacy sends any required update and logs the Article 37 decision and its evidence.

    Check before handing it over

    The case record preserves awareness, the notification decision, the submitted text and receipt, corrective action and the assessment of harm to affected people.

    Give the on-call controller access to the approved notification route and a backup reviewer who can work in Catalan.

    Incident assessmentSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.

    Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes