Data Protection & Privacy

Spain Royal Decree 1720/2007

RD 1720/2007 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
Real Decreto 1720/2007, de 21 de diciembre, por el que se aprueba el Reglamento de desarrollo de la Ley Orgánica 15/1999, de 13 de diciembre, de protección de datos de carácter personal
  • Classification
    Category
    Data Protection & Privacy
    Domain
    Privacy
    Framework Family
    Global Privacy Regulations
  • Regulatory Context
    Type
    Regulation
    Legal Instrument
    Royal Decree
    Sector
    Cross-Sector
    Industry
    Cross-Industry
  • Region / Publisher
    Region
    Europe
    Region Detail
    Spain
    Publisher
    Government of Spain (Royal Decree, proposed by the Ministry of Justice); supervisory authority Agencia Española de Protección de Datos (AEPD)
  • Versioning
    Version
    Royal Decree 1720/2007 (BOE-A-2008-979), consolidated text last updated March 8, 2012; largely superseded by the GDPR and Organic Law 3/2018
    Effective Date
    April 19, 2008 (three months after publication); GDPR applicable May 25, 2018 and LOPDGDD in force December 7, 2018
    Issue Date
    December 21, 2007 (published in the BOE January 19, 2008)
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    Medium
  • Official Reference
License Information

License included / downloadable: Yes

The Royal Decree is Spanish law published free in the Boletín Oficial del Estado, including the consolidated text; the platform links to the BOE.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
Spain Royal Decree 1720/2007 Regulation Text
Official text of the Royal Decree 1720/2007 implementing Spain's Organic Law on Data Protection.
Spanish Data Protection Agency Guidelines
Provides guidance by the Spanish Data Protection Agency for compliance with data protection laws.
AEPD Official Portal
Outlines resources and documentation available from the Spanish Data Protection Authority.
BOE: Ley Orgánica 3/2018 (LOPDGDD), texto consolidado
The organic law of 5 December 2018 that repealed the LOPD and defines what remains of Royal Decree 1720/2007.
Key takeaways
  • Royal Decree 1720/2007 approved the regulation implementing Spain's Organic Law 15/1999 on personal data protection.
  • In force since April 19, 2008, it is largely superseded by the GDPR and Organic Law 3/2018 (LOPDGDD).
  • Its 158 articles set three-level security measures (basic, medium, high), AEPD file registration, and ARCO rights.
  • The LOPDGDD repealed every lower-rank provision that contradicts the GDPR or the LOPDGDD.
  • The Agencia Española de Protección de Datos (AEPD) remains the authority.

Overview

Royal Decree 1720/2007 of December 21, 2007 (Real Decreto 1720/2007, BOE-A-2008-979) approved the regulation implementing Spain's Organic Law 15/1999 on the protection of personal data (LOPD), and it is largely superseded. The GDPR has applied since May 25, 2018, and Organic Law 3/2018 of December 5 on the protection of personal data and the guarantee of digital rights (LOPDGDD) took effect on December 7, 2018. The LOPDGDD repealed the LOPD together with every lower-rank provision that contradicts the GDPR or the LOPDGDD. What survives of the Royal Decree is read through those two texts; the Agencia Española de Protección de Datos (AEPD) remains the authority.

The Royal Decree was published in the BOE on January 19, 2008 and entered into force three months later, on April 19, 2008 (final provision two), replacing Royal Decrees 1332/1994 and 994/1999. Its 158 articles in nine titles set out the data quality principles and consent rules (Title II), the ARCO rights of access, rectification, cancellation and opposition (Title III), the notification of files to the AEPD's General Data Protection Register (Title V), international transfers under AEPD authorization (Title VI), codes of conduct (Title VII), the three-level security measures of Title VIII (basic, medium and high, Articles 79 to 114) and the AEPD's procedures (Title IX). The Supreme Court annulled Articles 11, 18, 38.1(a) in part, 38.2 and 123.2 in 2010 and Article 10.2(b) in 2012.

