learn-pdpa-dnc-with-phoebe / Practitioner session 2 of 8
Learn PDPA + DNC with Phoebe · Practitioner track · Session 2 of 8

Capturing valid consent

Consent is the lawful basis you will lean on most - and the one most easily done wrong. This session makes it practical: what "clear and unambiguous" actually requires, why a pre-ticked box is not consent, the three kinds of deemed consent you can rely on without asking again, and how withdrawal really works. Marina Retail rebuilds its sign-up form so the consent it collects would survive a PDPC query.

🟢 easy Marketers · DPOs · sales ops Running case: Marina Retail 45 min
0-3 · Welcome 3-22 · Valid consent 22-40 · Deemed + withdrawal 40-45 · Q&A
Part 0

Consent you can actually prove

In b1 the checker kept assuming a clean answer to one question: do you have consent? This session earns that answer. Real consent is not "we think they agreed" - it is a positive action the person took, on a clear notice, that you recorded. Get those three right and you have a lawful basis that overrides the register and survives a query. Get them wrong and you have a marketing list built on sand.

Read this first Educational, not legal advice. This session is a practical teaching model of the PDPA consent rules - always verify against the current PDPC Advisory Guidelines on Key Concepts and get proper advice before relying on a consent design for a real campaign.
Live - presented in session Self-study - full depth after class ★ Try it now Sources covered at the end
★ What you build today A working definition of valid consent you can hold a form up against, the three deemed-consent routes that let you use data without asking again, a withdrawal process that ceases use cleanly, and a rewritten Marina Retail consent line that would pass review.
Part 1 · covers what valid consent requires

What valid consent looks like 8 min live

Consent is not a checkbox - it is a moment where a person, having been told plainly what they are agreeing to, does something to say yes. The good flow and the bad flow below look similar on a screen and are worlds apart in law.

Valid consent Clear notice what, why, who Positive action person opts in Record it what + when + how Not consent Pre-ticked box inaction is not a yes Bundled consent forced beyond what is needed Misleading means tricked into agreeing If the person did not take a positive action on a clear notice, you do not have consent - you have a checkbox.
🔍 Click to zoom - the good consent flow, and the three ways it fails
LivePositive action, on a clear notice3 min▶

Under s.14 of the PDPA, consent must be clear and unambiguous. In practice that means the person took a positive action to agree - ticked an empty box, typed their number into a field labelled for marketing, replied "YES" to a keyword. What is not consent:

  • A pre-ticked box. If the default is "yes" and the person did nothing, they did not consent. Inaction or failure to opt out is not a clear-and-unambiguous yes.
  • Silence or "continuing to use the site". Passive states are not positive actions. The person has to do the agreeing.
  • A notice buried where no reasonable person would read it. Clear means clear - the purpose has to be visible at the moment of the action.
LiveTwo limits: reasonableness and honesty3 min▶

Even a positive action is not enough if you asked for too much or asked dishonestly. Section 14 draws two hard lines:

  • You cannot require consent beyond what is reasonable to provide the product or service. Making marketing consent a condition of buying a kettle is over-reach - the sale does not need it, so you cannot force it as a bundle.
  • You cannot obtain consent by false or misleading means. If the person agreed because you misrepresented what they were agreeing to, that consent is not valid - it is deemed not given.
  • Separate the asks. Consent to fulfil the order and consent to market are different purposes. Bundle them and the marketing consent is tainted.
Part 2 · covers deemed consent + withdrawal

Deemed consent + withdrawal 8 min live

Sometimes you do not need to ask, because the person's own conduct or the transaction supplies the consent - that is deemed consent. And whenever consent exists, the person can take it back. Both paths are below.

Deemed consent By conduct volunteers data for an obvious purpose Contractual necessity needed to conclude or perform a transaction By notification no adverse effect + reasonable opt-out window Withdrawal - any time Reasonable notice person opts out Inform consequences do not prohibit it Cease use ~10 business days Deemed consent covers the purpose it was given for - it is not a licence to market for anything.
🔍 Click to zoom - three deemed-consent routes and the withdrawal path
LiveThe three deemed-consent routes3 min▶

Deemed consent means the law treats consent as given without an explicit tick, in three defined situations:

  • By conduct (s.15(1)). The person voluntarily provides their data for a purpose that is obvious in context - handing over a phone number to book a delivery slot deems consent to use it for that delivery. It does not deem consent to market to them.
  • By contractual necessity (s.15(3)). Where sharing the data is reasonably necessary to conclude or perform a transaction the person is party to, consent is deemed - and it can extend downstream to a party you need to involve to deliver.
  • By notification (s.15A). You may deem consent for a new purpose if you assess it will have no adverse effect on the person, tell them about it, and give a reasonable period to opt out before you proceed. This one requires a documented assessment - it is not a free pass.
