[{"data":1,"prerenderedAt":265},["ShallowReactive",2],{"focus:systems-integration":3},{"id":4,"title":5,"body":6,"decision":253,"description":254,"extension":255,"eyebrow":256,"focusArea":12,"lead":257,"meta":258,"navigation":259,"order":260,"path":261,"seo":262,"stem":263,"__hash__":264},"content\u002Fenterprises\u002Ffocus-areas\u002Fsystems-integration.md","Making privacy work inside your systems",{"type":7,"value":8,"toc":242},"minimark",[9,13,18,28,32,39,45,51,62,66,69,164,167,171,175,178,181,185,201,205,222],[10,11],"self-assessment-scorecard",{"slug":12},"systems-integration",[14,15,17],"h2",{"id":16},"what-integration-means-here","What integration means here",[19,20,21,22,27],"p",{},"The ",[23,24,26],"a",{"href":25},"\u002Fenterprises\u002Ffocus-areas\u002Fdata-discovery-classification-and-mapping","discovery and mapping work"," tells you which systems hold personal data and act on consent: core business systems, CRM, marketing platforms, data warehouses, HR systems, document management, partner connections. Integration makes the duties executable across them. In banking the connection list is consistent: the core banking system, internet and mobile banking, payment and digital lending platforms, payment rails, identity services on a strict consent basis, document management, HR systems and third-party providers.",[14,29,31],{"id":30},"the-framework-four-moves","The framework: four moves",[19,33,34,38],{},[35,36,37],"strong",{},"Move 1: Map before you buy."," Inventory the systems that must connect before evaluating any platform. The map comes first; the platform is chosen against it.",[19,40,41,44],{},[35,42,43],{},"Move 2: Set the architecture and the posture."," API-first and modular. Decide deployment early: your own data centres, your own cloud tenancy, or vendor hosting. Regulated enterprises increasingly insist on their own environment; some mandate deployment on their own public-cloud tenancy. The choice is hard to reverse, so make it with security, sectoral and cost input. Settle infrastructure responsibility and environment sizing. Plan the legacy path: systems without APIs need adapters, file-based bridges or staged replacement; ignoring them leaves the oldest data outside the programme.",[19,46,47,50],{},[35,48,49],{},"Move 3: Connect and test the duties."," Consent propagation, request execution, deletion reach: each tested like a duty, with pass or fail evidence. A demonstration on the vendor's sample data proves nothing about your estate.",[19,52,53,56,57,61],{},[35,54,55],{},"Move 4: Plan the exit and the AI guardrails."," The export test: notices, consent events, artefacts, configurations, all exportable in readable form, so consent evidence never dies inside a subscription. On AI inside privacy operations, careful practice admits it only with guardrails: no autonomous AI decisions about people without human review, AI activity logged in the processing records, model documentation available to the DPO for audit, and an AI bill of materials alongside the software and hardware ones. The ",[23,58,60],{"href":59},"\u002Fenterprises\u002Fai-tools","AI tools page"," covers the wider picture.",[14,63,65],{"id":64},"template-the-integration-connection-register","Template: the integration connection register",[19,67,68],{},"One row per system. Copy this and fill it in.",[70,71,72,100],"table",{},[73,74,75],"thead",{},[76,77,78,82,85,88,91,94,97],"tr",{},[79,80,81],"th",{},"System",[79,83,84],{},"What it holds",[79,86,87],{},"Connection type",[79,89,90],{},"Duties it must execute",[79,92,93],{},"Test status",[79,95,96],{},"Last tested",[79,98,99],{},"Owner",[101,102,103,126,148],"tbody",{},[76,104,105,109,112,115,118,121,123],{},[106,107,108],"td",{},"Example: marketing platform",[106,110,111],{},"Customer profiles, consents",[106,113,114],{},"API",[106,116,117],{},"Consent propagation, erasure",[106,119,120],{},"Passing",[106,122],{},[106,124,125],{},"Digital",[76,127,128,131,134,137,140,143,145],{},[106,129,130],{},"Example: legacy loan system",[106,132,133],{},"Closed loan files",[106,135,136],{},"File bridge",[106,138,139],{},"Rights retrieval, deletion",[106,141,142],{},"Partial",[106,144],{},[106,146,147],{},"IT",[76,149,150,152,154,156,158,160,162],{},[106,151],{},[106,153],{},[106,155],{},[106,157],{},[106,159],{},[106,161],{},[106,163],{},[19,165,166],{},"The downloadable file adds the column guide and the duty-level test list.",[168,169],"template-download-card",{"slug":170},"integration-connection-register",[14,172,174],{"id":173},"what-good-looks-like-at-the-end","What good looks like at the end",[19,176,177],{},"You should have: an integration architecture and API specifications, a decided deployment posture, environment sizing, and integration test results proving the duties execute across systems.",[19,179,180],{},"The live test: capture consent on one channel, withdraw it on another, and verify the stop in every downstream system and at one partner. Then ask the vendor to export everything: notices, events, artefacts, configurations. Both results tell you whether the integration is real.",[14,182,184],{"id":183},"where-enterprises-go-wrong","Where enterprises go wrong",[186,187,188,192,195,198],"ul",{},[189,190,191],"li",{},"Buying the platform before mapping the systems it must touch.",[189,193,194],{},"Accepting a demonstration on the vendor's sample data as proof of fit.",[189,196,197],{},"No exit plan: consent evidence locked inside a subscription.",[189,199,200],{},"Core system replacement smuggled into a privacy project. Integration connects privacy capability to what exists; rebuilding what exists is a separate programme with a separate budget.",[14,202,204],{"id":203},"the-decisions-to-make","The decisions to make",[186,206,207,210,213,216,219],{},[189,208,209],{},"Deployment model and who hosts.",[189,211,212],{},"Infrastructure responsibility and environment sizing.",[189,214,215],{},"Integration breadth: how many systems in phase one, and which.",[189,217,218],{},"How legacy systems without APIs are handled.",[189,220,221],{},"Whether and how AI is admitted into privacy operations, under which guardrails.",[223,224,225,230],"blockquote",{},[19,226,227],{},[35,228,229],{},"Next step",[19,231,232,236,237,241],{},[23,233,235],{"href":234},"\u002Fenterprises\u002Ffocus-areas\u002Ftraining-and-awareness","Training the people who touch personal data",", because systems do not leak data on their own. If you need help with any of this, ",[23,238,240],{"href":239},"\u002Fcontact","write to us"," and we will help.",{"title":243,"searchDepth":244,"depth":244,"links":245},"",3,[246,248,249,250,251,252],{"id":16,"depth":247,"text":17},2,{"id":30,"depth":247,"text":31},{"id":64,"depth":247,"text":65},{"id":173,"depth":247,"text":174},{"id":183,"depth":247,"text":184},{"id":203,"depth":247,"text":204},null,"Integration is where privacy programmes quietly fail: consent captured on the website that never reaches the marketing platform, a deletion request that...","md","Focus area 11","Integration is where privacy programmes quietly fail: consent captured on the website that never reaches the marketing platform, a deletion request that cannot reach the backup policy. Privacy tooling has to execute inside your real estate, not beside it. When consent changes, the change must reach every system that acts on it. When a right is exercised, the request must reach the systems where the data lives. When retention ends, deletion must reach archives and backups.",{},true,11,"\u002Fenterprises\u002Ffocus-areas\u002Fsystems-integration",{"title":5,"description":254},"enterprises\u002Ffocus-areas\u002Fsystems-integration","GffBdmUbOF_-VR1ZVo1HzV4XgtLx2zewx3rTTpJlC0U",1795073010250]