Christian Rhino

Member of the Board

Since February 2021, Christian Rhino holds the position of Helaba's Chief Infor­mation and Chief Ope­ra­ting Officer (CIO/COO). He as­sumes re­sponsi­bi­lity for the Infor­mation Tech­no­logy, Ope­ra­tions and Orga­ni­sation divi­sions on the Board of Mana­ging Direc­tors.

After com­ple­ting a de­gree in in­dus­trial en­gineering and laun­ching his profes­sional career at Deutsche Bank AG, from 2001 Christian Rhino held various positions within the Com­merz­bank AG Group. 

Until 2007, he was active in the sales unit as Glo­bal Head of Cash Ma­na­ge­ment & Inter­natio­nal Busi­ness. From 2008 to 2012, he was a mem­ber of the Manage­ment Board of mBank S.A., Warsaw, Poland, as Chief Ope­ra­tions Officer (COO). Upon his re­turn to Com­merz­bank AG, he served from 2012 - 2019 as a member of the Executive Team for Banking Operations with re­spon­­sibi­lity for global trans­action bank­ing, cash manage­ment, bank­ing services, credit admin­istra­tion for pri­vate and cor­po­rate custo­mers, archi­ving and the service com­panies of the Group Services division. Most recently, Christian Rhino served as Group Chief Data Officer (CDO) / Executive for Customer Process & Data Management at Com­merz­bank AG before joining Helaba on 1 August 2020.

Christian Rhino, CIO and COO of Helaba
Christian Rhino, CIO and COO of Helaba

Your choice

When we make our website available to you, we use cookies. 

Some are necessary to help our website work properly, and can't be switched off. And some are optional, but support us in order to improve your experience during your visit.

Are you happy to accept cookies to improve our website?

Details

cookie [publisher]purposestorage period
_et_coid [etracker]statistic: cookie detection2 years
allowLoadExternRessources [helaba]statistic: Saves the user decision that external components may be loaded automatically.30 days
allowTracking [helaba]statistic: Saves the user decision that visitor behavior may be tracked.30 days
BT_ctst [etracker]statistic: Is used to detect whether cookies are activated in the visitor's browser or not.session
BT_pdc [etracker]statistic: Contains Base64-coded visitor history data (is customer, newsletter recipient, visitor ID, displayed smart messages) for personalization.2 years
BT_sdc [etracker]statistic: Contains Base64-encoded data of the current visitor session (referrer, number of pages, number of seconds since the beginning of the session), which is used for personalization purposes.session
disclaimer_disclosureRequirements [helaba]necessary: Verification when accessing certain (sub) areas of the websitesession
disclaimer_residenceGermany [helaba]necessary: Verification when accessing certain (sub) areas of the websitesession
hideCookieNotice [helaba]necessary: Saves that the cookie or data protection notice will not be requested every time you visit.30 days
isSdEnabled [etracker]statistic: Detection of whether the visitor's scroll depth is measured.1 hour
WSESSIONID [helaba]necessary: Standard cookie to use with PHP session data.session

You can find out more in our data policy.