[{"data":1,"prerenderedAt":253},["ShallowReactive",2],{"focus:policies-notices-and-consent":3},{"id":4,"title":5,"body":6,"decision":242,"description":243,"extension":244,"eyebrow":245,"focusArea":12,"lead":246,"meta":247,"navigation":248,"order":233,"path":249,"seo":250,"stem":251,"__hash__":252},"content\u002Fenterprises\u002Ffocus-areas\u002Fpolicies-notices-and-consent.md","Policies, notices and consent: the paper and the machinery of permission",{"type":7,"value":8,"toc":231},"minimark",[9,13,18,22,25,29,36,42,48,54,57,61,64,146,149,153,157,160,163,167,186,190,210],[10,11],"self-assessment-scorecard",{"slug":12},"policies-notices-and-consent",[14,15,17],"h2",{"id":16},"what-valid-consent-requires","What valid consent requires",[19,20,21],"p",{},"Before collecting personal data on the basis of consent, you owe the person a notice: a clear description of the data you want, the purpose, how they can exercise their rights, how to withdraw consent, and how to complain to the Data Protection Board. Consent given without a proper notice is not valid consent, and every downstream use of that data then rests on nothing.",[19,23,24],{},"Under the Act, consent is valid only when it is free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action. A pre-ticked box, a bundled \"agree to everything\", or consent forced as a condition for an unrelated service can all fail the test, taking the legal basis for the processing with them. Withdrawal must be as easy as giving, and when consent dies, your processors must stop too.",[14,26,28],{"id":27},"the-framework-four-moves","The framework: four moves",[19,30,31,35],{},[32,33,34],"strong",{},"Move 1: Write the notice suite."," One notice per purpose, each class of data and each purpose described separately. Offer the choice of English or any of the 22 Eighth Schedule languages; the choice is the person's under the law, and large organisations are preparing all 22 as practice. Keep every published version on file with its dates: the notice that matters in a complaint is the one shown on that day. Put publishing behind a maker-checker workflow so one person cannot silently change what customers see.",[19,37,38,41],{},[32,39,40],{},"Move 2: Design the yes."," Separate purposes so each can be accepted or refused on its own. Record every choice as an explicit action. For each processing activity, write down the legal basis: consent, or a permitted non-consent ground such as voluntary provision for a purpose the person asked for, certain state functions, employment purposes or medical emergencies. Never manufacture a consent record for an activity that properly runs on another basis.",[19,43,44,47],{},[32,45,46],{},"Move 3: Build withdrawal that propagates."," Map every system and partner that receives data under each purpose. Build the withdrawal signal to reach all of them, with confirmation and retries. Test end to end. For anyone under 18, and for a person with disability who has a lawful guardian, consent comes from the parent or guardian and you must verify that relationship; collect the minimum data needed for the check. Behavioural monitoring of children and targeted advertising at them are prohibited.",[19,49,50,53],{},[32,51,52],{},"Move 4: Keep the artefact."," The consent artefact is the stored proof of a consent event: the exact notice version and language shown, the data categories and purposes, the choice, the time, the channel, the identity it belongs to. Make records tamper-evident, aligned with the Government's published electronic consent framework, exportable in readable form, kept for the life of the relationship and the required period after. \"Our system shows a tick\" is not enough if nobody can reconstruct what the tick referred to.",[19,55,56],{},"One more layer: Consent Managers, registered platforms through which a person manages consent across enterprises from one place, are in force now. If your sector will interact with them, finance already has account-aggregator-style sharing, your systems must honour external consent instructions exactly like ones captured on your own screens.",[14,58,60],{"id":59},"template-the-notice-and-consent-register","Template: the notice and consent register",[19,62,63],{},"One row per purpose per channel. Copy this and fill it in.",[65,66,67,98],"table",{},[68,69,70],"thead",{},[71,72,73,77,80,83,86,89,92,95],"tr",{},[74,75,76],"th",{},"Purpose",[74,78,79],{},"Legal basis",[74,81,82],{},"Notice version",[74,84,85],{},"Languages",[74,87,88],{},"Channels",[74,90,91],{},"Systems and partners fed",[74,93,94],{},"Withdrawal route",[74,96,97],{},"Artefact stored where",[99,100,101,128],"tbody",{},[71,102,103,107,110,113,116,119,122,125],{},[104,105,106],"td",{},"Example: account opening",[104,108,109],{},"Consent",[104,111,112],{},"v3.2",[104,114,115],{},"English, Hindi, +6",[104,117,118],{},"App, branch",[104,120,121],{},"Core banking app, KYC agency",[104,123,124],{},"App settings, branch form",[104,126,127],{},"Consent store, exportable",[71,129,130,132,134,136,138,140,142,144],{},[104,131],{},[104,133],{},[104,135],{},[104,137],{},[104,139],{},[104,141],{},[104,143],{},[104,145],{},[19,147,148],{},"The downloadable file adds the consent artefact field list: the exact proof each consent event must leave behind.",[150,151],"template-download-card",{"slug":152},"notice-and-consent-register",[14,154,156],{"id":155},"what-good-looks-like-at-the-end","What good looks like at the end",[19,158,159],{},"You should have: an approved notice set with version history, consent journeys on every channel including offline, a working artefact store, tested withdrawal propagation, and the records to prove all of it.",[19,161,162],{},"The live test: pick one customer and one date. Produce the notice they saw, in the language they saw it, and the choice they made. Then withdraw a consent in one channel and watch every other channel and partner stop. If either takes weeks, the machinery is not there.",[14,164,166],{"id":165},"where-enterprises-go-wrong","Where enterprises go wrong",[168,169,170,174,177,180,183],"ul",{},[171,172,173],"li",{},"One bundled privacy policy treated as the notice.",[171,175,176],{},"Silent edits to notices with no version history, and translations that drift from the approved text.",[171,178,179],{},"One yes covering everything, or dark patterns that make \"no\" hard to find.",[171,181,182],{},"Withdrawal handled only in the app while the CRM and marketing platform keep processing.",[171,184,185],{},"Consent evidence dying inside a vendor's subscription with no exit export.",[14,187,189],{"id":188},"the-decisions-to-make","The decisions to make",[168,191,192,195,198,201,204,207],{},[171,193,194],{},"Cookie and tracker consent: in scope or not, on which properties.",[171,196,197],{},"Offline and branch capture: required or not, and how it is digitised to the same evidence value as online.",[171,199,200],{},"Language coverage depth: the two you need, or all 22.",[171,202,203],{},"The artefact standard to align to.",[171,205,206],{},"Build, buy or extend existing tooling for consent management, decided after your systems are mapped, not before.",[171,208,209],{},"How and when to prepare for Consent Manager interactions.",[211,212,213,218],"blockquote",{},[19,214,215],{},[32,216,217],{},"Next step",[19,219,220,225,226,230],{},[221,222,224],"a",{"href":223},"\u002Fenterprises\u002Ffocus-areas\u002Fdata-principal-rights-and-grievance","Answering people",", the requests and grievances your consent records will have to support. If you need help with any of this, ",[221,227,229],{"href":228},"\u002Fcontact","write to us"," and we will help.",{"title":232,"searchDepth":233,"depth":233,"links":234},"",3,[235,237,238,239,240,241],{"id":16,"depth":236,"text":17},2,{"id":27,"depth":236,"text":28},{"id":59,"depth":236,"text":60},{"id":155,"depth":236,"text":156},{"id":165,"depth":236,"text":166},{"id":188,"depth":236,"text":189},null,"Consent is the part of data protection most likely to be tested by a real dispute, and the part where implementations quietly fail. In a dispute, the first...","md","Focus area 03","Consent is the part of data protection most likely to be tested by a real dispute, and the part where implementations quietly fail. In a dispute, the first question is \"show me what the person was told\". This page helps you test whether your notices and consent journeys would survive that question, on every channel you run.",{},true,"\u002Fenterprises\u002Ffocus-areas\u002Fpolicies-notices-and-consent",{"title":5,"description":243},"enterprises\u002Ffocus-areas\u002Fpolicies-notices-and-consent","gIaMfH-9u_rYrHEm4KKEIDkIpKebafzvUMdudNtv51g",1795073010183]