Nigeria Data Protection Regulation 2019 Implementation Framework
Nigeria Data Protection Regulation 2019 Implementation Framework
REGULATION 2019:
IMPLEMENTATION FRAMEWORK
JULY, 2020
PREFACE
It gives me immense pleasure to present the Nigeria Data Protection Regulation
(NDPR) 2019: Implementation Framework. The Framework is a necessary step after
the issuance of the NDPR in January 2019 and the Guideline for the Use of Personal
Data by Public Institutions, May 2020. NITDA’s methodical approach to data protection
implementation has been the subject of interest around the world because of some
unique offerings the Regulation has introduced. The NDPR has pioneered a functional
data audit filing process that gives NITDA, as the information technology regulator, a
good view of the state of information systems management in the country. It also
establishes a public-private partnership regulatory compliance model which has
empowered professionals to provide compliance-as-a-service thereby accelerating
NDPR implementation across all sectors.
My joy knows no bound because NITDA, working with the excellent blueprint laid by
Dr. Isa Ali Ibrahim Pantami, the Hon. Minister of Communications and Digital Economy,
has begun making Nigeria a sterling example of data protection implementation in the
Global South. We are not however resting on our oars; we are daily reviewing and
rejigging the implementation architecture through robust stakeholder engagements. I
am glad to say that through our dedicated and methodical approach, NDPR has
become an household name in the digital economy sector. This indicates the level of
awareness and ownership of the Regulation by Nigerians.
This Framework is a product of robust partnership and stakeholder engagement both
within and outside Nigeria. I want to appreciate all our Data Protection Compliance
Organisations (DPCO) who reviewed the document in November, 2019; Aissatou Sylla
of Hogan Lovells LLP (France) who provided robust global perspectives; the law firm
of Udo-Udoma, Belo Osagie for final vetting among many other contributors. I am very
proud of our astute and dynamic NITDA staff who prepared the initial draft and
managed the stakeholder process to completion.
1|Page
TABLE OF CONTENTS
CONTENTS
SECTION 1 BACKGROUND
SECTION 2 SUMMARY
SECTION 3 COMPLIANCE FRAMEWORK
SECTION 5 CONSENT
SECTION 6 DATA PROTECTION AUDIT
2|Page
NIGERIA DATA PROTECTION REGULATION 2019: IMPLEMENTATION
FRAMEWORK1
1. BACKGROUND
1.1 It has been identified that the Personal Data of Nigerians is being
processed by unauthorised persons without any lawful basis. This has
resulted in processing which could lead to the loss of rights and
freedoms of such Nigerian citizens or residents, leading to harm and
distress. To curtail such activity, the National Information Technology
Development Agency (the ‘NITDA’) developed the Nigeria Data
Protection Regulation (the ‘Regulation’ or ‘NDPR’). The Regulation is
made pursuant to section 6(a) and (c) of the NITDA Act 2007 and section
37 of the 1999 Constitution of the Federal Republic of Nigeria 1999 (as
amended).
1.3 The NDPR was issued on 25th January 2019 pursuant to section 6 (a)
and (c) of the National Information Technology Development Agency Act
2007 (the ‘NITDA Act’). It was made in recognition of the fact that many
public and private bodies have migrated their respective businesses and
other information systems online. These information systems have thus
become critical information infrastructure which must be safeguarded,
regulated and protected against personal data breaches. The
Government further takes cognizance of emerging data protection laws
1 Capitalised terms used herein and not otherwise defined herein shall have the meanings assigned to
them in the Regulations, unless the context shall otherwise require.
3|Page
and regulations within the international community geared towards
protecting privacy, identity, lives and property as well as fostering the
integrity of commerce and industry in the data and digital economy and
has realised the imperative importance of developing data protection
rules and regulations to protect the personal data of Nigerian citizens
and residents.
2. SUMMARY
c) stored only for the period within which it is reasonably needed; and
4|Page
i. consent given by the Data Subject;
5|Page
so do. Every Data Controller must state and implement data
retention schedules and communicate same to the Data Subject or
potential clients.
2.2 Application
3. COMPLIANCE FRAMEWORK
iv. Monitoring and Analytics: The compliance framework will ensure the
proactive monitoring and evaluation of Personal Data provided by
concerned entities by utilising analytic tools to identify patterns that
reflect non-compliance.
9|Page
viii. conduct a Data Protection Impact Assessment (‘DPIA’) in
accordance with the provisions of the NDPR: A DPIA is a process to
identify, evaluate and minimise possible data protection risks in an
existing or new business or organisational activity. Where the
organisation intends to embark on a project that would involve the
intense use of personal data, a DPIA should be conducted to identify
possible areas where breaches may occur and devise a means of
addressing such risks. Organisations are expected to conduct a
DPIA on their processes, services and technology periodically to
ensure continuous compliance;
ix. notify the NITDA of Personal Data breaches within 72 (seventy-two)
hours of becoming aware of the breach;
x. appoint a data protection officer in accordance with the provisions
of the NDPR and this Framework;
xi. update agreements with third party processors to ensure
compliance with the NDPR;
xii. design system and processes to make data requests and access
seamless for Data Subjects;
xiii. design systems and processes to enable Data Subjects to easily
correct or update their Personal Data;
xiv. design system and processes to enable Data Subjects to easily
transfer data to another platform or person (natural or artificial) at
minimal costs;
xv. within the first 6 (six) month of incorporation and then on a biennial
basis, train members of senior management and employees that
collect and/or process Personal Data in the course of their duty, on
Nigerian data protection laws and practices;
xvi. clearly communicate to Data Subjects the process for objecting to
the processing of their Personal Data; and
10 | P a g e
xvii. outline the procedure for informing Data Subject and for protecting
their rights, where an automated decision is being made on their
Personal Data.
3.3.2 In this model, the NITDA would register DPCOs who will provide training,
auditing and compliance services to data controllers and administrators.
The criteria for licensing DPCOs is publicly accessible and such licensed
DPCOs are listed on the NITDA website. Data Controllers who process
the Personal Data of more than 2,000 Data Subjects in the 12-month
period preceding 15th March (or such other date the NITDA may
stipulate as the deadline for the filing of annual data protection audit
reports), are expected to submit a report of their data protection audit to
the NITDA on an annual basis.
11 | P a g e
3.4 Appointment of a Data Protection Officer
3.4.1 A Data Controller is required to appoint a dedicated Data Protection
Officer (‘DPO’) within 6 months of commencing business or within 6
months of the issuance of this Framework, where one or more of the
following conditions are present:
a) the entity is a government organ, ministry, department, institution
or agency;
b) the core activities of the organisation involve the processing of the
Personal Data of over 10,000 (ten thousand) Data Subjects per
annum;
c) the organisation processes Sensitive Personal Data in the regular
course of its business; and
d) the organisation processes critical national information
infrastructure (as defined under the Cybercrimes (Prohibition,
Prevention, Etc.) Act 2015 or any amendment thereto) consisting
of Personal Data.
3.4.2 Notwithstanding the above, an organisation may voluntarily appoint a
DPO.
A DPO shall be chosen with due regard to the nature of the organisation’s
Processing activities and the data protection issues that arise within the
organisation.
13 | P a g e
Where a Data Controller wishes to further process Personal Data initially
collected for a defined or limited purpose, the Data Controller shall
consider the following:
4.1.2 The above information shall be provided to the Data Subject before
further processing is done. The further processing may be done if:
14 | P a g e
e) when Personal Data Processing relates to vulnerable or differently-
abled data subjects; and
f) when considering the deployment of innovative processes or
application of new technological or organizational solutions.
5. CONSENT
5.1 Consent of the Data Subject means any freely given, specific, informed
and unambiguous indication of the Data Subject's wishes by which he
or she, through a statement or a clear affirmative action, signifies
agreement to the processing of Personal Data relating to him or her.
Consent may be made through a written statement, sign or an affirmative
action signifying agreement to the processing of personal data.
The following principles shall govern the giving and obtaining of consent:
15 | P a g e
c) further processing;
I want to receive XXX newsletter If the box is left unticked, you will
not receive the XXX newsletter
A child for the purpose of the NDPR shall be any person below thirteen
(13) years. A data controller or processor whose processing activity targets
children shall ensure its privacy policy is made in a child-friendly form with the
aim of making children and their guardians have clear understanding of the data
processing activity before grant of consent.
16 | P a g e
b) Include the name of your organisation and any third parties, why you
want the data, what you will do with it and the right to withdraw consent
at any time;
c) You must ask people to actively opt-in. Don’t use pre-ticked boxes, opt-
out boxes or default settings;
d) Wherever possible, give granular options to consent separately to
different purposes and different types of processing;
e) Keep records to evidence consent- who consented, when, how and what
they were told;
f) Make it easy for people to withdraw consent at any time they choose;
g) Keep consent under review and refresh it if anything changes; and
h) Build regular reviews into your business processes
6.3 The reasons for conducting a data protection audit include to:
18 | P a g e
6.5 Filing Fees
Each Data Controller and Administrator is expected to file its audit report
through a DPCO and pay the following amount as applicable2:
6.6.1 The data protection audit shall contain the following information:
2
The NITDA in its discretion may vary the applicable fees.
19 | P a g e
i) the existence of the right to withdraw consent at any time, without
affecting the lawfulness of Processing based on consent before its
withdrawal;
j) the right to lodge a complaint with a relevant authority;
k) whether the provision of Personal Data is a statutory or contractual
requirement, or a requirement necessary to enter into a contract,
as well as whether the Data Subject is obliged to provide the
Personal Data and the possible consequences of failure to provide
such Personal Data;
l) the existence of automated decision-making, including profiling
and, at least, in those cases, meaningful information about the logic
involved, as well as the significance and the envisaged
consequences of such Processing for the Data Subject;
m) the basis for further Processing (where applicable); and
n) where applicable, the basis for the transfer Personal Data to a
recipient in a foreign country or international organisation by the
Data Controller or Processor, and the existence or absence of an
adequacy decision by the Agency.
20 | P a g e
b) appraising Data Subjects rights protection. The DPCO should be
satisfied that the organisation has clear processes to protect the
rights of the Data Subject;
c) assessing the level of awareness by top management, members of
staff, contractors and customers of the NDPR;
d) identifying current or potential non-compliance; and
e) drawing up a remedial plan to remediate identified non-
compliances.
21 | P a g e
iii. ensure every information it provides to the NITDA about its client
shall be factual and professional;
iv. not mishandle or withhold any Personal Data or asset of its client
unlawfully in the course of its relationship with the client;
v. be held liable, if found to have conspired to provide false and
misleading information in an audit filing or communication.
6.10 AUDITOR’S CODE OF CONDUCT
Every DPCO shall ensure all its members of staff are aware of the ethical
considerations in the performance of an audit under the NDPR. As part
of the licensing process, the NITDA shall verify that a DPCO is registered
with a professional association that regulates the ethical conduct of its
members, in order to ensure a standardised service delivery. The
following are basic ethical expectations required of DPCOs in the
conduct of their business.
22 | P a g e
improved. Any established falsehood in an audit report or
communication to the NITDA by the DPCO, and which falsehood
was known to the DPCO at the time of preparing such report or
communication; is a ground for the immediate withdrawal of the
DPCO’s license
d) Professionalism - DPCOs must perform the service with the highest
level of professionalism and carry out continuous capacity building
for its members of staff, which is a prerequisite for relicensing by
the NITDA. DPCOs must not undertake any work for which they
lack the requisite skills, manpower and capacity.
7.2 The NITDA shall coordinate transfer requests with the office of the
Attorney-General of the Federation (‘AGF’). A ‘white-list’ of jurisdictions
(the ‘White List’) has been compiled and is set out in Annexure C to this
Framework. Where transfer to a jurisdiction outside the White List is
being sought, the Data Controller shall ensure there is a verifiable
23 | P a g e
documentation of consent to one or more of the exceptions stated in
Article 2.12 of the NDPR.
8. RETENTION OF RECORDS
8.1 The Regulation does not explicitly provide for a time period for the
retention of data, because the retention period in certain scenarios may
be subject to existing laws or contractual agreements. Every data
Controller and Administrator shall specify the duration of storage clearly
in its terms of service or other binding document.
8.2 Where the retention period of Personal Data is not specified in the
contract between the parties or by applicable law, the retention period
shall be:
24 | P a g e
The NITDA would consider the above and other circumstances to
determine if the data was stored appropriately and for a reasonable
length of time.
8.3 Personal Data that is no longer in use or which has been retained beyond
the requisite statutorily required storage period, shall be destroyed in
line with global best practices for such operations. Evidence of
destruction of data shall be a valid defence against future allegation of
breach by a Data Subject.
9.1 In line with Article 4.1(8) and other relevant provisions, Data Subjects,
civil societies or professional organisations or any government Agency
may report a breach of this Regulation to the NITDA through any of the
advertised channels. Upon receipt of this report, the Director
General/CEO of the NTDA may direct action to be taken which may
include any of the following:
9.3 A notification of data breach to the NITDA must include the following
information:
25 | P a g e
a) a description of the circumstances of the loss or unauthorised
access or disclosure;
26 | P a g e
10.1.1 Surveillance
Any person who believes a party is not complying with any of the
provisions of the Regulation may file a complaint with the NITDA. Such
complaints must meet the following requirements:
The NITDA will investigate any complaint filed against a Data Controller
or Administrator when a preliminary review of the facts indicates a
possible violation of the provision(s) of the NDPR. The NITDA may by its
officers or through designated DPCO, investigate any complaint filed by
third parties and may also do so based on a special audit check or “spot
check”. Investigation may include a review of the policies, procedures,
or practices of the concerned entity and of the circumstances regarding
any alleged violation. At the time of the initial written communication with
the concerned entity, the NITDA will indicate the basis of the audit.
28 | P a g e
c) Issue public notice to warn the public to desist from patronizing or
doing business with the affected party;
d) Refer the parties in breach to other Self-Regulatory Organization
for appropriate sanctions.
Where the NITDA has determined that a party is in breach of the NDPR,
especially where such breach affects national security, sovereignty and
cohesion, it may seek to prosecute officers of the organization as
provided for in section 17(1) and (3) of the NITDA Act 2007. The NITDA
shall seek a fiat of the Honourable Attorney General of the Federation or
may file a petition with any authority in Nigeria, this may include; the
Economic and Financial Crimes Commission, the Department of State
Security, the Nigerian Police Force, the Independent Corrupt Practices
(and other related offences) Commission or the Office of National
Security Adviser.
29 | P a g e
3. For external complaint, the document must be written
and signed by an Individual either in personal capacity or
a group (of persons or companies) or registered entity
(registered with the CAC).
30 | P a g e
alleged violator coherent and sufficient, the NITDA may
discontinue the enforcement process
31 | P a g e
11. ESTABLISHMENT OF ADMINISTRATIVE REDRESS PANEL
11.1 Pursuant to Article 4.2 of the Regulation, the NITDA shall establish
Administrative Redress Panels (ARP), for the purpose of resolving issues
related to the Regulation. The ARP shall be composed of accomplished
information technology professionals, public administrators and legal
practitioners who shall work with the Agency
11.2 The ARP procedure shall give preference to an online dispute resolution
mechanism. Where it is impracticable to adopt such mechanism, the
ARP panel shall be convened at a physical venue.
11.3 The ARP shall give its opinion within a stipulated period of time.
32 | P a g e
12. THIRD PARTY PROCESSING
12.1 Third Party processors may include Data Administrators and other
statutory or non-statutory data recipients whom the Data Controller
sends data to for the purpose of delivering service to the Subject.
12.2 Data Controllers are required to publish a list of third parties with whom
the Data Subject’s Personal Data may be shared. This publication which
must also be included in the audit report should include:
33 | P a g e
13. DATA PROTECTION IN MDAS
13.2 Every PI shall publish a privacy policy on its website and any other digital
media platform through which it collects Personal Data. A sample
Privacy Policy for PIs is available in Annexure B for guidance.
14.1 In accordance with Article 2.12 of the NDPR, where a Data Controller or
Data Administrator seeks to transfer Personal Data to a foreign country
or an international organisation, the NITDA shall examine if such country
has adequate data protection law or regulation that can guarantee
minimum privacy for the Personal Data of Nigerian citizens and
residents. Where there is need for further legal cooperation from a target
34 | P a g e
country, the NITDA may approach the office of Attorney-General for that
purpose. In such circumstance, such data transfer and storage
processes shall be done under the supervision of the Attorney-General.
14.5 The transfer of data to any country other than the ones listed, by a Data
Controller or Administrator in its request for an adequacy decision, shall
be subject to further processes to ascertain the protection of the
Personal Data of Nigerian citizens and residents.
36 | P a g e
ANNEXURE A
37 | P a g e
Have you set out the management support and
1.8 Article 2.5 direction for data protection compliance in a
framework of policies and procedures?
1.9 Article 2.1 Do you have a Data Protection compliance and review
mechanism?
Have you developed a capacity building plan for
1.10 Article 2.6 compliance with data protection for all members of
staff?
1.12 Article 4.1(5) Do you know the sources of the personal data you
hold?
1.14 Article 4.1(2) Who is responsible for your compliance with data
protection laws and processes
1.15 Article 1.3 Have you assessed whether you are a Data Controller
or Data Processor?
Have you reviewed your Human Resources policy to
1.16 Art 4.1(5) ensure personal data of employees are handled in
compliance with the NDPR?
Have appropriate technical and organisational
measures been implemented to show you have
1.17 Article 2.5(d)
considered and integrated data protection into your
processing activities?
Do you have a policy for conducting Data Protection
1.18 Article 4.5 Impact Assessment (DPIA) on existing or potential
projects?
38 | P a g e
Does your DPIA Policy address issues such as:
a) A description of the envisaged processing
operations b) The purposes
of the processing
c) The legitimate interest pursued by the controller
1.19 Article 4.5 d) An assessment of the necessity and proportionality
of the processing operations in relation to the
purposes
e) An assessment of the risks to the rights and
freedoms of Data Subject f) Risk mitigation
measures being proposed to address the risk
2 DATA PROTECTION OFFICER/DATA PROTECTION COMPLIANCE ORGANISATION
Have you appointed a Data Protection Compliance
Article 4.1(4)
Organisation (DPCO)?
Which kind of service has a DPCO provided for you till
Article 4.1(4) date? Hint- Audit, Data Protection Impact Assessment,
Data Breach Remediation etc.
Article 4.1(2) Does your DPCO also perform the role of your DPO?
Has a Data Protection Officer (DPO) been appointed
and given responsibility for NDPR compliance and the
2.1 Article 4.1(2)
management of organisational procedures in line with
the requirements of NDPR?
Article 4.1(4) Do you utilise the same DPCO for Data Protection
compliance implementation and audit?
2.2 Article 4.1(3) Have you trained your Data Protection Officer in the
last one year?
Does the Data Protection Officer (DPO) have sufficient
Article 4.1(2)
access, support and the budget to perform the role?
If the DPO has other job functions, have you evaluated
Article 4.1(2)
whether there is no conflict of interest?
39 | P a g e
Does the DPO have verifiable professional expertise
and knowledge of data protection to do the following:
a) To inform and advice the business, management,
employees and third parties who carry out processing,
of their obligations under the NDPR b) To
monitor compliance with the NDPR and with the
organisation's own data protection objectives
c) Assignment of responsibilities, awareness-raising
Article 4.1(2)
and training of members of staff involved in processing
operations
d) To provide advice where requested as regards the
data protection impact assessment and monitor its
performance e) To
cooperate with the NITDA as the Supervisory Authority
f) To act as the contact point for the NITDA on issues
relating to data processing
Is there a clearly available mechanism (e.g. webpage,
etc.) for data subjects that explains how to contact
2.3 Article 2.5
your organisation to pursue issues relating to personal
data?
3 DOCUMENTATION TO DEMONSTRATE COMPLIANCE
40 | P a g e
3.5 Article 1.3 Do you have a register of data breaches and security
incidents?
4 PROCESSING ACTIVITIES
Have you carried out a comprehensive review of the
4.1 Article 2.2 various types of processing your organisation
perform?
Have you identified lawful basis for your processing
Article 2.2 activities and documented this?
41 | P a g e
Have you reviewed your forms and other data
collection tools to comply with the NDPR?
4.7 Article 2.2 personal data, for determining and authorising internal
or external access and all disclosures of data?
4.16 Article 2.7 Have you contracted with any third-party data
processors?
If so, are such contracts compliant with the
4.17 Article 2.7
requirements of the NDPR?
Have you agreed a schedule to review current
4.18 Article 2.7
contracts for compliance with NDPR?
42 | P a g e
If so, do you have in place appropriate contracts and
4.20 Article 2.10 methods of ensuring compliance?
43 | P a g e
ANNEXURE B
1.1 This Privacy Policy describes your privacy rights regarding our collection, use,
storage, sharing and protection of your personal information. It applies to the
NITDA website and all database, applications, services, tools and physical
contact with us, regardless of how you access or use them.
1.2 If you have created a username, identification code, password or any other
piece of information as part of our access security measures, you must treat
such information as confidential, and you must not disclose it to any third party.
1.3 We reserve the right to disable any user identification code or password,
whether chosen by you or allocated by us, at any time, if in our opinion you
have failed to comply with any of the provisions of this privacy policy.
1.4 If you know or suspect that anyone other than you know your security details,
you must promptly notify us at [email protected].
2.0 Consent
You accept this privacy policy when you give consent upon access to our
platforms, or use our services, content, features, technologies or functions
offered on our website, digital platforms or visit any of our offices for official or
non-official purposes (collectively the “NITDA Services”). This privacy policy
governs the use of the NITDA Services and intervention projects by our users
and stakeholders, unless otherwise agreed through a written contract. We
44 | P a g e
may amend this privacy policy at any time by posting a revised version on our
website, or placing such notice at conspicuous points at our office facilities.
The revised version will be effective 7 days after publication.
3.1 When you use the NITDA Services, we collect information sent to us by your
computer, mobile phone or other electronic access device. The automatically
collected information includes but is not limited to data about the pages you
access, computer IP address, device ID or unique identifier, device type, geo-
location information, computer and connection information, mobile network
information, statistics on page views, traffic to and from the sites, referral URL,
ad data, standard web log data, still and moving images.
3.2 We may also collect information you provide us including but not limited to-
information on web form, survey responses account update information, email
address, phone number, organization you represent, official position,
correspondence with the NITDA support services, and telecommunication
with the NITDA. We may also collect information about your transactions,
enquiries and your activities on our platform or premises.
3.3 We may also use information provided by third parties like social media sites.
Information about you provided by other sites are not controlled by the NITDA
and we are, therefore, not liable for how such third parties use your
information.
The purpose of our collecting your personal information is to give you efficient,
enjoyable and secure service. We may use your information to:
45 | P a g e
e) manage risk, or to detect, prevent, and/or remediate fraud or other
potentially prohibited or illegal activities;
f) detect, prevent or remediate violation of laws, regulations, standards,
guidelines and frameworks;
g) improve the NITDA Services by implementing aggregate customer or
user preferences;
h) measure the performance of the NITDA Services and improve content,
technology and layout;
i) track information breach and remediate such identified breaches;
j) manage and protect our information technology and physical
infrastructure; or
k) contact you at any time through your provided telephone number, email
address or other contact details.
5.0 Cookies
Cookies are small files placed on your computer’s hard drive that enables the
website to identify your computer as you view different pages. Cookies allow
websites and applications to store your preferences in order to present
contents, options or functions that are specific to you. Like most interactive
websites, our website uses cookies to enable the tracking of your activity for
the duration of a session. Our website uses only encrypted session cookies
which are erased either after a predefined timeout period or once the user
logs out of the platform and closes the browser. Session cookies do not collect
information from the user’s computer. They will typically store information in
the form of a session identification that does not personally identify the user.
7.0 How We Share your information within the NITDA and with Other Users
7.1 During your interaction with our website or premises, we may provide other
Ministries, Departments, Agencies (MDA), other organs of government, private
sector operators performing government functions, with information such as
your name, contact details, or other details you provide us for the purpose of
performing our statutory mandate to you or third parties.
7.2 We work with third parties, especially government agencies to perform the
NITDA Services and implement its mandate. In doing so, a third party may
share information about you with us, such as your email address or mobile
phone number.
7.3 You accept that your pictures and testimonials on all social media platforms
about the NITDA can be used for limited promotional purposes by us. This
does not include your trademark or copyrighted materials.
7.4 From time to time we may send you relevant information such as news items,
enforcement notice, statutorily mandated notices and essential information to
aid the implementation of our mandate. We may also share your personal
information in compliance with national or international laws; crime prevention
and risk management agencies and service providers.
8.0 Security
8.2 The NITDA has also taken measures to comply with global Information
Security Management Systems. We, have, therefore, have put in place digital
and physical security measures to limit or eliminate possibilities of data privacy
breach incidents.
10.1 Certain transaction processing channels may require links to other websites
or organisations other than ours. Please note that the NITDA is not responsible
and has no control over websites outside its domain. We do not monitor or
review the content of other party’s websites which are linked from our website
or media platforms.
10.3 Please be aware that we are not responsible for the privacy practices, or
content of these sites.
48 | P a g e
10.4 We encourage our users to be aware of when they leave our site, and to read
the privacy statements of these sites. You should evaluate the security and
trustworthiness of any other site connected to this site or accessed through
this site yourself, before disclosing any personal information to them.
10.5 The NITDA will not accept any responsibility for any loss or damage in
whatever manner, howsoever caused, resulting from your disclosure to third
parties of personal information.
This privacy policy is made pursuant to the Nigeria Data Protection Regulation
2019 and other relevant Nigerian laws, regulations or international conventions
applicable to Nigeria. Where any provision of this Policy is deemed
inconsistent with a law, regulation or convention, such provision shall be
subject to the overriding law, regulation or convention.
49 | P a g e
ANNEXURE C
50 | P a g e
SN
COUNTRY DATA PROTECTION LAW COMMENT
51 | P a g e
17
Personal Information Protection Commission
South Korea The Personal Information Protection Act (PIPA)
(PIPC)
18 Information and Data Protection Commissioner
Albania Law No. 9887 dated 10.03.2008
(IDP)
19 Andorra Law 15/2003 of 18 Data Protection Agency of Andorra
20 Austria GDPR Austrian Data Protection Authority
21 The Law on Protection of Personal Data ('Official
Bosnia- Personal Data Personal Data Protection
Gazette of BIH', nos. 49/06, 76/11 and 89/11) (DP
Herzegovina Agency in Bosnia and Herzegovina
Law)
22 Implementation of the General Data Protection
Croatia Croatian Personal Data Protection Agency
Regulation
23 Faeroe Islands Data Protection Act Faroese Data Protection Agency
24
DATA PROTECTION ACT 2018
Data Protection (Application of GDPR) Order
2018 (SD2018/0143) (GDPR Order)
Isle of Man Data Protection (Application of LED) Order 2018 Office of the Data Protection Supervisor
(SD2018/0144) (LED Order)
GDPR and LED Implementing Regulations 2018
(SD2018/0145) (Implementing Regulations)
52 | P a g e
handling of personal data. The Ordinance has
been in force since 1996, but, in 2012/2013 was
significantly amended (notably with regard to
direct marketing).
35 Malaysia The Personal Data Protection Act 2010 (PDPA),
was passed by the Malaysian Parliament on June
2, 2010 and came into force on November 15,
2013.
36 Mauritius Mauritius regulates data protection under the
Data Protection Act 2017 (DPA 2017 or Act),
proclaimed through Proclamation No. 3 of 2018,
effective January 15, 2018. The Act repeals and
replaces the Data Protection Act 2004, so as to
align with the European Union General Data
Protection Regulation 2016/679 (GDPR).
37 Qatar The Qatar Financial Centre (QFC) implemented
QFC Regulation No. 6 of 2005 on QFC Data
Protection Regulations (DPL).
38 Singapore Singapore enacted the Personal Data Protection
Act of 2012 (No. 26 of 2012) (the Act) on October
15, 2012. The Act took effect in three phases:
39 South Korea Personal Information Protection Act, 'PIPA') was
enacted and became effective as of 30
September 2011
40 Taiwan The former Computer Processed Personal Data
Protection Law (CPPL) was renamed as the
Personal Data Protection Law (PDPL) and
amended on May 26, 2010. The PDPL became
effective on October 1, 2012, except that the
provisions relating to sensitive personal data and
the notification obligation for personal data
indirectly collected before the effectiveness of
the PDPL remained ineffective. The government
later proposed further amendment to these and
other provisions, which passed legislative
procedure and became effective on March 15,
2016.
41 Turkey The main piece of legislation covering data
protection in Turkey is the Law on the Protection
of Personal Data No. 6698 dated April 7, 2016
(LPPD). The LPPD is primarily based on EU
Directive 95/46/EC.
42 United Arab The Dubai International Financial Centre (DIFC)
Emirates implemented DIFC Law No. 1 of 2007 Data
Protection Law in 2007 which was subsequently
amended by DIFC Law No. 5 of 2012 Data
Protection Law Amendment Law (DPL).
43 India On August 24, 2017, a Constitutional Bench of
nine judges of the Supreme Court of India in
Justice K.S.Puttaswamy (Retd.) v. Union of India
[Writ Petition No. 494/ 2012] upheld that privacy
is a fundamental right, which is entrenched in
53 | P a g e
Article 21 [Right to Life & Liberty] of the
Constitution. This led to the formulation of a
comprehensive Personal Data Protection Bill
2018.[1] However, presently the Information
Technology Act, 2000 (the Act) contains specific
provisions intended to protect electronic
data(including non-electronic records or
information that have been, are currently or are
intended to be processed electronically).
44 Data Protection Act Law No. 18.331 (August 11,
Unidad Reguladora y de Control de
Uruguay 2008); Decree No. 414/009 (August 31, 2009)
DatosPersonales (URCDP)
(the Act).
NB: NITDA may by public notice signed by the Director General/CEO update
this list of countries as the need arises
54 | P a g e