For a practitioner today the Royal Decree matters as the origin of the security practices Spanish organizations still run, such as the security document, the incident register, access logs and the two-yearly security audit from the medium level, and as the law that governed processing before May 2018. Current obligations come from the GDPR's Article 32 risk-based security duty and the LOPDGDD, and public bodies apply the Esquema Nacional de Seguridad under the LOPDGDD's first additional provision.

Why does it matter?

The Royal Decree was the operating manual of Spanish data protection for a decade: it told every controller which security level its files fell into, what the security document had to contain, when an audit was due and how to notify a file to the AEPD. Its prescriptive model, fixed lists of measures per level rather than a risk analysis, is what the GDPR replaced, and the LOPDGDD's repealing provision removed everything in it that contradicts the Regulation. It still matters for understanding AEPD decisions and contracts from before May 2018, for the residual rules that the LOPDGDD's fourteenth additional provision keeps alive, and because the three security levels remain the vocabulary many Spanish security policies use.

Key benefits include:

  • A clear historical baseline

Title VIII's basic, medium and high levels (Articles 80 and 81) gave every file a defined set of controls, and that classification still appears in Spanish policies and contracts.

  • Documented security

Article 88 required a security document covering scope, measures, staff duties, file structure, incident handling, backups and media transport, the ancestor of today's records of processing and security policies.

  • Evidence of operation

Article 90's incident register, Article 103's access log and Article 96's two-yearly audit from the medium level produced the evidence the AEPD inspected.

  • Rights with procedure

Title III fixed the ARCO rights as independent, free and exercisable by simple means (Article 24), with AEPD enforcement procedures in Title IX.

  • Continuity with the GDPR

Reading the Royal Decree against the GDPR's Article 32 and the LOPDGDD shows what changed: risk analysis replaced fixed levels, and file notification gave way to records of processing.

How does it work?

Title I defines the scope, the terms and the computation of time limits, and clarifies which personal or domestic files fall outside the law. Title II, on principles, develops the data quality rules of Article 8 (fair and lawful processing, specified purposes, no incompatible use, proportionality, accuracy), the rules on consent including that of minors and in electronic communications services, and the status of the processor. Title III sets the ARCO rights: Article 23 makes them personal, Article 24 makes them independent, free of charge and exercisable by a simple means, and Articles 27 to 36 fix the content and time limits of each right. Title IV applies the rules to credit and solvency files and advertising files.

Title V required files to be notified before processing: public files by a published creation instrument and notification to the AEPD within thirty days (Articles 52 to 55), private files by prior notification to the AEPD for entry in the General Data Protection Register (Article 55.2). Title VI made international transfers depend on the authorization of the AEPD Director unless the destination offered an adequate level of protection or a statutory exception applied, with notification for registration in every case (Article 66). Title VII governed voluntary codes of conduct (códigos tipo), binding on those who adhered (Articles 71 to 78). Title IX laid down the AEPD's procedures, including publication of resolutions (Article 116), protection of rights, international transfer authorizations, file registration and sanctions.

Title VIII was the security regulation. Article 80 set three levels and Article 81 assigned them: basic measures for every file; medium measures also for files on administrative or criminal offenses, solvency and credit, tax, financial services, social security and personality profiling; high measures also for data on ideology, union membership, religion, beliefs, racial origin, health or sex life, police data collected without consent and data from gender violence. Chapter III set the automated measures: the security document (Article 88), staff functions, incident register (Article 90), access control (Article 91), media management, identification and authentication, backups; at medium level a security officer, a two-yearly internal or external audit (Article 96), media entry and exit registers and limits on repeated access attempts; at high level encrypted distribution of media and portable devices (Article 101), off-site backups (Article 102), an access log kept for two years (Article 103) and encryption over public or wireless networks (Article 104). Chapter IV applied equivalent measures to paper files (Articles 105 to 114).

Key Elements

  • Three security levels (Articles 80 and 81)

