Help center Core configuration Auditing & privacy Maintain privacy contacts and review the data-processing addendum Updated Wednesday, October 28, 2026 · Marc Staine The GDPR settings page records privacy-contact information and the account’s data-processing-addendum acceptance state. It provides an administrative workflow for these details; it does not determine whether your organization has met every legal obligation. Applies to: Supportbench Core. Location: Authorized GDPR settings page, /agent/settings/1073/. This page is not a guaranteed visible sidebar item.. Access and editable controls depend on the relevant administration permissions. Before you begin Confirm the organization-appointed privacy contacts and who is authorized to accept the addendum. This procedure explains the product controls; it does not replace review of the agreement.Read the existing Accepted on / Accepted by state before taking action. Contact changes and agreement acceptance are separate operations. Update contacts and verify acceptance separately Open the authorized GDPR settings page. If the page or editing is unavailable, ask your account administrator to check access and availability.Review Accepted on and Accepted by. Do not assume an empty or failed load proves that no acceptance is recorded.Update the European Union representative and Data Protection Officer blocks as appropriate, including names, postal details and email addresses.Choose Save contact details. Reload and verify the saved contacts; this action does not accept the addendum.If acceptance is required, the authorized representative chooses Review and Accept, reads the displayed agreement, and separately chooses Accept. Verify Accepted on and Accepted by afterward.If a load or save has an uncertain result, choose Retry when offered to reload the recorded state before attempting the action again. Settings reference Addendum and contact detailsSettingWhat it controlsHow to chooseData Processing Addendum link / Review and AcceptThe link opens the external addendum page. Review and Accept opens embedded addendum text with a separate Accept action.An authorized representative should review the actual agreement before accepting.Accepted on / Accepted byRecords the acceptance timestamp in UTC and accepting user.Use the displayed record when checking whether acceptance occurred.European Union representativeContact block for the designated representative.Enter the correct organization-appointed contact where applicable.Data Protection OfficerContact block for the designated officer.Keep details current with the appointed contact.Name / Address lines / City / State / Postal code / Country / EmailFields within each contact block.Use complete, accurate contact details.Save contact detailsSaves the contact blocks independently of agreement acceptance.Reopen to verify the details.RetryAppears conditionally after a load or uncertain-save failure to reload the recorded state.Use the result shown by the page rather than assuming a failed load means no acceptance exists. Behavior to knowContact maintenance and accepting the addendum are distinct actions. Do not treat saving contact details as acceptance. Recommended use Verify contacts after organizational changes so requests reach the responsible people.Keep agreement review with an authorized representative and rely on the recorded acceptance state rather than a remembered button click. Worked example When the designated privacy contact changes, confirm the replacement details with the responsible team.Update only the relevant contact block and choose Save contact details.Reload and verify the new email and postal details. Check acceptance independently; a personnel update is not an acceptance action. Troubleshooting ProblemWhat to checkI cannot find GDPR in the sidebarThe section is not a guaranteed navigation item. Use the authorized settings page or ask the administrator about access.Contacts saved but acceptance did not changeExpected: Save contact details and Accept are distinct actions.The page failed while accepting or savingUse Retry to reload recorded state before repeating. A timeout does not establish that the previous action failed.The acceptance details are unexpectedCheck the displayed accepting user and UTC timestamp; escalate the discrepancy to the responsible account administrator. Related configuration Organization → Configure agent roles and division accessConfiguration → Configure workflows and automationTerms of useData Protection Policy (DPA) Was this article helpful? Yes No Thank you for your feedback.