LiveWithdrawal, and the records to keep3 min▶

Consent is never permanent. Under s.16 an individual may withdraw at any time, on reasonable notice:

  • You must not prohibit withdrawal - no "you agreed forever" clauses. You may inform the person of the likely consequences (for example, they will stop getting offers), but you cannot block the withdrawal itself.
  • Cease use on withdrawal. Once withdrawn, you stop using the data for that purpose. The PDPC rule of thumb is to give effect within about 10 business days.
  • Keep records of both. Record the consent you obtained (what, when, how) and every withdrawal. If the PDPC asks how you were entitled to market to someone, the record is your answer.
Real world

Marina Retail fixes its sign-up form. Marina's old checkout had one pre-ticked box: "Keep me updated and agree to terms." It bundled the sale with marketing and defaulted to yes - failing on both positive action and reasonableness. The rebuild splits it into two empty boxes: one to complete the order (deemed by contractual necessity anyway), one clearly labelled "Yes, send me Marina offers by SMS" that the customer must tick themselves. Same page, now provable consent.

Practical tip Timestamp and store the exact consent wording shown at the moment of the tick, not just a "consented = true" flag. When a dispute arises two years later, "here is precisely what they agreed to, and when" is far stronger than a boolean.
Build-along · take it further

Rewrite a bad consent line ★ 10 min

The fastest way to internalise valid consent is to fix a broken one. Here is Marina's old line - repair it, then design the record you would keep.

Marina's bad line (fix this)Why it fails
"[x] Keep me updated and agree to terms" (pre-ticked, bundled)Default yes = no positive action; sale and marketing bundled; not clear what "updated" means.

Unbundle. Separate the order-completion consent from the marketing consent. The order can rely on contractual necessity; marketing needs its own ask.

Make it a positive action. Start unticked. Write a line the customer actively ticks - name the channel and who is sending. For example: "Yes, send me Marina Retail promotions by SMS. Unsubscribe any time."

Design the record. Sketch the fields you would store on each tick: customer ID, exact consent text shown, channel, timestamp, source page, and a matching withdrawal field. This is what you show the PDPC.

Reflect. In one line: where in your real sign-up flow does a person actually take a positive action to be marketed to - and can you prove it today?

★ Marina Retail after b2 Marina's consent is now real and provable - an unticked, unbundled, channel-specific opt-in with a timestamped record and a clean withdrawal path. In b3 we put it to work: running one full marketing campaign end to end, from scoping the message to keeping the evidence.
Homework

Before session b3 ◐ 40 min total

Source material

Official sources covered

Taught from the PDPC's own guidance on consent. This page covers ~80% of its working content on obtaining and recording consent - deeper obligations land in later sessions.

✓PDPC · Advisory Guidelines on Key Concepts - ConsentPart 1 · clear + unambiguous · positive action · reasonableness · no misleading means
✓PDPC · Advisory Guidelines on Key Concepts - Deemed Consent + WithdrawalPart 2 · s.15(1) conduct · s.15(3) contractual · s.15A notification · s.16 withdrawal
◐PDPA Part 4 (s.14, s.15, s.15A, s.16)Part 1-2 · the statutory basis for valid, deemed, and withdrawn consent
Check yourself

Three questions before you go 🎯 ◐ 90 seconds

1 · Your checkout has a pre-ticked "keep me updated" box. A customer completes the order without touching it. You have...

Valid consent (s.14) needs a positive action on a clear notice. A pre-ticked box and failure to opt out is not clear-and-unambiguous consent - the person has to do the agreeing.

2 · Which is a genuine deemed-consent route under the PDPA?

Deemed consent by notification (s.15A) requires a documented no-adverse-effect assessment plus notice and a reasonable opt-out window. A bought list or a short non-reply is not deemed consent.

3 · A customer withdraws marketing consent. You must...

Under s.16 you cannot prohibit withdrawal; you may inform of consequences, then must cease use - the PDPC rule of thumb is about 10 business days - and record the withdrawal.

Practitioner session 2 cheat sheet · pin this

Valid consent (s.14)Clear and unambiguous - a positive action on a clear notice. Not a pre-ticked box, not silence.
Reasonableness limitCannot require consent beyond what is reasonable to provide the product or service.
No misleading meansConsent obtained by false or misleading means is not valid consent.
Deemed by conduct (s.15(1))Volunteers data for an obvious purpose - covers that purpose only, not marketing.
Deemed by contract (s.15(3))Reasonably necessary to conclude or perform a transaction; can extend downstream.
Deemed by notification (s.15A)Assess no adverse effect + notify + reasonable opt-out period. Document it.
Withdrawal (s.16)Any time, reasonable notice. Inform of consequences, do not prohibit, then cease use (~10 business days).
Keep recordsStore exact consent wording + when + how, and every withdrawal. That record is your proof.