<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="434954" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="11/11/2026" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="285,906,972,1471" />
         <classifier id="Layer" value="Layer 1"/>
          <classifier id="numcol" value="4"/>
         <classifier id="ArticleStyle" value=""/>
       <classifier id="Epaper-Build" value="7.1.5.2"/>
  <classifier id="ProcessingDateTime" value="Tue Nov 10 2026 20:33:14 GMT+0600"/>
      </identified-content>

      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20261111T000000+5.30" edition.name="Dhaka Edition" edition.area="MAI" position.section="DST11112606MAI-EDITORIAL" position.sequence="6" ex-ref="DST11112606MAI-EDITORIAL.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
<body.head>
      <hedline>
    	<hl1 id="Headline1" ul="0" ol="0" ulColor=""  ulWeight=""  olColor=""  olWeight="" textFrameColor="" orgstyle="[No Paragraph Style]" class="1" MainHead="true" style="Headline1">
		<lang class="3" colour="#000000" orgstyle="[No Paragraph Style]" style="Headline1"  font="Antonia H1" fontStyle="Medium" size="40">Our banking future cannot come at the cost of data privacy</lang>
	</hl1>

       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
		<media-reference id="tn" source-credit="" data-location="1" source="ImageOfFrame38852_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
<media-reference id="tn" source-credit="" data-location="2" source="namzul_photo_10_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
	</media>
</block>

     <p style=".Bodylaser" ul="0" ol="0"  orgstyle="INDENTLESS BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="INDENTLESS BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">In August 2025, at least 54 customers of a multinational bank in Bangladesh reported that a total of Tk 27 lakh had been fraudulently transferred from their credit cards to unknown bKash and Nagad accounts without any OTP being shared. The bank initially refused to treat the transactions as fraud because they were OTP verified. If fraudsters can compromise the very systems responsible for delivering our security codes, how safe is the data we hand over to banks every day?
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">This question becomes more urgent as the country’s banking sector embraces artificial intelligence. From detecting suspicious transactions to assessing loan eligibility, AI is transforming financial services. However, this smartness comes with the invisible risk to the security of personal and financial data. Bank balances, transaction histories, and shopping patterns all become part of the database that AI learns from. As mobile financial services expand, data accumulates on bank and fintech servers. The more centralised the data, the more catastrophic a single leak becomes.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Banks rely on National ID information for customer verification. The 2023 leak of NID and birth registration data of millions of citizens from a government service exposed its vulnerability. When names, addresses, and dates of birth fall into criminal hands, fake bank accounts and fraudulent loans become easy. A 2025 Financial Consumer Protection Survey found that nearly 30 percent of digital financial service users in Bangladesh did not have a PIN or password on their phone to protect their accounts. Among those who did, 45 percent shared it with others, typically family members.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Article 43 (b) of the constitution recognises citizens’ right to the privacy of correspondence and communication. But informational privacy has yet to become a standalone right. The Personal Data Protection Act, 2026 covers identifiable financial information but lacks AI-specific provisions, such as the right to explanation for automated decisions or mandatory algorithmic audits. Section 7 of the Bankers Books Evidence Act, 2021 imposes strict restrictions on disclosing customer information without prescribed conditions, but enforcement remains weak. Chapter 14 of the Bangladesh Banks Guideline on ICT Security (4.0) warns about AI risks, including flawed algorithms, biased outcomes, and cyber attacks, However, it is a guideline, not a binding law. The Bangladesh Bank began drafting an integrated AI policy for the banking sector in late 2025, forming a seven-member team to prepare guidelines and announcing plans to develop its own large language model (LLM) to reduce dependence on foreign AI tools. However, the broader policy had yet to be officially published as of November 2026. On November 1, the central bank reiterated that it was working on a separate AI-focused cybersecurity policy for banks and financial institutions.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">In June 2026, the central bank instructed its officials not to input confidential or sensitive banking information into AI tools like ChatGPT, Gemini or Claude, citing cross-border data transfer risks. Meanwhile, a study by the Bangladesh Institute of Bank Management found that nearly 60 percent of local banks lack any policy for using AI in cybersecurity.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Internationally, three cases offer lessons. In Germany in 2023, the Court of Justice of the European Union (CJEU) ruled in </lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Regular Italic" size="9">OQ v Land Hessen (SCHUFA)</lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9"> that an automated credit score constitutes an automated individual decision when a lender relies heavily on it to determine whether to grant credit. For Bangladesh, this means automated credit scores used in loan approvals should be subject to legal safeguards for automated decision-making, including customers’ right to understand how these scores influence lending decisions. In 2025 in Austria, the CJEU clarified in </lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Regular Italic" size="9">CK v Magistrat der Stadt Wien (Dun and Bradstreet)</lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9"> that trade secrecy cannot be used as a blanket excuse to deny a customer meaningful information about the logic of an AI decision. The data protection law must close the path for banks to refuse a customer’s right to explanation by citing trade secrets. In Poland, Toyota Bank Polska was fined approximately Tk 1.6 crore in 2025 for failing to properly document customer profiling and for not ensuring the independence of its data protection officer. This means mandatory data protection impact assessments must be conducted before AI-driven profiling, and the DPO must report directly to the board.  
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Three things become clear. First, despite laws and guidelines, practical enforcement and accountability are lacking. Second, citizens often don’t know who is taking their data, how long it is kept, or whether it is being used to train AI models. Third, without an independent and empowered supervisory body, laws remain on paper.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">There is a path forward. First, banks must stop collecting excessive data, ensure strong encryption and limited access, and conduct regular security audits. Second, data usage terms with third-party technology providers must be clarified. Third, in automated decisions, customers must have the right to an explanation and access to human review. Fourth, Bangladesh Bank must finalise and publish its long-delayed AI policy for the banking sector. And last, digital literacy must be expanded. Mass awareness must be built about keeping OTPs secret, not clicking unknown links, and checking app permissions. A protection framework combining law, technology, and awareness is essential, one where the banking sector becomes modern but citizens’ personal data remains intact.</lang>
</p>

    </body.content>
  </body>
</nitf>