[{"data":1,"prerenderedAt":281},["ShallowReactive",2],{"focus:data-principal-rights-and-grievance":3},{"id":4,"title":5,"body":6,"decision":269,"description":270,"extension":271,"eyebrow":272,"focusArea":12,"lead":273,"meta":274,"navigation":275,"order":276,"path":277,"seo":278,"stem":279,"__hash__":280},"content\u002Fenterprises\u002Ffocus-areas\u002Fdata-principal-rights-and-grievance.md","Answering people: data principal rights and grievance redressal",{"type":7,"value":8,"toc":258},"minimark",[9,13,18,22,26,33,39,51,62,66,69,180,183,187,191,194,197,201,220,224,238],[10,11],"self-assessment-scorecard",{"slug":12},"data-principal-rights-and-grievance",[14,15,17],"h2",{"id":16},"what-the-rights-are","What the rights are",[19,20,21],"p",{},"A data principal can ask for a summary of their personal data and how it is being processed, ask for correction and erasure, nominate someone to act for them, and raise a grievance. On grievances the discipline is specific: you must publish how a person raises one, and answer within the period you publish. The published period binds you, and the Board is the next stop for an unanswered grievance.",[14,23,25],{"id":24},"the-framework-four-moves","The framework: four moves",[19,27,28,32],{},[29,30,31],"strong",{},"Move 1: Build intake on every channel."," Website, app, call centre, branch, email. Log and acknowledge automatically. Every channel has a named owner: a request that arrives where nobody owns it is a missed deadline waiting to happen.",[19,34,35,38],{},[29,36,37],{},"Move 2: Verify proportionately."," Check enough identity to stop one person reading another's data. The check should not collect more data than the request itself involves.",[19,40,41,44,45,50],{},[29,42,43],{},"Move 3: Retrieve, decide, respond."," The request executes against the systems where the data actually lives; this is where the ",[46,47,49],"a",{"href":48},"\u002Fenterprises\u002Ffocus-areas\u002Fdata-discovery-classification-and-mapping","discovery and mapping work"," pays off. Every decision is reasoned: granted, partially granted, or refused with reasons recorded. A reasoned refusal is a defensible outcome; silence is not. Respond in plain language, inside your stated timeline.",[19,52,53,56,57,61],{},[29,54,55],{},"Move 4: Close with evidence, and layer the grievance SLA."," Record what was requested, verified, found, decided and done, and when. On top, the grievance machinery: one visible published channel, automatic acknowledgement, escalation for grievances that miss their clock, closure tracking with reasons, and volume and ageing reports to the DPO office. Erasure deserves special honesty: \"deleted\" in the app while copies persist in the warehouse and at processors is not erasure. The ",[46,58,60],{"href":59},"\u002Fenterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation","retention and erasure page"," covers how to reach archives, backups and partners.",[14,63,65],{"id":64},"template-the-request-and-grievance-log","Template: the request and grievance log",[19,67,68],{},"One row per request or grievance. Copy this and fill it in.",[70,71,72,106],"table",{},[73,74,75],"thead",{},[76,77,78,82,85,88,91,94,97,100,103],"tr",{},[79,80,81],"th",{},"ID",[79,83,84],{},"Type",[79,86,87],{},"Channel",[79,89,90],{},"Received",[79,92,93],{},"Verified",[79,95,96],{},"Decision and reasons",[79,98,99],{},"Responded",[79,101,102],{},"Closed",[79,104,105],{},"Days taken",[107,108,109,135,160],"tbody",{},[76,110,111,115,118,121,123,125,128,130,132],{},[112,113,114],"td",{},"Example: R-104",[112,116,117],{},"Access summary",[112,119,120],{},"App",[112,122],{},[112,124],{},[112,126,127],{},"Granted in full",[112,129],{},[112,131],{},[112,133,134],{},"6",[76,136,137,140,143,146,148,150,153,155,157],{},[112,138,139],{},"Example: G-21",[112,141,142],{},"Grievance, marketing after withdrawal",[112,144,145],{},"Email",[112,147],{},[112,149],{},[112,151,152],{},"Upheld; suppression list fixed",[112,154],{},[112,156],{},[112,158,159],{},"3",[76,161,162,164,166,168,170,172,174,176,178],{},[112,163],{},[112,165],{},[112,167],{},[112,169],{},[112,171],{},[112,173],{},[112,175],{},[112,177],{},[112,179],{},[19,181,182],{},"The downloadable file adds the full field list, including the evidence each closure must carry.",[184,185],"template-download-card",{"slug":186},"rights-and-grievance-log",[14,188,190],{"id":189},"what-good-looks-like-at-the-end","What good looks like at the end",[19,192,193],{},"You should have: live workflows for each request type with owners and clocks, verification standards per channel, a published grievance channel with its response period, and closure records that prove handling.",[19,195,196],{},"The live test: submit one request of each type through your own channels, as a customer would. Track how long each takes, how many people had to be asked, and whether the answer was complete. Then try a withdrawal and check whether processing actually stopped everywhere.",[14,198,200],{"id":199},"where-enterprises-go-wrong","Where enterprises go wrong",[202,203,204,208,211,214,217],"ul",{},[205,206,207],"li",{},"A request form that feeds a mailbox nobody owns.",[205,209,210],{},"Identity checks that demand more data than the request itself involves.",[205,212,213],{},"Erasure answered in the app while copies persist in the warehouse and at processors.",[205,215,216],{},"A published response period chosen for marketing, then missed.",[205,218,219],{},"No evidence of closure, so a handled request looks exactly like an ignored one.",[14,221,223],{"id":222},"the-decisions-to-make","The decisions to make",[202,225,226,229,232,235],{},[205,227,228],{},"Which request types are automated versus manual, and to what depth.",[205,230,231],{},"Verification strength per channel.",[205,233,234],{},"Whether the grievance system is bought, built, or run on existing ticketing.",[205,236,237],{},"How request and grievance SLAs align with the published response period.",[239,240,241,246],"blockquote",{},[19,242,243],{},[29,244,245],{},"Next step",[19,247,248,252,253,257],{},[46,249,251],{"href":250},"\u002Fenterprises\u002Ffocus-areas\u002Frecord-of-processing-and-dpia","The record of processing and impact assessments",", the register these workflows read from. If you need help with any of this, ",[46,254,256],{"href":255},"\u002Fcontact","write to us"," and we will help.",{"title":259,"searchDepth":260,"depth":260,"links":261},"",3,[262,264,265,266,267,268],{"id":16,"depth":263,"text":17},2,{"id":24,"depth":263,"text":25},{"id":64,"depth":263,"text":65},{"id":189,"depth":263,"text":190},{"id":199,"depth":263,"text":200},{"id":222,"depth":263,"text":223},null,"People can ask you what data you hold on them, ask you to correct or erase it, withdraw consent, and complain when they are not heard. Rights requests are the...","md","Focus area 04","People can ask you what data you hold on them, ask you to correct or erase it, withdraw consent, and complain when they are not heard. Rights requests are the part of the law the public actually touches. A working process turns a potential complaint to the Data Protection Board into a closed ticket, with the evidence to show it was handled. The duties attach once the relevant provisions commence; the dates and timeline page carries the verified position.",{},true,4,"\u002Fenterprises\u002Ffocus-areas\u002Fdata-principal-rights-and-grievance",{"title":5,"description":270},"enterprises\u002Ffocus-areas\u002Fdata-principal-rights-and-grievance","qDkecY_ZTIIq7c6YdvC85Sv3oX335OClmbeD2E9z2sg",1795073010194]