Basic for all files, medium for offense, solvency, tax, financial, social security and profiling files, high for special categories, police and gender violence data; telecom traffic and location data took the high-level access log.

  • Security document (Article 88)

An internal document of mandatory compliance stating scope, measures, staff obligations, file structure, incident procedure, backup and recovery, and media transport and destruction; at medium and high levels also the security officer and periodic controls.

  • Incident register and access log (Articles 90 and 103)

A record of each incident with its type, time, reporter, recipient, effects and corrective measures; at high level a log of every access attempt with user, time, file, type and outcome.

  • Two-yearly audit (Articles 96 and 110)

From the medium level, an internal or external audit at least every two years, and after substantial changes, reporting adequacy, deficiencies and corrective measures to the security officer and available to the AEPD.

  • File notification and the General Register (Article 55)

Public files notified within thirty days of their creation instrument and private files before creation, replaced since 2018 by the GDPR's records of processing.

  • Status after 2018 (LOPDGDD repealing provision)

Organic Law 15/1999 repealed; lower-rank provisions that contradict the GDPR or the LOPDGDD repealed; law-enforcement processing remained under the LOPD until Organic Law 7/2021 of May 26.

What does it cover?

The Royal Decree applied, under Articles 2 and 3, to personal data recorded in any medium that made it susceptible to processing, automated or not, by controllers established in Spain or using means located in Spain, in both the public and the private sector, with exclusions for purely personal or domestic activities and for deceased persons. Since May 25, 2018 that scope has been governed by the GDPR and the LOPDGDD; the Royal Decree's provisions apply only where they do not contradict them, and Title VIII's fixed measures no longer stand in for the risk-based security the GDPR's Article 32 requires. Public-sector security is set by the Esquema Nacional de Seguridad under the LOPDGDD's first additional provision.

What are its objectives?

The Royal Decree's preamble states its purpose: to develop Organic Law 15/1999 in a single text, extending the previous security regulation to non-automated files, giving the processor a clear status and setting the AEPD's procedures. Its titles served five ends.

Apply the data quality principles and consent rules of the Organic Law in detail, including for minors and electronic services (Title II).

Guarantee the rights of access, rectification, cancellation and opposition with fixed procedures and time limits (Title III).

Make every file known to the AEPD through prior notification and the General Data Protection Register (Title V).

Impose security measures proportionate to the sensitivity of the data through three defined levels (Title VIII).

Give the AEPD orderly procedures for protecting rights, authorizing transfers and sanctioning breaches (Title IX).

Framework in Context

The Royal Decree implemented Organic Law 15/1999, Spain's transposition of Directive 95/46/EC, and it carried forward the 1999 security regulation (Royal Decree 994/1999) that it repealed. The GDPR displaced that framework on May 25, 2018, and the LOPDGDD of December 5, 2018 replaced the Organic Law, repealed whatever in the Royal Decree contradicts the Regulation and, in its first additional provision, pointed public bodies to the Esquema Nacional de Seguridad for the security of personal data. The LOPDGDD's fourth transitional provision kept the LOPD and its implementing rules for law-enforcement processing until Organic Law 7/2021 transposed Directive (EU) 2016/680, and its fourteenth additional provision keeps the rules adopted under Article 13 of Directive 95/46/EC until they are expressly replaced. No separate LOPDGDD page exists on this site; the GDPR page describes the regime that applies today.

Common Framework Mappings

Organizations that still carry controls from the Royal Decree map them to the frameworks below so that the security document, access logs and audits they already run serve the GDPR and current security standards.

Mapped frameworks include:

CIS Controls v8.1

GDPR

ISO 27001:2022

ISO 27002:2022

ISO 27701

NIST CSF 2.0

NIST Privacy Framework v1.0

NIST 800-53 Rev.5

PCI DSS 4.0.1

SOC 2

SMARTSUITE

