Guide
Notice and consent under Sections 5 and 6
What a notice has to contain under Rule 3, what makes consent valid under Section 6, and the records that let you show both.
Consent is one of the two grounds on which personal data may be processed under Section 4. Where an organisation relies on it, two things have to be right: the notice that comes with the request, and the consent itself. The organisation also has to be able to show both afterwards.
When a notice is needed
Every request for consent is to be accompanied or preceded by a notice (Section 5(1)). Where consent was given before the Act commenced, a notice is to be given as soon as it is reasonably practicable, and processing may continue until the Data Principal withdraws her consent (Section 5(2)).
What a notice has to contain
Rule 3 sets out three requirements. The notice is to:
- be presented and be understandable independently of any other information the Data Fiduciary has made available;
- give, in clear and plain language, a fair account of the details necessary for specific and informed consent, including at the minimum an itemised description of the personal data and the specified purpose, with a specific description of the goods or services to be provided or uses to be enabled; and
- give the particular communication link for the website or app, and a description of any other means, by which the Data Principal may withdraw consent, exercise her rights under the Act and make a complaint to the Board.
The Data Principal is to have the option to access the notice in English or in any language specified in the Eighth Schedule to the Constitution (Section 5(3)).
What makes consent valid
The consent given by the Data Principal shall be free, specific, informed, unconditional and unambiguous with a clear affirmative action, and shall signify an agreement to the processing of her personal data for the specified purpose and be limited to such personal data as is necessary for such specified purpose.
Section 6(1)
The Act illustrates the last part with a telemedicine app that asks for consent to provide its service and to read the user's contact list. Because the contact list is not necessary for telemedicine, the consent is limited to the first purpose.
Any part of a consent that infringes the Act, the Rules or another law is invalid to that extent (Section 6(2)). The request is to be in clear and plain language, with the same choice of languages, and is to give the contact details of the Data Protection Officer where there is one, or of another person authorised to respond (Section 6(3)).
Withdrawal
A Data Principal may withdraw consent at any time, and doing so is to be as easy as giving it (Section 6(4)). Withdrawal does not affect the legality of processing carried out before it (Section 6(5)).
After withdrawal, the Data Fiduciary is to cease processing within a reasonable time and to cause its Data Processors to cease, unless processing without consent is required or authorised by law (Section 6(6)). Personal data is then to be erased unless retention is necessary for compliance with a law (Section 8(7)).
Consent Managers
A Data Principal may give, manage, review or withdraw consent through a Consent Manager, which acts on her behalf and is registered with the Board (Sections 6(7) to 6(9)). Rule 4 and the First Schedule set the conditions for registration and the obligations of a Consent Manager.
Being able to show it
Where consent is the basis of processing and a question arises in a proceeding, the Data Fiduciary is obliged to prove that a notice was given and that consent was given in accordance with the Act and the Rules (Section 6(10)). A consent that cannot be shown is, for practical purposes, a consent you do not have.
Records worth keeping
The Act does not prescribe a record format. These are our recommendations for being able to meet Section 6(10):
- Every version of each notice, with the dates it was in use.
- For each consent: the person, the purpose, the time, and the notice version shown.
- For each withdrawal: the time it was received and the time each system and processor stopped.
- A way to show that the record has not been altered since it was made.
When consent is not the ground
Consent is not always the right ground. Section 7 lists certain legitimate uses for which no consent is needed, such as a purpose for which the Data Principal has voluntarily provided her data, compliance with a legal obligation to disclose information, and purposes of employment. The list is closed. See the DPDP Act page for the full list.
Related reading
Privacy notice review checklist
Check a notice against each element of Section 5 and Rule 3, then against the practices that keep it accurate.
Data Fiduciary or Data Processor: who carries which duty
The Act places its obligations on the Data Fiduciary, including for work done by its processors. A practical look at what that means on each side of the contract.
DPDP readiness: a starter checklist
Thirty questions, grouped by theme, to establish where an organisation stands before detailed assessment begins.