LPDP
Personal Data Protection Law No. 29733
51 sections indexed, 13 with our notes. Our index and notes; the law itself is at its source: official text ↗
Preliminary Title General Provisions
Definitions
Scope of application
Title I Guiding Principles
Principle of legality
Principle of consent
Principle of purpose
Principle of proportionality
Principle of quality
Principle of security
Principle of availability of remedies
Principle of adequate level of protection
Value of the principles
Title II Processing of Personal Data
Scope of processing of personal data
Limits on consent for processing
Cross-border flow of personal data
Security of processing
Confidentiality of personal data
Title III Rights of the Data Subject
Right to information
Right of access
Right to updating, inclusion, rectification and deletion
Right to prevent disclosure
Right to object
Right to objective processing
Right to protection (tutela)
Right to compensation
Consideration (fees)
Limitations
Title IV Obligations of the Database Owner and the Processor
Obligations
Title V Personal Data Banks
Creation, modification or cancellation of personal data banks
Provision of personal data processing services
Codes of conduct
Title VI National Personal Data Protection Authority
Competent body and legal regime
Functions of the National Authority
National Personal Data Protection Register
Confidentiality
Resources of the National Authority
Title VII Administrative Infringements and Sanctions
Sanctioning procedure
Infringements
Administrative sanctions
Coercive fines
Final Supplementary Provisions Final Supplementary Provisions
Regulations under the law
Security directive
Adjustment of the Ministry of Justice's management documents and TUPA
Regulatory alignment
Pre-existing personal data banks
Habeas data
Powers of Indecopi
Sensitive information
Tax administration powers unaffected
Funding
Entry into force
No section matches. Try another word, or clear the topic.
Start from the question. Pick a topic to see the sections of LPDP that deal with it, and how 39 laws compare on it.
Scope and definitions
In LPDP
Reach abroad across 39 laws
| |
2 | Covers non-established controllers that offer goods or services to, or profile, people in Peru; they must appoint a representative. |
| |
3 | Applies regardless of location if processing occurs in Brazil, targets goods or services to people in Brazil, or data was collected in Brazil. |
| |
3 | Covers Egyptians anywhere, non-Egyptians in Egypt, and non-Egyptians abroad where the data concerns Egyptians or residents and the act is also criminal there. |
| |
3 | Applies to controllers in Ghana, foreign controllers using equipment or processors in Ghana, and processing of information originating in Ghana. |
| |
3 | Applies inside Indonesia and to acts abroad with legal effect in Indonesia or on Indonesian citizens abroad. |
| |
3 | Applies to controllers and processors outside Kenya that process personal data of data subjects located in Kenya. |
| |
3 | Applies to controllers and processors outside Nigeria processing personal data of data subjects in Nigeria. |
| |
3 | Applies to processing in the Kingdom and to processing outside it of personal data of individuals residing in the Kingdom, by any means. |
| |
3 | Applies to any circumstances that have an effect in Switzerland, even if initiated abroad; some foreign controllers must appoint a Swiss representative. |
| |
3 | Applies to controllers and processors outside the UAE that process personal data of data subjects inside the State. |
| |
3 | Applies to anyone collecting or processing personal data in Uganda, and to anyone outside Uganda handling data relating to Ugandan citizens. |
| |
3 | Applies to foreign entities in Vietnam and to foreign entities directly processing data of Vietnamese citizens and residents in Vietnam. |
| |
2 | Applies to organizations abroad with an Australian link, including carrying on business in Australia. |
| |
2 | Applies to for-profit businesses doing business in California that meet revenue or data-volume thresholds, wherever located, for California residents' data. |
| |
2 | Applies to commercial activity with a real and substantial connection to Canada, and to interprovincial or international disclosures for consideration. |
| |
2 | Applies outside China when providing products or services to people in China or analyzing their behavior; foreign handlers need a local representative. |
| |
2 | Applies to foreign controllers offering goods or services to, or monitoring behavior of, residents of Ecuador; non-residents must appoint an agent in Ecuador. |
| |
2 | Applies to non-EU controllers offering goods or services to, or monitoring the behavior of, people in the EU. |
| |
2 | Applies to processing outside India connected with offering goods or services to data principals in India. |
| |
2 | Applies to foreign businesses handling personal information of people in Japan in connection with supplying goods or services to them. |
| |
2 | Applies to overseas agencies carrying on business in New Zealand, even without a place of business or commercial purpose. |
| |
2 | Applies to processing outside the Philippines of citizens' or residents' data where the entity has a Philippine link (contract, branch, business, data collected there). |
| |
2 | Applies to enterprises collecting, holding, using or communicating personal information about people in Quebec in the course of business. |
| |
2 | Applies to organizations whether or not resident or with an office in Singapore, in practice when collecting, using or disclosing data in Singapore. |
| |
2 | No express territorial clause, but foreign controllers meeting Decree thresholds without a Korean address must designate a domestic agent; PIPC applies the Act to services targeting Koreans. |
| |
2 | Applies to controllers or processors abroad that offer goods or services to people in Thailand or monitor their behavior in Thailand. |
| |
2 | The law is silent on territory, but the Board requires foreign controllers processing data of people in Turkey to register in VERBIS through a local representative. |
| |
2 | Applies to non-UK controllers offering goods or services to, or monitoring behavior of, people in the UK. |
| |
2 | Applies to non-established controllers offering goods or services to, or analyzing behavior of, people in Uruguay, or using means located there. |
| |
1 | Applies to processing in Colombia and to foreign controllers or processors when Colombian law applies under international norms or treaties. |
| |
1 | Applies to controllers or processors incorporated in DIFC, and to processing in DIFC including through stable arrangements, wherever the controller sits. |
| |
1 | Applies to data users controlling data in or from Hong Kong; no express reach over foreign businesses targeting Hong Kong residents. |
| |
1 | No express extraterritorial clause; the PPA applies the law where processing has a material impact on Israelis, e.g. targeting the Israeli market or local servers. |
| |
1 | Applies to persons established in Malaysia, or using equipment in Malaysia other than for transit; foreign users must nominate a local representative. |
| |
1 | Law applies nationwide; the Regulation also reaches non-established controllers that use means located in Mexico (other than transit). |
| |
1 | Applies to responsible parties domiciled in South Africa, or not domiciled but using automated or non-automated means in the Republic. |
| |
1 | Applies to controllers active in Zimbabwe and to controllers not established there that use means located in Zimbabwe. |
| |
0 | No extraterritorial provision; applies to files and databases, public or private, in Argentina. |
| |
0 | No extraterritorial provision in the current text. |
Principles
In LPDP
- Article 4Principle of legality
- Article 5Principle of consent
- Article 6Principle of purpose
- Article 7Principle of proportionality
- Article 8Principle of quality
- Article 9Principle of security
- Article 10Principle of availability of remedies
- Article 11Principle of adequate level of protection
- Article 12Value of the principles
We don't score this topic in the comparison. The sections on the left are the place to start.
Lawful basis and consent
In LPDP
- Article 5Principle of consent
- Article 13Scope of processing of personal data
Consent is the default basis; exceptions listed in the Law (public entities, public sources, contracts, health, anonymized data). No legitimate interests.
- Article 14Limits on consent for processing
Consent is the default basis; exceptions listed in the Law (public entities, public sources, contracts, health, anonymized data). No legitimate interests.
Lawful basis across 39 laws
| |
3 | Consent is the default basis; exceptions listed in the Law (public entities, public sources, contracts, health, anonymized data). No legitimate interests. |
| |
3 | Processing is unlawful without consent, except listed cases such as public sources, state functions, basic listings, contracts and certain financial operations. No legitimate interests. |
| |
3 | Consent is the default basis, with limited statutory exceptions. |
| |
3 | Processing only when a law authorizes it or the holder expressly consents; narrow exceptions for public-source and certain internal data. No legitimate interests. |
| |
3 | Prior, express and informed authorization is required, with narrow exceptions (public authority requests, public data, medical emergencies, civil registry). No legitimate interests. |
| |
3 | Explicit consent is the default; other grounds are contract, legal obligation and exercising legal rights. No legitimate interests ground. |
| |
3 | Consent is the default basis; processing without consent only for listed 'legitimate uses' (s.7). No general legitimate interests ground. |
| |
3 | Informed consent is the main basis; the alternative is statutory authority. There is no legitimate-interests basis, and new purposes need new consent. |
| |
3 | Consent is the general rule; non-consent processing only where necessary for contract, legal obligation, vital interests, justice and similar listed grounds. |
| |
3 | Consent is the default basis; processing without consent only under listed exceptions (law, public sources, legal relationship, emergency, health care, court order). No legitimate interests. |
| |
3 | Consent is the default basis for use and communication, with listed exceptions. |
| |
3 | Processing without consent is prohibited except in listed cases (public interest, contract, legal obligation, public data and others); no legitimate interests ground. |
| |
3 | Prior consent is the default; exceptions cover law, national security, medical purposes, legal obligation and contracts. No legitimate interests ground. |
| |
3 | Consent is the default basis, with exceptions for public sources, state functions, limited listings, contracts and domestic use. No legitimate interests. |
| |
3 | Consent is the default basis; the Law adds listed exceptions such as contract performance, legal obligations and protecting legitimate rights. |
| |
2 | Consent or six other bases (contract/HR, legal duty, emergencies, news, public data, other laws); no legitimate interests. |
| |
1 | No lawful-basis list; collection must be reasonably necessary, and secondary use needs consent, reasonable expectation or an exception. |
| |
1 | Ten legal bases including consent, legal obligation, contract, credit protection and legitimate interests. |
| |
1 | Multiple bases including consent, contract, legal obligation, vital interests and legitimate interests. |
| |
1 | Eight bases including consent, legal obligation, contract, vital interests, public interest and legitimate interest. |
| |
1 | Six lawful bases, including consent, contract, legal obligation, vital interests, public task and legitimate interests. |
| |
1 | Prior consent or listed grounds, including contract, legal obligation, and legitimate interests of the controller or a third party. |
| |
1 | No lawful-basis list; collection must be lawful, fair and for a purpose directly related to the data user's functions. |
| |
1 | Consent, contract, legal obligation, vital interests, public interest/authority, and legitimate interests. |
| |
1 | No list of lawful bases; purpose must be specified and notified, and consent is needed for use beyond purpose and for most third-party provision. |
| |
1 | Consent or listed necessity grounds, including legitimate interests unless unwarranted given harm to the data subject. |
| |
1 | No lawful-basis list; collection must be for a lawful purpose connected to the agency's functions and necessary for it. |
| |
1 | Consent or listed necessity grounds, including legitimate interests unless the data subject would not reasonably expect the processing. |
| |
1 | Multiple bases: consent, contract, legal obligation, vital interests, public order, public authority and legitimate interests. |
| |
1 | Consent plus other bases, including legitimate interests (since 2023 amendment) after a documented assessment; not for sensitive data. |
| |
1 | Consent, deemed consent, or exceptions in the First and Second Schedules, including a legitimate interests exception. |
| |
1 | Six lawful grounds including consent, contract, legal obligation, and legitimate interests of the responsible party or a third party. |
| |
1 | Consent, law, public duties, contract, vital interests, legitimate interests that clearly override data subject rights, and urgent public safety. |
| |
1 | No closed list of bases; processing must follow the principles, and breaches are justified by consent, an overriding private or public interest, or law. |
| |
1 | Consent or six other bases: research, vital interests, contract, public task, legitimate interests, and legal obligation. |
| |
1 | Explicit consent is the default, but processing without consent is allowed on listed grounds, including contract, legal obligation and legitimate interests. |
| |
1 | Six GDPR bases plus a new 'recognised legitimate interests' basis (Annex 1) needing no balancing test, in force 5 Feb 2026. |
| |
1 | Consent or listed grounds including legal obligation, vital interests, public interest and legitimate interests of the controller or third party. |
| |
0 | No lawful-basis requirement; notice at collection plus purpose limitation, with opt-out of sale/sharing. |
Sensitive data
In LPDP
- Article 13Scope of processing of personal data
Sensitive data, including biometric, genetic and neural data, requires written consent by signature or equivalent.
- DCF-8Sensitive information
Sensitive data across 39 laws
| |
2 | Sensitive data, including biometric, genetic and neural data, requires written consent by signature or equivalent. |
| |
3 | Processing sensitive data requires both written explicit consent and a licence from the Personal Data Protection Center. |
| |
2 | No one can be compelled to provide sensitive data; processing only for general interest authorized by law, or dissociated statistics or science. |
| |
2 | Sensitive information may be collected only with consent and where reasonably necessary, or under listed exceptions. |
| |
2 | Sensitive data processed only with specific, highlighted consent or under listed exceptions. |
| |
2 | Sensitive data cannot be processed unless a law authorizes it, the holder consents, or it is needed to grant health benefits. |
| |
2 | Sensitive data needs a specific purpose, sufficient necessity, strict safeguards and separate consent. |
| |
2 | Processing sensitive data is prohibited except with explicit authorization or listed exceptions; no activity may be conditioned on providing it. |
| |
2 | Special categories may not be processed unless a listed condition, such as explicit consent, applies. |
| |
2 | Processing sensitive data is prohibited unless a listed exception applies, such as explicit consent. |
| |
2 | Special categories (health, biometrics, religion, etc.) are prohibited unless explicit consent or another listed exception applies. |
| |
2 | Special personal data (health, religion, ethnicity, sexual life and others) is prohibited unless consent or a listed exception applies. |
| |
2 | Special care-required information (race, creed, medical history, criminal record, etc.) needs prior consent to acquire and cannot be shared by opt-out. |
| |
2 | Sensitive personal data may be processed only on listed grounds; health data only by or under health professionals. |
| |
2 | Health, political, religious, offence and biometric data need explicit consent or a listed exception. |
| |
2 | Sensitive data needs express written consent (signature, e-signature or other authentication); databases of sensitive data need a legitimate, specific justification. |
| |
2 | Sensitive data (genetic, biometric, health, religion, politics, ethnicity, sex life, union membership) needs specific consent or a listed ground. |
| |
2 | Processing sensitive and privileged information is prohibited except for listed cases such as specific consent, legal authorization or medical emergencies. |
| |
2 | Sensitive data needs explicit consent or a listed basis; legitimate interests cannot be used; DPIA and DPO triggers apply. |
| |
2 | Special personal information is prohibited unless consent or a listed exception applies; the Regulator may authorize processing in the public interest. |
| |
2 | Sensitive data (beliefs, union, politics, health, sex life, etc.) may be processed only with separate consent or where law requires or permits. |
| |
2 | Sensitive data (incl. genetic, biometric, social assistance, criminal proceedings) needs express consent if relying on consent; disclosing it to third parties needs justification. |
| |
2 | Sensitive data (health, beliefs, criminal records, biometrics, genetics, etc.) requires explicit consent unless a listed exception applies. |
| |
2 | Processing special categories, including appearance, clothing and association membership, is prohibited unless an Art. 6(3) exception applies, such as explicit consent, law or employment obligations. Board-set measures are required. |
| |
2 | Special personal data (beliefs, politics, sexual life, financial, health) may be processed only under listed exceptions, such as freely given consent. |
| |
2 | Special categories prohibited unless explicit consent or listed condition applies; many conditions need an appropriate policy document. |
| |
2 | No one may be compelled to provide sensitive data; processing needs express written consent or legal authorization for general interest. |
| |
2 | Sensitive data list set by Government (now includes banking, credit, location and behavioral data); extra safeguards and notice required. |
| |
2 | Sensitive, genetic, biometric and health data require written consent or listed exceptions; some uses need Authority authorization. |
| |
1 | Sensitive personal information defined; consumers may limit its use to listed necessary purposes, with notice required. |
| |
1 | No special category; sensitivity drives the form of consent, generally express for sensitive information. |
| |
1 | 'Specific' data (health, biometric, genetic, criminal, child, financial) defined; mainly triggers DPIA and DPO duties rather than a ban. |
| |
1 | 'Information of special sensitivity' is broadly defined (incl. biometrics, location, financial data). It brings higher security levels, PPA notification above 100,000 people, DPO triggers and higher fines, but no ban. |
| |
1 | Sensitive information requires express consent for secondary uses and communication. |
| |
1 | Sensitive data is defined; no separate prohibition, but large-volume sensitive processing triggers DPO and DPIA duties. |
| |
0 | No special category of sensitive data. |
| |
0 | No separate sensitive data category; volume and sensitivity only factor into Significant Data Fiduciary designation. |
| |
0 | No special category in the Act; Biometric Processing Privacy Code 2025 regulates biometrics. |
| |
0 | No statutory special category; PDPC treats some data as sensitive when assessing security and penalties. |
People's rights
In LPDP
- Article 18Right to information
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 19Right of access
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 20Right to updating, inclusion, rectification and deletion
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 21Right to prevent disclosure
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 22Right to object
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 23Right to objective processing
Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects).
- Article 24Right to protection (tutela)
- Article 25Right to compensation
Rights across 39 laws
| |
3 | Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects). |
| |
3 | Confirmation, access, correction, anonymization/blocking/deletion, portability, consent revocation, objection and review of automated decisions. |
| |
3 | Know/access, delete, correct, portability, opt-out of sale/sharing, limit sensitive data, and ADMT opt-out and access rights. |
| |
3 | Know and decide, restrict or refuse, access and copy, portability, correction, deletion, explanation and refusal of solely automated decisions. |
| |
3 | Withdraw consent, access, rectification, erasure, objection (incl. direct marketing), restriction, portability and automated-decision rights. |
| |
3 | Information, access, rectification, deletion, objection, portability, suspension of processing, and not to be subject to solely automated decisions. |
| |
3 | Access, rectification, erasure, restriction, portability, objection and rights on solely automated decisions. |
| |
3 | Information, correction, access, erasure, withdrawal, objection to automated decisions, restriction/suspension, portability and compensation. |
| |
3 | Information, access, objection, correction, deletion, restriction, portability, and the right not to be subject to solely automated decisions. |
| |
3 | Access, copy, rectification, erasure, restriction, portability, objection (absolute for direct marketing) and safeguards against solely automated decisions. |
| |
3 | Access, rectification, portability, de-indexing or cessation of dissemination, consent withdrawal, and information on automated decisions. |
| |
3 | Access, correction, deletion, objection (including direct marketing), protection from solely automated decisions, and restriction in limited cases. |
| |
3 | Access, portability (transmission), correction, erasure, suspension of processing, and the right to object to or seek explanation of automated decisions. |
| |
3 | Access, rectification, deletion, restriction/prohibition of processing, objection, data portability, and a right to be heard on automated individual decisions. |
| |
3 | Access, portability, objection, erasure, restriction and rectification. |
| |
3 | Information and access, portability, correction and erasure, restriction, objection (incl. direct marketing) and rights against automated decisions. |
| |
3 | Access, rectification, erasure, restriction, portability, objection, and safeguards on significant automated decisions, plus a right to complain to the controller. |
| |
2 | Access, rectification, updating and suppression; removal or blocking of marketing data at any time. |
| |
2 | Information (access), modification, deletion and blocking; opposition to use for advertising, market research or surveys. |
| |
2 | Know, update and correct data; proof of authorization; information on use; complain to SIC; revoke authorization or request deletion. |
| |
2 | Know and access data, withdraw consent, correct and erase, restrict processing, object, and be told of breaches. |
| |
2 | Access, correction and deletion, the right to prevent processing, direct marketing opt-out, and rights against solely automated decisions. |
| |
2 | Access, correction or deletion of inaccurate data, deletion from direct-mail databases (opt-out), and erasure for EEA-origin data. |
| |
2 | Disclosure (access), correction/deletion, cessation of use or erasure, cessation of third-party provision, and disclosure of third-party provision records. |
| |
2 | Access, correction, withdrawal of consent, prevent damaging processing, stop direct marketing and data portability. |
| |
2 | ARCO rights: access, rectification, cancellation and opposition, including objection to automated processing with significant effects. No portability right. |
| |
2 | Right to be informed, access, rectification, erasure or blocking, objection (incl. direct marketing), portability and damages. |
| |
2 | Rights to be informed, access and copy, correction, restriction and destruction; no portability right. |
| |
2 | Learn whether data is processed and get information (access), rectification, erasure, notice to third-party recipients, objection to solely automated outcomes, and compensation. |
| |
2 | Access, correction and deletion, objection to damaging processing, direct marketing opt-out, and rights against solely automated decisions. |
| |
2 | Access, rectification, updating, inclusion, suppression; challenge automated decisions; removal or blocking of marketing data. |
| |
2 | Be informed, consent and withdraw, access, correction, deletion, restriction, objection, complaint and lawsuit. |
| |
2 | Information, access, objection, correction and deletion of false data, and protection from solely automated decisions. |
| |
1 | Access and correction; no statutory erasure, portability or objection rights (direct marketing opt-out aside). |
| |
1 | Access, correction, and withdrawal of consent; no statutory deletion, portability or automated-decision rights. |
| |
1 | Access and correction only. |
| |
1 | Access to information, correction, completion, updating and erasure, grievance redressal and nomination. No portability, objection or automated-decision rights. |
| |
1 | Access and correction only. |
| |
1 | Access and correction; data portability enacted but not yet in force; right to withdraw consent. |
Registration and licensing
In LPDP
- Article 34National Personal Data Protection Register
Creation, modification and cancellation of personal data banks must be registered (free, automatic approval) with the National Registry.
Registration across 39 laws
| |
2 | Creation, modification and cancellation of personal data banks must be registered (free, automatic approval) with the National Registry. |
| |
3 | Controllers and processors need Center licences with fees capped at EGP 2 million, plus permits for transfers, marketing and CCTV. |
| |
3 | Every data controller must register with the Commission, pay a fee and renew every two years; processing unregistered is an offense. |
| |
3 | Controllers and processors must register, pay tiered fees (KES 4,000-40,000) and renew every 24 months; small entities exempt unless in listed sectors. |
| |
3 | All collectors, processors and controllers must register with the PDPO, renew annually and pay fees (UGX 100,000 reported). |
| |
3 | Controllers processing data of 50 or more people need a POTRAZ licence, tiered USD 50-2,500, renewed every 12 months. |
| |
2 | Public databases and private databases that go beyond exclusively personal use must register with the AAIP registry. |
| |
2 | Controllers and processors must register by filing a notification of processing with the Commissioner, kept up to date, with fees. |
| |
2 | Controllers must register with and keep updated the National Personal Data Protection Registry. |
| |
2 | Prescribed classes of controllers (banking, insurance, health, telecoms, education, real estate and others) must register and renew certificates with fees. |
| |
2 | Controllers and processors of major importance must register, with fees of N10,000-250,000 by tier; ordinary-tier entities renew annually. |
| |
2 | Register processing systems and DPO if 250+ employees, sensitive data of 1,000+ individuals, or risky processing; renew annually. |
| |
2 | Controllers must register in VERBIS before processing, unless exempt (under 50 employees and under TRY 100m balance sheet, or under 10 and TRY 10m if mainly sensitive data). |
| |
2 | Most controllers must pay an annual data protection fee to the ICO unless exempt. |
| |
2 | All public and private databases, other than purely personal ones, must be registered with the URCDP, including foreign controllers in scope. |
| |
1 | No general registration; data brokers must register annually with the CPPA under the Delete Act. |
| |
1 | Companies and non-profits above an asset threshold (and public entities) must register databases in the SIC's National Database Registry (RNBD) and update annually. |
| |
1 | No PDP Law registration; electronic system operators register with the ministry under GR 71/2019. |
| |
1 | Registration only for public-body databases and databases of 10,000+ people mainly used to transfer data for payment; notify the PPA of special-sensitivity databases above 100,000 people. |
| |
1 | No general registration; businesses using the opt-out route for third-party provision must notify the PPC in advance. |
| |
1 | National Register of Controllers applies to public entities, controllers whose main activity is processing, sensitive-data processors and some individuals; no fees seen. |
| |
1 | No general controller registration. Information Officers must be registered; prior authorization needed for listed processing such as credit reporting. |
| |
1 | Public institutions must register personal information files with the PIPC; no registration for private controllers. |
| |
1 | No registration for private controllers; federal bodies must report their processing activities to the FDPIC. |
| |
1 | No controller registration; impact assessment dossiers are filed with the Ministry of Public Security instead. |
| |
0 | No registration of organizations. |
| |
0 | No registration for private controllers; the Civil Registry keeps a registry of public bodies' databases. |
| |
0 | No general controller registration; foreign handlers report their China representative to regulators. |
| |
0 | No general registration; controllers communicate DPO contact details to the supervisory authority. |
| |
0 | Data user return scheme exists but has not been activated for any class of data user. |
| |
0 | No general controller registration. Only Consent Managers must register with the Data Protection Board. |
| |
0 | No registration or notification of databases with the regulator. |
| |
0 | No registration. |
| |
0 | No controller registration. |
| |
0 | No registration of controllers. |
| |
0 | No controller registration or licensing. |
| |
– | Not addressed |
| |
– | Not addressed |
| |
– | Not addressed |
Security
In LPDP
We don't score this topic in the comparison. The sections on the left are the place to start.
Transfers abroad
In LPDP
- Article 15Cross-border flow of personal data
Transfers allowed to adequate countries or with safeguards such as model clauses; every cross-border flow must be notified to the Authority.
Transfers abroad across 39 laws
| |
2 | Transfers allowed to adequate countries or with safeguards such as model clauses; every cross-border flow must be notified to the Authority. |
| |
3 | Transfers need CAC security assessment, certification or the CAC standard contract, plus notice and separate consent. |
| |
3 | Transfers abroad need equivalent protection in the destination and a licence or permit from the Center, unless a listed exception applies. |
| |
3 | Transfer impact assessment dossier must be filed with MPS within 60 days of first transfer, plus a written agreement with the recipient. |
| |
2 | Transfers prohibited to countries or bodies without adequate protection, except listed cases such as treaties, judicial cooperation and other statutory exceptions. |
| |
2 | Transfers allowed via adequacy, ANPD standard clauses (mandatory since Aug 2025), ANPD-approved specific clauses or BCRs, or specific consent. |
| |
2 | Transfers to countries without adequate protection are prohibited unless an exception applies (explicit consent, contract, treaty) or SIC issues a declaration of conformity. |
| |
2 | Transfer if destination has adequate protection or with appropriate safeguards, or listed derogations. |
| |
2 | Transfers allowed to countries declared adequate by the regulator, or with binding guarantees or binding corporate rules; listed exceptions include explicit consent. |
| |
2 | Transfers outside the EEA need an adequacy decision or appropriate safeguards (SCCs, BCRs), or a listed derogation. |
| |
2 | Destination must offer equal or higher protection, else adequate binding safeguards, else consent; BCRs need DPA approval under GR 33. |
| |
2 | Allowed only if the destination's protection is no lower than Israel's, or under listed exceptions such as consent, EU-adequate or Convention 108 countries, group or contractual safeguards; no PPA approval. |
| |
2 | Transfer abroad needs prior consent after information on the destination regime, an adequate country (EU/UK), or a recipient with equivalent systems. |
| |
2 | Transfers need proof of appropriate safeguards to the Data Commissioner or a listed condition; sensitive data needs consent. |
| |
2 | Transfer allowed if destination law is substantially similar or protection equivalent, or under listed exceptions (consent, contract, due diligence). |
| |
2 | Domestic and international transfers need consent via the privacy notice, with listed exceptions; recipient assumes the controller's obligations, typically by contract. |
| |
2 | Overseas disclosure allowed only with comparable safeguards, consent after warning, prescribed binding scheme or country, or contract. |
| |
2 | Transfers need an adequate level of protection in the destination or a listed basis such as informed consent. |
| |
2 | Before communicating data outside Quebec, conduct a PIA confirming adequate protection and sign a written agreement. |
| |
2 | Transfers need a specified purpose, minimum data, and adequacy, BCRs, standard clauses, certification or listed derogations, with a risk assessment. |
| |
2 | Transfers only under prescribed requirements ensuring a comparable standard of protection (contracts, BCRs, certification, consent). |
| |
2 | Transfers abroad allowed only with adequate protection (law, binding corporate rules or agreement), consent, contract necessity, or data subject benefit. |
| |
2 | Transfer abroad needs separate consent, a statutory basis, contract necessity with disclosure, a certified recipient, or a PIPC-recognized country. |
| |
2 | Allowed to Federal Council-listed adequate countries; otherwise FDPIC-recognized SCCs, FDPIC-approved BCRs, or notified clauses; limited derogations such as explicit consent. |
| |
2 | Destination must have adequate standards, or a listed exception applies (consent, contract, etc.); intra-group transfers need a PDPC-certified policy. |
| |
2 | Needs a Board adequacy decision; else Board-approved BCRs or undertakings, or a Board standard contract filed within five business days. Incidental transfers allowed on listed grounds. |
| |
2 | Transfer to countries with adequate protection approved by the Data Office, or via contract, explicit consent and other listed grounds. |
| |
2 | Processing or storage abroad requires adequate protection at least equivalent to the Act, or data subject consent; onward transfer needs express consent. |
| |
2 | Transfers need UK adequacy regulations under a 'not materially lower' data protection test, or appropriate safeguards such as the IDTA or Addendum. |
| |
2 | Transfers prohibited to countries without adequate protection, except listed cases (explicit consent, contract, vital interest); URCDP may authorize transfers with safeguards. |
| |
2 | Transfers abroad need adequate protection in the recipient country or a listed derogation such as unambiguous consent. |
| |
1 | Take reasonable steps so overseas recipients comply with APPs; discloser stays accountable. Whitelist power added in 2024. |
| |
1 | Organization remains accountable and must use contracts or other means to ensure comparable protection by third-party processors. |
| |
1 | No general transfer restriction; controllers must ensure foreign processors comply and list transfer countries at registration. |
| |
1 | No adequacy regime; controller stays accountable for data sent abroad and must ensure comparable protection by contract or other means. |
| |
0 | No international transfer restriction in the current text. |
| |
0 | No transfer restriction in force; s.33 never commenced. PCPD recommends model contract clauses. |
| |
0 | Transfers allowed except to countries the government restricts by notification; conditions may be set by order. |
| |
– | Not addressed |
Regulator
In LPDP
We don't score this topic in the comparison. The sections on the left are the place to start.
Complaints and enforcement
In LPDP
- Article 10Principle of availability of remedies
- Article 24Right to protection (tutela)
Anyone harmed may claim compensation; denied rights can be pursued before the Authority or by habeas data action.
- Article 25Right to compensation
Anyone harmed may claim compensation; denied rights can be pursued before the Authority or by habeas data action.
- Article 37Sanctioning procedure
- Article 38Infringements
- Article 39Administrative sanctions
- Article 40Coercive fines
Private action across 39 laws
| |
2 | Anyone harmed may claim compensation; denied rights can be pursued before the Authority or by habeas data action. |
| |
3 | Controllers and processors must compensate material or moral damage; individual and collective actions allowed. |
| |
3 | Private right of action for data breaches from failure to maintain reasonable security: USD 107-799 per consumer per incident, class actions allowed. |
| |
3 | Tort claims with presumed fault of the handler; prosecutors and designated organizations may bring public interest suits. |
| |
3 | Right to compensation for material or non-material damage; representative bodies may bring claims, including collective redress. |
| |
3 | Civil tort claims plus statutory damages without proof of harm: up to ILS 10,000 for listed database violations, more for privacy infringement. Class actions are available. |
| |
3 | Courts must award punitive damages of at least CAD 1,000 for intentional or grossly negligent infringements; class actions available. |
| |
3 | Damages with reversed burden of proof, up to 5x for intentional or negligent leaks, statutory damages up to KRW 3 million, and group suits. |
| |
3 | Strict liability for damages, plus punitive damages up to twice actual damages; class actions available under civil procedure. |
| |
2 | Habeas data court action to access, rectify, suppress or keep data confidential; liability for damages also arises. |
| |
2 | Statutory tort for serious invasions of privacy (from 10 Jun 2025); representative complaints to OAIC. |
| |
2 | Controller must compensate material and moral damage from improper processing; amount set by the judge. |
| |
2 | Data subjects complain to SIC after exhausting the controller process; damages are claimed under general civil liability. |
| |
2 | Data subjects may sue directly in DIFC Courts for financial and non-financial harm, including distress. |
| |
2 | Data subjects may sue for damages (Constitution art. 92 habeas data) and must be guaranteed full reparation. |
| |
2 | Victims keep the right to claim compensation; entities are jointly liable for employees' violations. |
| |
2 | Individuals who suffer damage or distress from a contravention are entitled to compensation, subject to a reasonable care defense. |
| |
2 | Individuals suffering damage, including injury to feelings, may claim compensation; PCPD may give legal assistance. |
| |
2 | Data subjects may sue for compensation for violations of processing. |
| |
2 | Individuals may sue to compel disclosure, correction or cessation, and claim tort damages under the Civil Code. |
| |
2 | Persons who suffer damage, including distress, are entitled to compensation from the controller or processor. |
| |
2 | Administrative sanctions apply without prejudice to civil liability, so data subjects can claim damages in the civil courts. |
| |
2 | After a Commissioner complaint, individuals may bring proceedings in the Human Rights Review Tribunal for damages. |
| |
2 | Data subjects who suffer injury, loss or harm may sue for damages; the Commission can also order compensation. |
| |
2 | Data subjects may be indemnified for damages from inaccurate or unlawful processing. |
| |
2 | Anyone harmed may seek proportionate compensation for material or moral damage before the competent court. |
| |
2 | Persons suffering loss or damage may sue for injunction, declaration, damages or other relief. |
| |
2 | Data subjects, or the Regulator on their behalf, may sue for patrimonial, non-patrimonial and aggravated damages, regardless of intent or negligence. |
| |
2 | Data subjects can sue for injunctions, rectification or deletion, damages, moral damages and surrender of profits. |
| |
2 | Data subjects can claim compensation in civil courts for damage from unlawful processing; complaints to the Board come after a request to the controller. |
| |
2 | A data subject who suffers damage or distress may apply to court for compensation; complaints also go to the PDPO. |
| |
2 | Individuals can claim compensation for material or non-material damage; representative actions are limited in practice. |
| |
2 | Habeas data court action with summary procedure to access, rectify, include or delete data. |
| |
2 | Violators must compensate damage; controllers and processors liable for losses caused by their processing. |
| |
1 | After a Commissioner complaint, individuals may apply to the Federal Court for damages, including for humiliation. |
| |
1 | Civil courts barred; data principals complain to the Data Protection Board after exhausting grievance redressal. No compensation provision. |
| |
1 | Data subjects may complain to the Data Office; no compensation or civil claim provision. |
| |
1 | No statutory compensation right; data subjects complain to POTRAZ, with appeal to the Administrative Court. |
| |
0 | No statutory right for data subjects to sue for compensation; complaints go to the Commissioner. |
Offenses and penalties
In LPDP
- Article 39Administrative sanctions
Up to 100 UIT (about PEN 535,000, roughly USD 145,000), not exceeding 10% of prior-year gross income.
- Article 40Coercive fines
Maximum fine across 39 laws
| |
2 | Up to 100 UIT (about PEN 535,000, roughly USD 145,000), not exceeding 10% of prior-year gross income. |
| |
3 | Body corporate: greater of AUD 50 million, 3x the benefit, or 30% of adjusted turnover for serious interferences. |
| |
3 | Simple fine up to 2% of Brazil revenue for the prior year, capped at BRL 50 million per infraction; daily fines also possible. |
| |
3 | Up to RMB 50 million or 5% of prior-year revenue; responsible individuals RMB 100,000 to 1 million. |
| |
3 | Serious infringements: 0.7% to 1% of prior-year business volume; public servants 10 to 20 basic salaries. |
| |
3 | Up to EUR 20 million or 4% of total worldwide annual turnover, whichever is higher. |
| |
3 | Up to INR 250 crore (about USD 30m) per instance for security safeguard failures. |
| |
3 | Administrative fines up to 2% of annual revenue; criminal corporate fines up to 10x individual maximum. |
| |
3 | Tiered administrative fines, many per data subject (e.g., ILS 4-8 per person for sensitive databases), plus fixed amounts up to ILS 640,000 per violation; no overall cap stated. |
| |
3 | Greater of N10 million or 2% of prior-year annual gross revenue for entities of major importance; N2 million or 2% for others. |
| |
3 | Penal fines up to CAD 25 million or 4% of worldwide turnover; administrative penalties up to CAD 10 million or 2%. |
| |
3 | Up to 10% of annual Singapore turnover if over SGD 10 million, otherwise SGD 1 million. |
| |
3 | Penalty surcharge up to 3% of total revenue (excluding unrelated revenue); up to 10% for repeat, mass (10m+) or post-order breaches. |
| |
3 | Courts may fine a corporation up to 2% of annual gross turnover; individual offenses up to 245 currency points (UGX 4.9 million). |
| |
3 | Up to GBP 17.5 million or 4% of worldwide annual turnover, whichever is higher; PECR fines now aligned to the same level. |
| |
3 | Up to 5% of prior-year revenue for cross-border violations, 10x revenue for illegal data trading, VND 3 billion for other violations. |
| |
2 | Up to USD 2,663 per violation or USD 7,988 per intentional violation or violation involving minors, with no aggregate cap. |
| |
2 | Up to 2,000 monthly minimum wages (roughly USD 0.7m), plus suspension or closure of operations. |
| |
2 | Administrative fines up to USD 100,000 per standard contravention under Schedule 2. |
| |
2 | Fines up to EGP 5 million (about USD 100,000) per offense, doubled for repeat offenses. |
| |
2 | Criminal fines up to HKD 1,000,000 (about USD 128k) for doxxing causing harm or selling data for marketing. |
| |
2 | Criminal corporate fine up to JPY 100 million for violating PPC orders or unlawful database provision. Amendment adds revenue-linked administrative surcharges. |
| |
2 | Up to RM1,000,000 (about USD 235k) and/or 3 years' imprisonment for breaching the data protection principles. |
| |
2 | Up to 320,000 UMA (about MXN 36 million, roughly USD 2m), doubled for sensitive data, plus an additional fine of up to 320,000 UMA for repeat violations. |
| |
2 | Fines up to SAR 5 million (about USD 1.3m) per violation, doubled for repeat violations. |
| |
2 | Administrative fine up to R10 million (about USD 550,000). |
| |
2 | Criminal fine up to CHF 250,000 per individual; a company can be fined up to CHF 50,000 when identifying the individual is disproportionate. |
| |
2 | Administrative fines up to THB 5 million per violation (about USD 150k). |
| |
2 | Administrative fines up to TRY 17,092,242 per violation in 2026, revalued each year. |
| |
1 | ARS 1,000 to 100,000 per infringement; total for the same conduct capped at ARS 50 million (about USD 35,000-40,000). |
| |
1 | Fines up to CAD 100,000 on indictment (CAD 10,000 summary) for knowing breach-reporting and listed violations; no administrative fines. |
| |
1 | Court-imposed fines of 1 to 10 UTM, or 10 to 50 UTM for economic, financial and commercial data (about USD 3,500 at most). |
| |
1 | General penalty up to 5,000 penalty units (about GHS 60,000) and/or 10 years' imprisonment. |
| |
1 | Up to KES 5 million or 1% of prior-year annual turnover, whichever is lower (about USD 39,000 maximum). |
| |
1 | Criminal fines up to NZD 10,000 (e.g. failing to notify a breach). |
| |
1 | Criminal fines up to PHP 5 million; administrative fines up to 3% of annual gross income, capped at PHP 5 million (about USD 86k) per act. |
| |
1 | Up to 500,000 indexed units (UI) (roughly USD 80,000), plus warning or suspension of the database. |
| |
1 | Fines up to level 11 (reported at about USD 1,000) and/or up to 7 years' imprisonment. |
| |
0 | No fines in force; Cabinet decision defining violations and penalties not issued. |
This index, the topic tags and the notes are ours, scored on the published rubric. Headings marked "our heading" are our descriptions where the source has none. Always read the official text before acting. Not legal advice.
Regulations library
Every US state privacy law, on one map
24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.
- In force
- Coming into force
- Sector laws