AIS CONSENT RE-CONSENT Clause Samples

AIS CONSENT RE-CONSENT. 4.6.1 When the Client procures: (i) initial consent; and (ii) re-consent (also referred to as ‘renew consent’) from End Users, for the purposes of Bud providing Account Information Services, from within the Client’s own user interface and using its own consent flows (“AIS Consent Flows”, the Client shall be permitted to do so provided that: the AIS Consent Flows are kept within the Client’s domain (it being made clear to the End User that the AIS Consent Flow is f or the purposes of AIS, and distinctive from other of the Client’s propositions, as applicable); the Client shall, for the purposes of designing the AIS Consent Flows, follow the key principles of example initial and re-consent Account Information Services flows (and related guidance) provided by TransUnion or Bud to the Client, which shall include but not be limited to, clearly procuring the End User’s explicit consent to Bud accessing the End User’s accounts as part of Account Information Services (the “Bud AIS Consent Requirements”); the Client shall submit to and have received the prior written consent of Bud’s Legal, Risk and Compliance team (“Bud LRC”) prior to the initial deployment of and any and all UI changes subsequently proposed to be made to the AIS Consent Flows; and 4.6.2 each of Bud and TransUnion shall, acting reasonably, have the right to require the Client to make amendments to the AIS Consent Flows as soon as reasonably practicable to ensure ongoing compliance with Applicable Law.