How SmartSuite Supports Royal Decree 1720/2007

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Privacy Management to hold the processing inventory that replaced file notification, the security level or risk rating of each processing activity, the policies that descended from the security document, the incident register and the two-yearly audit schedule, with the GDPR Article 32 measures linked to the legacy controls so the AEPD sees one coherent record.

Processing Inventory and Security Levels

Record each processing activity with its data categories, the historical basic, medium or high level under Article 81 and the current GDPR Article 32 risk rating.

Security Policy Descended from the Security Document

Maintain the policies, staff duties, backup and media rules that Article 88 required, with review cadences and evidence of approval.

Access Control and Access Log

Track user profiles, authorized access and periodic reviews under Article 91, and retain access logs for the periods Article 103 set and the GDPR now justifies.

ARCO and GDPR Rights Requests

Manage access, rectification, erasure, opposition and the GDPR's added rights with deadlines, identity checks and an audit trail.

Incident Register and Breach Notification

Log incidents with the fields of Article 90 and run the GDPR's 72-hour notification to the AEPD from the same record.

Audit Program and AEPD Evidence

Schedule the two-yearly audits that Article 96 established and keep reports, findings and corrective actions ready for the AEPD.

Related frameworks

GDPR

The GDPR (Regulation (EU) 2016/679) sets principles, lawful bases, individual rights and accountability duties for personal data, with fines up to EUR 20 million or 4 percent of turnover.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO 27701

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.

NIST Privacy Framework v1.0

The NIST Privacy Framework Version 1.0 is a voluntary tool for managing privacy risk: five Functions, 18 Categories, 100 Subcategories, Profiles and four Implementation Tiers.

SOC 2

SOC 2 is the AICPA examination, under AT-C 105 and 205, of a service organization's controls against the 2017 Trust Services Criteria, issued as a type 1 or type 2 attestation report.

FAQ

Frequently Asked Questions For Spain Royal Decree 1720/2007 (Regulation Implementing Organic Law on Data Protection)

Only residually. The GDPR has applied since May 25, 2018, and Organic Law 3/2018 (LOPDGDD) repealed Organic Law 15/1999, which the Royal Decree implemented, together with every lower-rank provision that contradicts the GDPR or the LOPDGDD (repealing provision, paragraph 3). The BOE still publishes the Royal Decree as a consolidated text with its 2010 and 2012 annulments, so provisions compatible with the GDPR can still be cited, but security, registration and transfer obligations now come from the GDPR and the LOPDGDD.

Article 80 classified security measures as basic, medium and high, and Article 81 assigned them. Every file took the basic measures. Medium measures were added for files on administrative or criminal offenses, solvency and credit, tax administration, financial services, social security and personality profiling. High measures were added for data on ideology, union membership, religion, beliefs, racial origin, health or sex life, police data collected without consent and data from gender violence, with the high-level access log also applied to telecom traffic and location data.

Article 88 required an internal document, binding on staff with access to the systems, stating its scope and the resources protected, the measures and procedures that achieved the required level, staff functions and obligations, the structure of the files and the systems that processed them, the incident notification and response procedure, backup and recovery procedures, and the rules for transporting, destroying or reusing media and documents. At medium and high levels it also named the security officer and the periodic compliance checks.

Article 96 required files at the medium level and above to undergo an internal or external audit at least every two years, and an extraordinary audit after substantial changes to the information system, which restarted the two-year count. The report had to assess the adequacy of the measures against the law and the regulation, identify deficiencies and propose corrective or complementary measures; it went to the security officer and the controller and was kept available for the AEPD. Article 110 set the same two-year cycle for paper files at medium level and above.

Title V required public files to be created by a published instrument and notified to the AEPD within thirty days, and private files to be notified before creation, for entry in the General Data Protection Register (Articles 52 to 55). The GDPR removed prior notification: controllers and processors now keep records of processing activities under Article 30 of the Regulation, and the LOPDGDD requires public bodies and certain others to publish an inventory of their processing activities.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.