GDPR Notes
GDPR Notes
This Regulation sets rules to protect individuals' personal data and ensure the
free movement of such data within the EU. It safeguards the fundamental rights and
freedoms of individuals,ie right to personal data protection. Movement of personal
data within the EU cannot be restricted or prohibited.
For instance, if a company in France needs to transfer personal data to its branch
in Germany for business purposes, this Regulation ensures that such data movement
within the EU cannot be blocked or limited solely based on data protection
concerns.
10. third party: means legal person/public authority/agency/any other body who is
authorised to process personal data but not included data
subject/controller/processor/persons who are under the direct authority of
controller or processor.
12. personal data breach: means the breach of security which causes
accident/unlawful destruction/loss/alteration/access/unauthorised disclosure of the
personal data which was stored.
16. main establishment: when controller/processor estb in more than one state, then
their main estb will be in the Union.
18. enterprise: a legal person engaged in economic activity and also includes
partnerships or associations.
21. supervisory authority: an independent public authority estb by member state u/A
51.
23. cross-border processing: wwhen processing takes place in more than one member
states.
Clearly state why they are collecting this data (lawfulness, fairness, and
transparency).
Use the data only for processing the customer's order and not for unrelated
purposes (purpose limitation).
Collect only the necessary information required for completing the transaction,
without asking for excessive details (data minimization).
Ensure the accuracy of the data by allowing customers to update their information
and promptly correcting any errors (accuracy).
Delete the customer's personal data after completing the transaction, unless
required for record-keeping purposes (storage limitation).
Safeguard the customer's data against unauthorized access or theft using encryption
and secure servers (integrity and confidentiality).
Maintain records and documentation demonstrating compliance with GDPR principles
(accountability).
The data subject has given consent for the specific purpose of the processing.
Processing is necessary for fulfilling a contract with the data subject or for
taking steps before entering into a contract.
Processing is required to comply with a legal obligation.
Processing is necessary to protect vital interests of the data subject or another
person.
Processing is needed to carry out a task in the public interest or exercising
official authority.
Processing is necessary for legitimate interests pursued by the controller or a
third party, except where overridden by the interests or fundamental rights and
freedoms of the data subject, especially if the data subject is a child.
Public authorities conducting tasks are not covered by point (f).
Member States can have specific rules for processing data related to legal
obligations and public interest tasks.
The legal basis for processing must be Union law or Member State law.
Consent: The patient consents to the processing of their personal data for medical
treatment purposes.
Contract: Processing is necessary for fulfilling the healthcare provider's contract
with the patient for medical services.
Legal obligation: The healthcare provider is required by law to maintain medical
records for a certain period.
Vital interests: Processing the patient's data is necessary to protect their life
in case of a medical emergency.
Public interest: The healthcare provider processes the data for public health
purposes, such as disease monitoring or health research.
Legitimate interests: The healthcare provider may use the data to send reminders
for appointments or to improve their services, as long as it doesn't override the
rights of the patient.
In each of these scenarios, the processing of personal data is lawful under GDPR
because it meets one of the specified conditions.
Suppose there's a healthcare app that wants to collect users' personal data for
research purposes. When users sign up for the app, they are presented with a
lengthy terms of service agreement that includes consent for data processing buried
within it. The consent language is complex and hard to understand amidst all the
legal jargon. This situation doesn't comply with GDPR because consent should be
presented clearly and distinctly from other matters, in a way that's easy for users
to understand.
Furthermore, users should have the ability to revoke their consent at any time. If
a user decides they no longer want their data used for research purposes, they
should be able to easily withdraw their consent through the app settings or by
contacting the app provider.
However, if the app makes access to its essential healthcare services conditional
on agreeing to the research data collection (which is not necessary for providing
basic healthcare services), then this could be considered coercive and would not
meet GDPR standards for freely given consent.
Let's say there's an online gaming platform targeted at children aged 12-15. The
platform collects personal data such as usernames, email addresses, and age during
the sign-up process. According to Article 8 of the GDPR, if the platform wishes to
process the personal data of children under the age of 16 (which is the default age
unless Member States lower it to a minimum of 13), it must obtain consent from a
parent or guardian.
In this example, if a child under the age of 16 signs up for the gaming platform,
the platform must provide clear information to the child and their parent or
guardian about the data processing activities, including why the data is being
collected and how it will be used. The platform must then obtain verifiable consent
from the parent or guardian before processing the child's personal data.
Failure to obtain proper consent from a parent or guardian for the processing of
personal data of children under the age of 16 would violate Article 8 of the GDPR.
Article 12. Transparent information, communication and modalities for the exercise
of the rights of the data subject
Article 12 of the GDPR focuses on transparency and communication with data subjects
regarding the processing of their personal data. Here's an example:
Let's consider an online shopping website. When a user creates an account and
provides personal information such as their name, address, payment details, and
browsing history, the website must comply with Article 12 of the GDPR.
Upon account creation, the website presents a clear and easily accessible privacy
policy or notice that outlines:
The identity and contact details of the website operator (the controller).
The purposes for which the personal data is being processed (e.g., order
fulfillment, marketing communication).
The legal basis for the processing (e.g., performance of a contract, consent).
The retention period for the personal data (e.g., data stored for as long as the
account is active).
The rights of the data subjects, including the right to access, rectify, and delete
their data, as well as the right to object to processing.
Any data transfers to third parties, along with information about safeguards in
place for such transfers.
Furthermore, the website ensures that this information is presented in plain
language and easily understandable to users, fostering transparency and enabling
users to make informed decisions about their personal data.
Article 13. Information to be provided where personal data are collected from the
data subject
1. When personal data is collected directly from the data subject, the controller
must provide the following information at that time:
Their own identity and contact details, and those of their representative if
applicable.
Contact details for the data protection officer, if applicable.
The purposes and legal basis for processing the data.
If processing is based on legitimate interests, the controller's or a third party's
interests pursued.
Any recipients or categories of recipients of the data.
If applicable, whether the data will be transferred to a third country or
international organization, and if so, whether there's an adequacy decision by the
Commission or reference to appropriate safeguards, along with how to obtain a copy
of them.
2. In addition to the previous information, the controller must also provide the
following details when collecting personal data:
How long the personal data will be kept, or if not possible, the criteria used to
determine that period.
The data subject's rights to access, rectify, erase, or restrict processing of
their data, as well as the right to data portability.
If processing is based on consent, the right to withdraw consent at any time.
The right to file a complaint with a supervisory authority.
Whether providing personal data is required by law, contract, or necessary to enter
into a contract, along with the consequences of not providing such data.
If automated decision-making or profiling is used, including information about the
logic involved, and the potential impact on the data subject.
3. If the controller plans to use the personal data for a different purpose than
originally collected, they must inform the data subject beforehand about this new
purpose and provide any additional relevant information mentioned in point 2.
Article 14. Information to be provided where personal data have not been obtained
from the data subject
1. When personal data is not obtained from the data subject, the controller must
provide the following information to the data subject:
Their own identity and contact details, and those of their representative if
applicable.
Contact details for the data protection officer, if applicable.
The purposes and legal basis for processing the data.
The categories of personal data involved.
Any recipients or categories of recipients of the data.
If applicable, whether the data will be transferred to a third country or
international organization, and if so, whether there's an adequacy decision by the
Commission or reference to appropriate safeguards, along with how to obtain a copy
of them.
2. In addition to the previous information, the controller must also provide the
following details to ensure fair and transparent processing for the data subject:
How long the personal data will be kept, or if not possible, the criteria used to
determine that period.
If processing is based on legitimate interests, the controller's or a third party's
interests pursued.
The data subject's rights to access, rectify, erase, or restrict processing of
their data, as well as the right to data portability.
If processing is based on consent, the right to withdraw consent at any time.
The right to file a complaint with
4. If the controller plans to use the personal data for a different purpose than
originally obtained, they must inform the data subject before doing so, providing
information about this new purpose along with any additional relevant details
mentioned in paragraph 2.
3. The controller must give the data subject a copy of their personal data being
processed. If the data subject asks for additional copies, the controller can
charge a reasonable fee based on administrative costs. If the data subject requests
the information electronically, it should be provided in a commonly used electronic
format, unless they ask for something different.
4. The right to get a copy of personal data should not harm the rights and freedoms
of others.