CDPA (Zimbabwe)
Cyber and Data Protection Act, 2021 (Zimbabwe)
37 sections indexed, 19 with our notes. Our index and notes; the law itself is at its source: official text ↗
Part I Preliminary
Object
Interpretation
Application
Part II Data Protection Authority
Designation of Postal and Telecommunications Regulatory Authority as Data Protection Authority
Functions of Data Protection Authority
Part III Quality of data
Quality of data
Part IV General rules on the processing of data
Generality
Purpose
Non-sensitive data
Sensitive information
Genetic data, biometric sensitive data and health data
Part V Duties of data controller and data processor
Duties of data controller
Rights of data subject
Disclosures when collecting data directly from data subject
Disclosures when not collecting data directly from data subject
Authority to process
Security
Security breach notification
Obligation of notification to Authority
Content of notification
Authorisation
Openness of processing
Accountability
Part VI Data subject
Decision taken on basis of Automatic Data Processing
Representation of data subject who is child
Representation of physically, mentally or legally incapacitated data subjects
Part VII Transborder flow
Transfer of personal information outside Zimbabwe
Transfer to country outside Zimbabwe which does not assure adequate level of protection
Part VIII Code of Conduct
Code of Conduct
Part IX Whistleblowing
Whistleblower
Part X General provisions
Regulations
Offences and penalties
Appeals
Part XI Consequential amendments
Amendment of Chapter VIII of Cap. 9:23
Amendment of Cap. 9:07
Amendment of Cap. 11:20
No section matches. Try another word, or clear the topic.
Start from the question. Pick a topic to see the sections of CDPA (Zimbabwe) that deal with it, and how 39 laws compare on it.
Scope and definitions
In CDPA (Zimbabwe)
- Section 1Short title
- Section 3Interpretation
- Section 4Application
Applies to controllers active in Zimbabwe and to controllers not established there that use means located in Zimbabwe.
Reach abroad across 39 laws
| |
1 | Applies to controllers active in Zimbabwe and to controllers not established there that use means located in Zimbabwe. |
| |
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 | Covers non-established controllers that offer goods or services to, or profile, people in Peru; they must appoint a representative. |
| |
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. |
| |
0 | No extraterritorial provision; applies to files and databases, public or private, in Argentina. |
| |
0 | No extraterritorial provision in the current text. |
Principles
In CDPA (Zimbabwe)
We don't score this topic in the comparison. The sections on the left are the place to start.
Lawful basis and consent
In CDPA (Zimbabwe)
- Section 3Interpretation
Consent must be specific, unequivocal, freely given and informed but may be implied for adults; sensitive data needs written consent.
- Section 10Non-sensitive data
Consent or listed grounds including legal obligation, vital interests, public interest and legitimate interests of the controller or third party.
- Section 11Sensitive information
Consent must be specific, unequivocal, freely given and informed but may be implied for adults; sensitive data needs written consent.
- Section 22Authorisation
Lawful basis across 39 laws
| |
1 | Consent or listed grounds including legal obligation, vital interests, public interest and legitimate interests of the controller or third party. |
| |
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; exceptions listed in the Law (public entities, public sources, contracts, health, anonymized data). 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. |
| |
0 | No lawful-basis requirement; notice at collection plus purpose limitation, with opt-out of sale/sharing. |
Sensitive data
In CDPA (Zimbabwe)
- Section 10Non-sensitive data
- Section 11Sensitive information
Sensitive, genetic, biometric and health data require written consent or listed exceptions; some uses need Authority authorization.
- Section 12Genetic data, biometric sensitive data and health data
Sensitive, genetic, biometric and health data require written consent or listed exceptions; some uses need Authority authorization.
- Section 22Authorisation
Sensitive, genetic, biometric and health data require written consent or listed exceptions; some uses need Authority authorization.
Sensitive data across 39 laws
| |
2 | Sensitive, genetic, biometric and health data require written consent or listed exceptions; some uses need Authority authorization. |
| |
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 | Sensitive data, including biometric, genetic and neural data, requires written consent by signature or equivalent. |
| |
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. |
| |
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. |
Children
In CDPA (Zimbabwe)
- Section 3Interpretation
Age 18. Parents or guardians consent and exercise rights; controllers must verify consent and run regular DPIAs for children's data.
- Section 26Representation of data subject who is child
Age 18. Parents or guardians consent and exercise rights; controllers must verify consent and run regular DPIAs for children's data.
Children across 39 laws
| |
3 | Age 18. Parents or guardians consent and exercise rights; controllers must verify consent and run regular DPIAs for children's data. |
| |
3 | Under 12 needs specific parental consent; all minors under 18 must be processed in their best interest. |
| |
3 | Processing data of all minors under 18 is prohibited except public data, or with legal representative authorization respecting the child's best interests. |
| |
3 | Children's data is sensitive. Under 15 needs written guardian consent; for ages 15 to 18 the Center sets the consent mechanism. |
| |
3 | Age 18 (Children's Act). Data about a child under parental control is treated as special personal data. |
| |
3 | Child means under 18; verifiable parental consent required; no tracking, behavioral monitoring or targeted advertising directed at children. |
| |
3 | Processing children's data needs consent of parent or guardian; child means under 18 under Indonesian child law. |
| |
3 | Age 18. Processing requires parent or guardian consent and must serve the child's best interests; profiling children for direct marketing is barred. |
| |
3 | For data subjects under 18, a parent, guardian or person with parental responsibility acts and consents. |
| |
3 | Age 18 (Child's Rights Act). Parental or guardian consent with age verification; regulations pending for electronic services to children 13 and over. |
| |
3 | No fixed age in the PDPL; legal guardians act for persons lacking full legal capacity, including minors. |
| |
3 | Child means under 18. Processing children's information is prohibited unless a s.35 exception applies, such as consent of a competent person. |
| |
3 | Minors (under 20) need guardian consent unless they could act alone; under 10 always needs guardian consent. |
| |
3 | Age 18. Processing a child's data needs prior parental or guardian consent, unless required by law or for research or statistics. |
| |
2 | Under 16: opt-in required to sell/share; under 13: parental authorization. Fines up to USD 7,988 for violations involving minors under 16. |
| |
2 | Under 14 requires parent or guardian consent and special handling rules; such data is sensitive. |
| |
2 | Adolescents 15 and over may consent; younger children need a legal representative; ages 12-15 exercise rights through a representative. |
| |
2 | Parental consent required for information society services offered to children under 16; Member States may lower the age to no less than 13. |
| |
2 | Minors 14 to 18 may consent if information is understandable; under 14 needs parental or guardian consent; reasonable age verification required. |
| |
2 | Information about a minor under 14 requires consent from the person with parental authority, unless clearly for the minor's benefit. |
| |
2 | Under 14: legal representative consent required and must be verified. |
| |
2 | Legal representative acts for children (under 16); child aged 7+ and representative must both consent for private-life data. |
| |
1 | No statutory age; OAIC guidance presumes capacity at 15. Children's Online Privacy Code (under 18) due by 10 Dec 2026. |
| |
1 | No statutory age; the OPC considers children under 13 unable to give meaningful consent. |
| |
1 | No statutory age today; PPC Q&A treats roughly 12-15 as needing a guardian. Amendment sets under 16 for guardian consent once in force. |
| |
1 | No age threshold; collection must be fair and not unreasonably intrusive, particularly from children or young persons. |
| |
1 | PDPC guidance: children 13 to 17 may consent if notices are understandable; under 13 need parent or guardian consent. |
| |
1 | Age of consent for information society services is 13; online services likely accessed by children must consider children's higher protection in design. |
| |
0 | No child-specific rule or age threshold in the Act; general capacity rules of the Civil and Commercial Code apply. |
| |
0 | No child-specific rule or age threshold in the current text. |
| |
0 | No children's consent age; minors are excluded from certain automated-decision exceptions. |
| |
0 | No age threshold or children-specific consent rule. |
| |
0 | No age threshold in the PPL; minors under 18 lack full legal capacity, so parental consent is generally needed. |
| |
0 | No child-specific rule or age threshold; minors act through representatives under the Federal Civil Code (minority ends at 18). |
| |
0 | No child-specific rule or age threshold in the Act; age is listed as sensitive personal information. |
| |
0 | No fixed age; a minor can consent if they have capacity of judgment, assessed case by case. |
| |
0 | No specific rule; under-18s are minors under the Civil Code, so a parent or guardian generally gives consent. |
| |
0 | No age threshold or child-specific rule in the Decree-Law. |
| |
0 | No child-specific rule or age threshold in the Law; minors' data listed among vulnerable groups triggering a DPIA. |
People's rights
In CDPA (Zimbabwe)
- Section 13Duties of data controller
No fixed response deadline in the Act or SI 155.
- Section 14Rights of data subject
Information, access, objection, correction and deletion of false data, and protection from solely automated decisions.
- Section 25Decision taken on basis of Automatic Data Processing
Information, access, objection, correction and deletion of false data, and protection from solely automated decisions.
Rights across 39 laws
| |
2 | Information, access, objection, correction and deletion of false data, and protection from solely automated decisions. |
| |
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 | Information, access, portability, rectification, cancellation, opposition, and objective treatment (no solely automated decisions with significant effects). |
| |
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. |
| |
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. |
Direct marketing
In CDPA (Zimbabwe)
- Section 15Disclosures when collecting data directly from data subject
Data subjects may object free of charge to processing for direct marketing; no opt-in rule.
- Section 16Disclosures when not collecting data directly from data subject
Data subjects may object free of charge to processing for direct marketing; no opt-in rule.
Marketing across 39 laws
| |
1 | Data subjects may object free of charge to processing for direct marketing; no opt-in rule. |
| |
3 | Any marketing use needs prior, express, informed authorization for that purpose; holders may revoke at any time. |
| |
3 | Direct marketing requires the data subject's prior written consent, and data subjects may later require it to stop. |
| |
3 | Consent (incl. 'no objection') required before using or providing personal data for any direct marketing; oral consent confirmed in writing within 14 days. |
| |
3 | Commercial use, including direct marketing, requires express consent; messages must carry a simple opt-out, and objection is absolute. |
| |
3 | Consent is required for any direct marketing; objection to direct marketing is absolute. |
| |
3 | Consent for marketing must be obtained directly; one first contact allowed to seek it, no further contact if refused; opt-outs handled within 10 days. |
| |
3 | Consent required before sending advertising or using personal data for direct marketing; easy opt-out required; no existing-customer exception confirmed. |
| |
2 | APP 7 requires opt-out; Spam Act 2003 requires opt-in consent for commercial electronic messages. |
| |
2 | Automated-decision marketing must offer a non-personalized option or easy refusal; marketing otherwise needs consent. |
| |
2 | Electronic direct marketing requires prior consent, a clear opt-out and a Center licence; consent records kept three years. |
| |
2 | Absolute right to object to direct marketing; prior consent required for electronic marketing under the ePrivacy Directive, with a customer soft opt-in. |
| |
2 | Prior written or electronic opt-in for commercial electronic messages, with a narrow existing-customer exception; the PPL also gives an absolute right to opt out of direct mail. |
| |
2 | Marketing email requires prior opt-in consent under the Act on Regulation of Transmission of Specified Electronic Mail. |
| |
2 | Commercial electronic messages require consent under the Unsolicited Electronic Messages Act 2007. |
| |
2 | Electronic direct marketing requires prior opt-in consent, which may be requested only once; existing customers may receive similar offers with an opt-out. |
| |
2 | Electronic advertising requires the recipient's prior explicit opt-in consent. |
| |
2 | Opt-in for automated mass advertising (email, SMS), except to existing customers for similar products with an opt-out offered. |
| |
2 | Commercial electronic messages need prior opt-in consent recorded in the national IYS system; opt-outs must be honored within 3 business days. |
| |
2 | Prior consent needed for electronic marketing, with soft opt-in for existing customers (extended to charities by DUAA); absolute right to object. |
| |
2 | Consent required for behavioral and targeted advertising, with an opt-out mechanism, plus anti-spam rules. |
| |
1 | Marketing may use data from public sources or provided by the holder; holders may demand removal or blocking at any time (opt-out). |
| |
1 | No specific marketing rule; requires a legal basis, and data subjects may object or revoke consent. |
| |
1 | Right to opt out of selling or sharing data for cross-context behavioral advertising; email marketing governed by federal CAN-SPAM. |
| |
1 | Opt-out consent can suffice for non-sensitive secondary marketing uses; commercial electronic messages need opt-in under CASL. |
| |
1 | Holders may object to use of their data for advertising, market research or opinion surveys (opt-out). |
| |
1 | Inform subjects before first disclosure for marketing and honor the right to object at any time, offered by the first communication. |
| |
1 | Data subjects may object at any time to direct marketing, including related profiling. |
| |
1 | Data subjects may require a controller, by written notice, to stop or not begin processing for direct marketing. |
| |
1 | Marketing is a secondary purpose disclosed in the privacy notice; data subjects can object or opt out. |
| |
1 | Data subjects have a right to object to direct marketing; processing must stop on objection. |
| |
1 | Prospection must identify the enterprise and inform individuals of their right to withdraw consent; electronic messages need CASL opt-in. |
| |
1 | Check the Do Not Call Register before marketing calls or texts unless clear consent; marketing use of data also needs consent. |
| |
1 | Data subjects may object to direct marketing at any time; no PDPA-specific opt-in for electronic marketing. |
| |
1 | Data subjects may object to processing for direct marketing, including related profiling. |
| |
1 | Data subjects may require a controller to stop direct marketing processing; the controller must respond within 14 days. |
| |
1 | Marketing profiles only from public sources, data provided by the holder or with consent; holder may request removal or blocking at any time. |
| |
0 | No specific direct marketing rule; marketing requires consent like other processing; targeted ads to children banned. |
| |
0 | Not addressed specifically; marketing needs a lawful basis and consent can be withdrawn. |
Privacy officer
In CDPA (Zimbabwe)
- Section 20Obligation of notification to Authority
Every data controller must appoint a DPO and notify POTRAZ on Form DP2.
DPO required across 39 laws
| |
3 | Every data controller must appoint a DPO and notify POTRAZ on Form DP2. |
| |
3 | Every organization must designate an individual accountable for compliance. |
| |
3 | Every controller and processor must designate a person or area to assume the data protection function and handle requests. |
| |
3 | Every legal-entity controller and processor must appoint a qualified employee as DPO and register them with the Center. |
| |
3 | Every controller must designate a person or data protection department to handle ARCO requests and promote data protection internally. |
| |
3 | Every agency must appoint one or more privacy officers. |
| |
3 | Every personal information controller and processor must designate a DPO or accountable individual, and register one DPO. |
| |
3 | The person with highest authority in every enterprise is by default the person in charge of personal information protection; may delegate in writing. |
| |
3 | Every organization must designate one or more individuals responsible for PDPA compliance and publish business contact information. |
| |
3 | Every public and private body has an Information Officer (the head by default), who must be registered with the Regulator before taking up duties. |
| |
3 | Every controller must designate a chief privacy officer; small businesses default to the owner or representative. |
| |
3 | The head of every institution covered by the Act must designate a data protection officer. |
| |
2 | Controllers must appoint an encarregado; ANPD may exempt small processing agents. |
| |
2 | Statute lets controllers appoint a certified data protection supervisor; DPC guidance requires medium and large controllers to appoint one. |
| |
2 | Data controllers and processors of major importance must designate a DPO; low thresholds (over 200 data subjects in six months) capture many firms. |
| |
2 | Must appoint qualified data protection personnel or department, or hire a service provider. |
| |
1 | Not required for organizations; Australian Government agencies must appoint a privacy officer under the Agencies Code. |
| |
1 | Handlers processing personal information above the volume set by the CAC must appoint a personal information protection officer. |
| |
1 | DPO required for DIFC Bodies and for controllers or processors performing high-risk processing on a systematic or regular basis. |
| |
1 | DPO required for public-sector processing, large-scale systematic monitoring and large-scale processing of special categories. |
| |
1 | DPO required for public bodies, large-scale systematic monitoring, or large-scale special-category or criminal data processing. |
| |
1 | Only Significant Data Fiduciaries notified by the government must appoint a DPO; others publish contact of a DPO or responsible person. |
| |
1 | DPO required for public-service processing, large-scale systematic monitoring, or large-scale specific/criminal data; any one trigger suffices. |
| |
1 | Required for public bodies, data brokers and direct mailers above 10,000 people, and entities whose core activity is systematic monitoring or large-scale special-sensitivity data. |
| |
1 | Controllers and processors may appoint a DPO for public or private bodies, systematic monitoring, or sensitive data processing. |
| |
1 | Controllers and processors must appoint a DPO when processing data of over 20,000 subjects, sensitive data of over 10,000, or systematic monitoring. |
| |
1 | Data protection officer required for public entities, large-scale or sensitive processing, and core sensitive-data activities; phased in by company size through Nov 2028. |
| |
1 | DPO required for public entities processing at large scale, and where core activities involve systematic monitoring or sensitive data. |
| |
1 | Optional for private controllers; federal bodies must appoint a data protection advisor. |
| |
1 | DPO required for public authorities, large-scale regular monitoring, or core activities involving sensitive data. |
| |
1 | DPO required for high-risk processing, systematic assessment of sensitive data including profiling, or large-volume sensitive data. |
| |
1 | DPO required for public authorities, large-scale systematic monitoring, or large-scale special-category or criminal data processing. |
| |
1 | DPO required for public bodies, majority state-owned entities, private entities whose core business is sensitive data, and those processing data of over 35,000 people. |
| |
0 | No DPO requirement; executive accountable for risk-assessment attestations and cybersecurity audit certification. |
| |
0 | No DPO requirement. |
| |
0 | No DPO requirement; controllers must take necessary security control measures, including organizational measures. |
| |
0 | No DPO requirement; registered controllers must appoint a contact person for the Authority and data subjects. |
| |
– | Not addressed |
| |
– | Not addressed |
Records and assessments
In CDPA (Zimbabwe)
- Section 21Content of notification
Controllers must notify the Authority of all processing activities, including purposes and retention, and keep a breach register.
- Section 22Authorisation
Regular DPIAs required for children's data; specific-risk processing needs prior Authority authorization. No general DPIA duty.
Records across 39 laws
| |
3 | Controllers must notify the Authority of all processing activities, including purposes and retention, and keep a breach register. |
| |
3 | Controllers must keep a personal data processing inventory and file its contents in the public VERBIS registry, plus keep a retention and destruction policy. |
| |
2 | Controllers and processors must keep records of processing operations, especially those based on legitimate interest. |
| |
2 | Keep processing records and assessment reports for at least three years; regular compliance audits required. |
| |
2 | Controllers must keep a written record of processing activities, which may be electronic. |
| |
2 | Records of processing required; controllers with fewer than 100 workers exempt if processing is occasional, low risk and excludes special categories. |
| |
2 | Controllers must keep a dedicated record of processing, and processors a record of processing activities. |
| |
2 | Controllers and processors keep records of processing; limited exemption for organizations under 250 employees doing occasional, low-risk processing. |
| |
2 | No standalone record of processing duty; registration files the data held, purposes, recipients and transfer countries. DPC guidance recommends a RoPA. |
| |
2 | Controllers must record all processing activities. |
| |
2 | Every database needs a database definition document (purposes, data types, transfers, processors) and written security procedures. |
| |
2 | No standalone record of processing duty; registration requires describing data, purposes, recipients and transfers, and breaches must be recorded. |
| |
2 | GAID defines a Record of Processing Activities; DPO reports feed into it and it is checked in the annual compliance audit. |
| |
2 | A dated security document must include an inventory of personal data and processing systems, kept for Authority review. |
| |
2 | Maintain records describing processing systems, purposes, data categories, flows, retention, security measures and accountable persons. |
| |
2 | Keep a written record of processing during processing and five years after it ends; provide to SDAIA on request. |
| |
2 | Responsible parties must maintain documentation of all processing operations, as required by PAIA manuals. |
| |
2 | Controllers and processors must keep records; firms under 250 employees are exempt unless they process sensitive data at scale or do high-risk profiling. |
| |
2 | Controllers must keep written or electronic records of processing; small organizations exempt per PDPC notification. |
| |
2 | Keep a special record of processing including controller and DPO details; provide to the Data Office on request. |
| |
2 | Records of processing required; limited exemption for organizations under 250 employees doing occasional, low-risk processing. |
| |
2 | Controllers must keep evidence of consent and document processing in the filed impact assessment dossier. |
| |
1 | No separate records duty; the database registration filing describes each database. |
| |
1 | Only a privacy policy and some use/disclosure notes (e.g. enforcement-related disclosures); no general ROPA. |
| |
1 | No general record of processing; businesses keep records of consumer requests for at least 24 months. |
| |
1 | No processing inventory; organizations must keep records of every breach of security safeguards. |
| |
1 | No general records duty; RNBD filings and documented processing, retention and deletion procedures act as a limited inventory. |
| |
1 | Log book required only for refused access or correction requests, kept 4 years. |
| |
1 | No general record of processing; fiduciaries must keep processing logs and related data for at least one year. |
| |
1 | Records required only for providing personal data to, or receiving it from, third parties. |
| |
1 | Keep a record of applications, notices, requests and other information relating to personal data, in the Commissioner's prescribed form. |
| |
1 | Regulation requires an inventory of personal data and processing systems as a security measure; not filed with the regulator. |
| |
1 | No processing inventory; enterprises must keep a register of confidentiality incidents. |
| |
1 | Public institution file registration and privacy policy disclosures; no general ROPA for private controllers. |
| |
1 | No general record of processing duty; the PDPO register records each entity's processing purpose, and registered entities file annual compliance reports. |
| |
1 | Accountability measures must be documented and available to the URCDP; database registration describes processing. |
| |
0 | No records-of-processing requirement in the current text. |
| |
0 | No records-of-processing duty. |
| |
0 | No record of processing requirement; organizations must document policies and practices. |
Security
In CDPA (Zimbabwe)
We don't score this topic in the comparison. The sections on the left are the place to start.
Breach notification
In CDPA (Zimbabwe)
- Section 19Security breach notification
Notify POTRAZ within 24 hours of becoming aware, on Form DP3; investigation report within 21 days.
Tell the regulator across 39 laws
| |
3 | Notify POTRAZ within 24 hours of becoming aware, on Form DP3; investigation report within 21 days. |
| |
3 | Immediately take remedial measures and notify the regulator of a leak, alteration or loss. |
| |
3 | Intimate the Board without delay, then a detailed report within 72 hours of becoming aware. |
| |
3 | Report a severe security incident to the PPA immediately on discovery, through its online form. |
| |
3 | Notify the PDPO immediately on believing data was accessed or acquired by an unauthorized person. |
| |
2 | Notify ANPD within 3 business days of learning an incident affected personal data and may cause relevant risk or harm. |
| |
2 | Notify the Attorney General within 15 days of notifying consumers when a breach affects more than 500 California residents. |
| |
2 | Report security incidents to SIC through the RNBD within 15 business days of detection. |
| |
2 | Notify the Superintendency within 5 days of becoming aware, unless the breach is unlikely to create risk; processors tell controllers within 2 days. |
| |
2 | Notify the Center within 72 hours of becoming aware; national-security breaches immediately. |
| |
2 | Notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless risk is unlikely. |
| |
2 | Written notice to the agency within 72 hours (3x24 hours) after a failure is established. |
| |
2 | Report reportable breaches (sensitive data, financial harm, improper purpose, over 1,000 persons) promptly (3-5 days guidance), final report within 30 days, 60 if malicious. |
| |
2 | Notify the Data Commissioner within 72 hours of becoming aware where there is a real risk of harm; processors tell controllers within 48 hours. |
| |
2 | Notify the Commissioner as soon as practicable and within 72 hours of the breach. |
| |
2 | Notify the Commission within 72 hours of becoming aware of a breach likely to risk individuals' rights. |
| |
2 | Notify the Authority within 48 hours of qualifying incidents (large-scale, sensitive data or many affected); digital incidents also to the National Digital Security Center. |
| |
2 | Notify the NPC within 72 hours of knowledge of a breach involving sensitive or fraud-enabling data with real risk of serious harm. |
| |
2 | Notify SDAIA within 72 hours of becoming aware of a breach that may harm data subjects. |
| |
2 | After assessing a breach as notifiable, notify the PDPC as soon as practicable and no later than 3 calendar days. |
| |
2 | Report to PIPC within 72 hours where 1,000+ persons, sensitive or unique identifiers, or external hacking are involved. |
| |
2 | Notify the PDPC Office within 72 hours of becoming aware, where feasible, unless no risk to rights. |
| |
2 | Notify the Board as soon as possible, interpreted by the Board as within 72 hours of discovery, with no risk threshold. |
| |
2 | Notify the ICO without undue delay and, where feasible, within 72 hours of becoming aware, unless risk is unlikely. |
| |
2 | Notify the URCDP within 72 hours of becoming aware of a breach, then file a detailed report once resolved. |
| |
2 | Notify the specialized agency (A05) within 72 hours of detecting a breach likely to cause serious harm. |
| |
1 | Assess suspected breaches within 30 days; notify OAIC as soon as practicable for eligible data breaches. |
| |
1 | Report to the Commissioner as soon as feasible if a breach creates a real risk of significant harm. |
| |
1 | Notify the Commissioner as soon as practicable in the circumstances; no fixed hours. |
| |
1 | Notify the Commission as soon as reasonably practicable after discovery; no fixed hour limit. |
| |
1 | Notify the Commissioner as soon as practicable after becoming aware of a notifiable breach (OPC guide: within 72 hours). |
| |
1 | Promptly notify the Commission d'accès à l'information of incidents presenting a risk of serious injury. |
| |
1 | Notify the Regulator as soon as reasonably possible after discovering a security compromise; no fixed hour limit. Filed through the eServices portal since April 2025. |
| |
1 | Notify the FDPIC as soon as possible of a breach likely to pose a high risk; no fixed hour deadline. |
| |
1 | Notify the Data Office on becoming aware of a breach prejudicing privacy, within a period the Executive Regulations will set. |
| |
0 | No statutory breach notification duty. |
| |
0 | No breach notification duty in the current text. |
| |
0 | No mandatory notification; voluntary notice to PCPD encouraged. |
| |
0 | No duty to notify the regulator. |
Transfers abroad
In CDPA (Zimbabwe)
- Section 28Transfer of personal information outside Zimbabwe
Transfers abroad need adequate protection in the recipient country or a listed derogation such as unambiguous consent.
- Section 29Transfer to country outside Zimbabwe which does not assure adequate level of protection
Transfers abroad need adequate protection in the recipient country or a listed derogation such as unambiguous consent.
Transfers abroad across 39 laws
| |
2 | Transfers abroad need adequate protection in the recipient country or a listed derogation such as unambiguous consent. |
| |
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 | Transfers allowed to adequate countries or with safeguards such as model clauses; every cross-border flow must be notified to the Authority. |
| |
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. |
| |
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 |
Retention
In CDPA (Zimbabwe)
- Section 13Duties of data controller
Data may be kept no longer than necessary for the purpose collected; no specific periods.
Retention across 39 laws
| |
1 | Data may be kept no longer than necessary for the purpose collected; no specific periods. |
| |
3 | Erase when purpose ends or consent is withdrawn; large e-commerce, gaming and social platforms must erase after three years of inactivity with 48 hours' notice. |
| |
3 | Without a statutory period, storage must end within six months after the purpose is accomplished. |
| |
2 | Destroy or de-identify personal information once no longer needed for any permitted purpose. |
| |
2 | Data must be deleted when processing ends, with listed exceptions such as legal obligations or research. |
| |
2 | Disclose retention period per category and keep data no longer than reasonably necessary for the disclosed purpose. |
| |
2 | Retain for the shortest period necessary; delete when purpose is achieved, consent withdrawn or retention period expires. |
| |
2 | Keep data no longer than necessary; when the basis ends, delete, anonymize, pseudonymize, encrypt or put it beyond use. |
| |
2 | Data may not be kept longer than the purpose requires and must be erased when the purpose ends. |
| |
2 | Data may not be kept longer than necessary and must then be destroyed, deleted or de-identified. |
| |
2 | Do not keep data longer than necessary and take practicable steps to erase it. |
| |
2 | Delete or destroy data at the end of the retention period or on request; notices must state the retention period. |
| |
2 | Keep data only as long as reasonably necessary, maintain a retention schedule with periodic review, then erase or anonymize. |
| |
2 | Do not keep data longer than necessary and take reasonable steps to destroy or permanently delete it. |
| |
2 | Data must be blocked, then deleted, once purposes end; records of contractual defaults must be deleted after 72 months. |
| |
2 | Indefinite retention generally prohibited; processors keep data at most 2 years after the engagement ends; access logs kept at least 2 years. |
| |
2 | Destroy or anonymize information once its purposes are achieved, subject to legal retention periods. |
| |
2 | Destroy data when no longer needed for its purpose or processed unlawfully, subject to legal retention exceptions. |
| |
2 | Records may not be kept longer than necessary for the purpose and must be destroyed, deleted or de-identified afterward. |
| |
2 | Destroy personal information without delay once the retention period ends or the purpose is achieved. |
| |
2 | Controllers must examine and erase or anonymize data after the retention period or when no longer needed. |
| |
2 | Erase, destroy or anonymize data once processing grounds end; registered controllers need a retention policy and periodic destruction at least every six months. |
| |
2 | Data may not be kept longer than necessary; at expiry it must be destroyed, deleted or de-identified. |
| |
2 | Delete data once no longer necessary; negative credit records limited to 5 years, renewable once. |
| |
2 | Delete when purpose is complete, retention period ends, ordered by authorities, or on request. |
| |
1 | Data must be destroyed once no longer necessary or relevant to the purpose collected. |
| |
1 | Keep information only as long as needed for its purposes; destroy, erase or anonymize when no longer required. |
| |
1 | Data must be deleted or cancelled when storage lacks a legal basis or the data has expired. |
| |
1 | Process data only as long as reasonable and necessary for the purpose, then delete unless law or contract requires retention. |
| |
1 | Data kept no longer than necessary; controllers must set deletion or periodic review deadlines; the regulator may set periods. |
| |
1 | Storage limitation: keep identifiable data no longer than necessary; erase when no longer needed. |
| |
1 | Delete data once its lawful purpose is exhausted and review holdings periodically, at least annually, for excess data; no statutory periods. |
| |
1 | Businesses must endeavor to delete personal data without delay once it is no longer needed. |
| |
1 | Do not keep information longer than required for lawful purposes. |
| |
1 | Retain only as long as necessary for the declared purpose, legal claims or legitimate business purposes, then dispose securely. |
| |
1 | Cease retention or anonymize once the purpose is no longer served and no legal or business need remains. |
| |
1 | Destroy or anonymize personal data once it is no longer needed for its purpose; no statutory periods. |
| |
1 | Personal data must not be kept after the purpose is exhausted, unless anonymized. |
| |
1 | Storage limitation: keep identifiable data no longer than necessary. |
Regulator
In CDPA (Zimbabwe)
We don't score this topic in the comparison. The sections on the left are the place to start.
Complaints and enforcement
In CDPA (Zimbabwe)
- Section 34Appeals
No statutory compensation right; data subjects complain to POTRAZ, with appeal to the Administrative Court.
Private action across 39 laws
| |
1 | No statutory compensation right; data subjects complain to POTRAZ, with appeal to the Administrative Court. |
| |
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 | Anyone harmed may claim compensation; denied rights can be pursued before the Authority or by habeas data action. |
| |
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. |
| |
0 | No statutory right for data subjects to sue for compensation; complaints go to the Commissioner. |
Offenses and penalties
In CDPA (Zimbabwe)
- Section 33Offences and penalties
Fines up to level 11 (reported at about USD 1,000) and/or up to 7 years' imprisonment.
Maximum fine across 39 laws
| |
1 | Fines up to level 11 (reported at about USD 1,000) and/or up to 7 years' imprisonment. |
| |
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 | Up to 100 UIT (about PEN 535,000, roughly USD 145,000), not exceeding 10% of prior-year gross income. |
| |
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. |
| |
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