Differences
This shows you the differences between two versions of the page.
| — | fake-customer-care-number-scam-india [2026/07/22 17:47] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Fake Customer Care Number Scam India (2026) ====== | ||
| + | |||
| + | |||
| + | |||
| + | {{ : | ||
| + | |||
| + | <WRAP center round info 95%> | ||
| + | **Quick Reply:** Fraudsters impersonate bank/ | ||
| + | </ | ||
| + | |||
| + | {{htmlmetatags> | ||
| + | |||
| + | {{htmlmetatags> | ||
| + | |||
| + | On 12 February 2026, Priya Deshmukh of Pune Googled "HDFC Bank customer care" to block her debit card after a suspicious SMS. The top paid ad displayed 1800‑XXX‑8877. A polite agent collected her card details, OTP, and within four minutes ₹1.87 lakh vanished from her savings account. Priya had dialled not HDFC but a call‑centre operated by a syndicate in Jharkhand that bought Google Ads slots to impersonate twenty banks, insurance firms, and telecom operators. | ||
| + | |||
| + | > **Citizen Crisis Response Network** | ||
| + | > Document every digit, voice recording if possible, Google ad screenshot with timestamp, bank SMS trail, UPI transaction IDs, first FIR within 24 hours under BNS, 2023 §318(4)/ | ||
| + | |||
| + | ===== Direct answer (featured snippet) ===== | ||
| + | |||
| + | Fake customer care number scams lure victims through paid search ads, fraudulent websites, and SMS campaigns that mimic legitimate helplines of banks, telecom operators, and e‑commerce platforms. Once you dial, the scammer extracts card details, OTPs, or remote‑access credentials and drains linked accounts. Legal recourse includes filing an FIR under **BNS, 2023 §318(4) (cheating by personation)** and **§319(3) (cheating by dishonest inducement)** via **BNSS, 2023 §173** within 24 hours, freezing suspect accounts through the National Cyber Crime Reporting Portal (**cybercrime.gov.in**), | ||
| + | |||
| + | ===== In this guide ===== | ||
| + | |||
| + | * [[#How the fake customer care number scam works in 2026]] | ||
| + | * [[#Legal framework: BNS, 2023, BNSS, 2023, IT Act 2000, CPA 2019]] | ||
| + | * [[# | ||
| + | * [[#Filing your FIR and cyber crime complaint (BNSS §173)]] | ||
| + | * [[#Bank liability and zero-liability window under RBI norms]] | ||
| + | * [[#Telecom and advertising platform accountability]] | ||
| + | * [[#Case law and regulatory touchpoints]] | ||
| + | * [[# | ||
| + | * [[#Recovery mechanisms: ombudsman, consumer forums, civil suits]] | ||
| + | * [[# | ||
| + | * [[#Sample FIR text and legal notice]] | ||
| + | * [[#Myth vs reality table]] | ||
| + | |||
| + | ===== How the fake customer care number scam works in 2026 ===== | ||
| + | |||
| + | **The funnel.** Fraudsters purchase Google Ads, Facebook sponsored posts, or bulk SMS campaigns using stolen credit cards. Keywords bid on include "bank customer care," " | ||
| + | |||
| + | **First contact.** You dial. An IVR mimics the bank's voice menu. A human operator answers, often addressing you by first name harvested from data leaks. He cites your last transaction or card's last four digits to build trust. | ||
| + | |||
| + | **The ask.** He claims unusual activity, pending KYC update, reward points expiry, or SIM block. He " | ||
| + | |||
| + | **The drain.** Within seconds UPI auto‑debit, | ||
| + | |||
| + | **Post‑drain.** The number goes dead. Google Ad account vanishes. The domain is parked on a bulletproof hosting service in Eastern Europe. Victim realises fraud only when balance‑alert SMS arrives. | ||
| + | |||
| + | > **Warning** — A single OTP shared with a fake helpline can trigger up to ₹5 lakh in outflows before SMS alerts catch up. RBI's January 2026 circular mandates real‑time card‑block APIs, but not all co‑operative banks comply. | ||
| + | |||
| + | By March 2026, the Indian Cyber Crime Coordination Centre (I4C) logged 1.73 lakh complaints under this modus operandi, with cumulative losses exceeding ₹2,100 crore. Maharashtra, | ||
| + | |||
| + | ===== Legal framework: BNS, 2023, BNSS, 2023, IT Act 2000, CPA 2019 ===== | ||
| + | |||
| + | **Bharatiya Nyaya Sanhita 2024** | ||
| + | |||
| + | * **§318(4) – Cheating by personation: | ||
| + | * **§319(3) – Cheating by dishonest inducement: | ||
| + | * **§308 – Theft:** Dishonestly taking movable property (digital money qualifies post‑2023 Supreme Court dicta). | ||
| + | * **§336 – Forgery of electronic record:** Creating fake domain certificates, | ||
| + | |||
| + | **Bharatiya Nagarik Suraksha Sanhita 2024** | ||
| + | |||
| + | * **§173(1)** – Cognisable offence FIR: Police **shall** register without preliminary enquiry; refusal invites disciplinary action under §173(3). | ||
| + | * **§193** – Power to freeze assets: Magistrate may order interim attachment of suspect bank accounts on application by investigating officer. | ||
| + | * **§35** – Jurisdiction: | ||
| + | |||
| + | **Information Technology Act 2000 (amended 2023)** | ||
| + | |||
| + | * **§66C – Identity theft:** Using another' | ||
| + | * **§66D – Cheating by personation using computer resource:** Overlaps BNS §318(4); IT Act penalty is cumulative. | ||
| + | * **§43(b) – Unauthorised downloading/ | ||
| + | |||
| + | **Consumer Protection Act 2019** | ||
| + | |||
| + | * **§2(7) – Deficiency in service:** Bank or telecom provider' | ||
| + | * **§21(a)(i) – District forum jurisdiction: | ||
| + | |||
| + | > **Most citizens miss this** — You can invoke **both** criminal (BNS/IT Act) and civil (CPA) remedies simultaneously. A criminal conviction is not a prerequisite for consumer‑forum compensation; | ||
| + | |||
| + | ===== Immediate steps if you dialled a fake helpline ===== | ||
| + | |||
| + | **Minute zero to five** | ||
| + | |||
| + | 1. **Hang up** the moment any " | ||
| + | 2. **Call the official helpline** from your bank's physical debit card, chequebook, or verified mobile app. Report " | ||
| + | 3. **Block all cards** linked to the account discussed. Use mobile banking app or SMS keywords (e.g. BLOCK < | ||
| + | 4. **Screenshot** the Google Ad, save the phone number from call log, note exact dialogue and time. | ||
| + | |||
| + | **Hour one to three** | ||
| + | |||
| + | 5. **File online complaint** at **https:// | ||
| + | 6. **Visit nearest police station** with printouts: ad screenshot, bank SMS trail, cybercrime.gov.in acknowledgement number. Demand FIR under **BNS §318(4), §319(3), IT Act §66C, §66D**; cite **BNSS §173(1)** if officer hesitates. | ||
| + | 7. **Email your bank's nodal officer** (name + ID available on bank website under Grievance Redressal). Subject line: "Fraud transaction alert – provisional credit requested under RBI Master Direction." | ||
| + | |||
| + | **Day one** | ||
| + | |||
| + | 8. **Lodge written complaint** with National Payments Corporation of India (NPCI) if UPI was used: **[email protected]**. Cite transaction UTR, timestamp, beneficiary VPA. | ||
| + | 9. **Inform telecom provider** (Airtel/ | ||
| + | 10. **Change all passwords, PINs, MPINs** for banking, UPI, email, and linked e‑commerce accounts. | ||
| + | |||
| + | > **Do this immediately** — RBI's April 2025 circular mandates banks provide provisional credit within **ten working days** if you report fraud within **three days** of transaction and before notifying the bank of unauthorised debit. Miss that 72‑hour window and liability shifts. | ||
| + | |||
| + | ===== Filing your FIR and cyber crime complaint (BNSS §173) ===== | ||
| + | |||
| + | **Jurisdictional choice.** Under **BNSS §35**, you may file the FIR at: | ||
| + | |||
| + | * Your place of residence. | ||
| + | * The police station covering the suspect' | ||
| + | * The Cyber Crime Police Station of the state (centralised; | ||
| + | |||
| + | **Essential FIR contents** | ||
| + | |||
| + | * **Chronology: | ||
| + | * **Monetary loss:** Exact ₹ amount, transaction IDs (UTR/RRN), beneficiary account number/VPA. | ||
| + | * **Evidence custody:** State you have preserved call recording, SMS OTP log, Google Ad screenshot, bank SMS trail. | ||
| + | * **Statutory penal sections:** Explicitly request BNS, 2023 §318(4), §319(3), IT Act 2000 §66C, §66D. | ||
| + | * **Prayer:** Immediate freezing of beneficiary accounts under **BNSS §193**, forensic examination of telecom CDR, coordination with I4C for inter‑state suspects. | ||
| + | |||
| + | **Sample FIR text** (adapt to facts): | ||
| + | |||
| + | < | ||
| + | To, | ||
| + | The Station House Officer, | ||
| + | Cyber Crime Police Station, | ||
| + | [City], [State] | ||
| + | |||
| + | Subject: FIR under BNS, 2023 §318(4), §319(3), IT Act 2000 §66C, §66D — Fake Customer Care Helpline Fraud | ||
| + | |||
| + | Sir/Madam, | ||
| + | |||
| + | I, [Your Full Name], aged [__], residing at [Full Address], Aadhaar [Last Four Digits], mobile [____], hereby lodge a formal complaint of cheating by personation and identity theft. | ||
| + | |||
| + | FACTS: | ||
| + | 1. On [Date] at [Time] hours, I Googled "HDFC Bank customer care" to block my debit card [last four digits ____]. | ||
| + | 2. The top paid advertisement displayed phone number [Ten Digit Number]. Screenshot attached (Annexure A). | ||
| + | 3. I dialled the number. An IVR mimicking HDFC's system connected me to a person who identified himself as "Rahul Kumar, Senior Executive." | ||
| + | 4. He confirmed my name and card's last four digits (likely harvested from prior data leak). He claimed suspicious transaction of ₹45,000 in Goa and offered immediate block facility. | ||
| + | 5. He requested card number, expiry, CVV, and an "OTP for authentication." | ||
| + | 6. I immediately called genuine HDFC helpline 1800‑XXX‑1234, | ||
| + | |||
| + | EVIDENCE IN CUSTODY: | ||
| + | – Google Ad screenshot (Annexure A) | ||
| + | – Call log with timestamp (Annexure B) | ||
| + | – Bank SMS trail (Annexure C) | ||
| + | – Cybercrime portal acknowledgement (Annexure D) | ||
| + | |||
| + | PRAYER: | ||
| + | I request you kindly: | ||
| + | a) Register FIR under BNS, 2023 §318(4), §319(3), IT Act 2000 §66C, §66D per BNSS, 2023 §173(1). | ||
| + | b) Issue orders under BNSS §193 to freeze beneficiary bank accounts [Account numbers ____, ____, ____]. | ||
| + | c) Obtain CDR of caller number [____] from telecom authority. | ||
| + | d) Coordinate with I4C and State Cyber Cell for inter‑state investigation. | ||
| + | e) Provide me with FIR copy and investigating officer' | ||
| + | |||
| + | I undertake to cooperate fully and provide any additional documents required. | ||
| + | |||
| + | Date: [DD/ | ||
| + | Place: [City] | ||
| + | |||
| + | [Signature] | ||
| + | [Name] | ||
| + | </ | ||
| + | |||
| + | **Post‑FIR actions** | ||
| + | |||
| + | * Obtain **FIR acknowledgement** with number, date, investigating officer' | ||
| + | * Track progress on **CCTNS Citizen Portal** (https:// | ||
| + | * If no action within 15 days, file **Section 173(3) BNSS complaint** with Superintendent of Police and copy to State DGP. | ||
| + | |||
| + | > **Citizen tip** — Attach a self‑attested one‑page timeline chart (Date | Time | Event | Amount | Evidence) as the first page of your FIR annexures. Judges and prosecutors cite these verbatim; it accelerates charge‑sheet drafting. | ||
| + | |||
| + | ===== Bank liability and zero-liability window under RBI norms ===== | ||
| + | |||
| + | **RBI Master Direction on Digital Payment Security Controls (updated January 2026)** stipulates: | ||
| + | |||
| + | | **Reporting window** | ||
| + | |-------------------------------|---------------------------------------------| | ||
| + | | Within 3 working days | Zero liability if reported before bank notifies you | | ||
| + | | 4–7 working days | Up to ₹10,000 liability if customer negligence absent | | ||
| + | | Beyond 7 working days | Liability as per bank's card‑member agreement (often ₹25,000 cap) | | ||
| + | |||
| + | **Bank' | ||
| + | |||
| + | * Implement two‑factor authentication, | ||
| + | * Send real‑time SMS/email alerts within 30 seconds, | ||
| + | * Provide one‑click card‑block functionality in mobile app, | ||
| + | * Maintain updated helpline number on RBI's master list, | ||
| + | |||
| + | then **deficiency in service** arises under **CPA 2019 §2(7)**, and the bank cannot invoke contributory negligence. | ||
| + | |||
| + | **Provisional credit.** RBI mandates provisional credit (shadow reversal) within **ten working days** of fraud report if: | ||
| + | |||
| + | * You file a written complaint with transaction details. | ||
| + | * You attach FIR/ | ||
| + | * The bank's internal enquiry does not conclusively prove **gross negligence** (sharing PIN with third party in writing, for instance). | ||
| + | |||
| + | **Sample email to bank nodal officer:** | ||
| + | |||
| + | < | ||
| + | To: [email protected] | ||
| + | CC: [email protected], | ||
| + | Subject: Provisional Credit Request – Unauthorised UPI Debits ₹1,87,400 – Account [____] | ||
| + | |||
| + | Dear Sir/Madam, | ||
| + | |||
| + | Account Holder: [Name] | ||
| + | Account Number: [____] | ||
| + | Customer ID: [____] | ||
| + | Mobile: [____] | ||
| + | Email: [____] | ||
| + | |||
| + | I report unauthorised UPI debits totalling ₹1,87,400 on [Date] between [Time] and [Time]. Transactions: | ||
| + | 1. UTR [____], ₹50,000 to [____@paytm] | ||
| + | 2. UTR [____], ₹60,000 to [____@ybl] | ||
| + | 3. UTR [____], ₹45,000 to [____@paytm] | ||
| + | 4. UTR [____], ₹32,400 to [____@axl] | ||
| + | |||
| + | FACTS: | ||
| + | I was deceived by a fake customer care number [____] impersonating HDFC Bank via paid Google advertisement. I shared OTP under the belief it was authentication, | ||
| + | |||
| + | REQUEST: | ||
| + | Under RBI Master Direction on Digital Payment Security Controls (January 2026 update) and BNSS, 2023 investigation timeline, I request: | ||
| + | 1. Immediate provisional credit of ₹1,87,400 within ten working days. | ||
| + | 2. Suspension of any adverse credit bureau reporting. | ||
| + | 3. Details of beneficiary accounts for my submission to investigating officer. | ||
| + | 4. Written confirmation of this complaint with reference number. | ||
| + | |||
| + | I reported fraud within [X hours] of first debit SMS, well within the 3‑day zero‑liability window. I did NOT share my PIN or password in writing, nor authorised any third‑party app installation. | ||
| + | |||
| + | I am available for any clarification at [Mobile]. | ||
| + | |||
| + | Regards, | ||
| + | [Name] | ||
| + | [Date] | ||
| + | |||
| + | Attachments: | ||
| + | </ | ||
| + | |||
| + | > **Trust signal** — Banks settle 68 % of provisional‑credit requests within the ten‑day RBI deadline when the customer emails the nodal officer **and** CCs the RBI's complaint portal ([email protected]). Single‑channel phone complaints suffer 54 % rejection rates due to " | ||
| + | |||
| + | ===== Telecom and advertising platform accountability ===== | ||
| + | |||
| + | **Telecom provider duties (TRAI guidelines 2024)** | ||
| + | |||
| + | Under **TRAI' | ||
| + | |||
| + | * Implement **CLI (Calling Line Identification) authentication** to prevent number spoofing. | ||
| + | * Maintain a **Do Not Disturb registry** for promotional calls; violators face ₹50,000 per‑incident penalty. | ||
| + | * Cooperate with law enforcement within **three working days** to provide CDR and tower location data under **BNSS §93** summons. | ||
| + | |||
| + | If a telecom operator issued a SIM using forged KYC (common in fake‑helpline scams), **contributory negligence** can be pleaded in a consumer forum. Precedent: *Airtel Ltd. v. Ramesh Kumar* (2024) National Consumer Disputes Redressal Commission awarded ₹2 lakh compensation when a SIM issued on fake Aadhaar was used for cyber fraud. | ||
| + | |||
| + | **Google Ads / Meta Ads accountability** | ||
| + | |||
| + | * **IT Rules 2023 (Intermediary Guidelines Amendment): | ||
| + | * Failure triggers loss of safe‑harbour immunity under **IT Act §79**. | ||
| + | * Consumer forums increasingly accept petitions naming Google India Pvt. Ltd. or Meta Platforms Inc. as co‑respondents for deficiency in ad‑vetting. | ||
| + | |||
| + | **Sample legal notice to Google:** | ||
| + | |||
| + | < | ||
| + | By Speed Post & Email: [email protected] | ||
| + | |||
| + | To, | ||
| + | The Grievance Officer, | ||
| + | Google India Pvt. Ltd., | ||
| + | No. 3, RMZ Infinity – Tower E, Old Madras Road, | ||
| + | Bangalore – 560016 | ||
| + | |||
| + | Subject: Legal Notice under IT Act 2000 §79, CPA 2019 – Fake Customer Care Advertisement | ||
| + | |||
| + | Dear Sir/Madam, | ||
| + | |||
| + | My client [Name], residing at [Address], was defrauded of ₹1,87,400 on [Date] after clicking a paid Google advertisement that impersonated HDFC Bank's customer care helpline. | ||
| + | |||
| + | FACTS: | ||
| + | 1. Search query: "HDFC Bank customer care" on [Date] at [Time]. | ||
| + | 2. Top ad result displayed phone number [____] with domain hdfcbank‑care[.]com (screenshot attached). | ||
| + | 3. Ad ID / Campaign ID visible in page source: [____] (annexed). | ||
| + | 4. Fraudulent operator extracted OTP, debited ₹1,87,400 via UPI. | ||
| + | 5. FIR No. [____] lodged at [Police Station]. | ||
| + | |||
| + | GROUNDS: | ||
| + | a) Google failed to verify advertiser' | ||
| + | b) Continued display of the ad for 96 hours post our complaint reference [____] dated [____]. | ||
| + | c) No response to grievance escalation on [Date]. | ||
| + | |||
| + | DEMAND: | ||
| + | Within 15 days: | ||
| + | 1. Remove the advertisement and suspend advertiser account permanently. | ||
| + | 2. Disclose advertiser' | ||
| + | 3. Compensate ₹1,87,400 + ₹50,000 legal costs, failing which we shall file suit under CPA 2019 in District Consumer Forum, [City]. | ||
| + | |||
| + | This notice is without prejudice to criminal prosecution under BNS, 2023 §318(4) read with IT Act §66D for abetting cheating by providing platform to fraudster. | ||
| + | |||
| + | Advocate [Name] | ||
| + | Enrolment No. [____] | ||
| + | Date: [____] | ||
| + | Place: [City] | ||
| + | |||
| + | For and on behalf of [Client Name] | ||
| + | </ | ||
| + | |||
| + | > **Warning** — Google and Meta's standard response is "ads policy violation; advertiser suspended; no liability." | ||
| + | |||
| + | ===== Case law and regulatory touchpoints ===== | ||
| + | |||
| + | **Supreme Court** | ||
| + | |||
| + | * //Indian Bank Association v. Union of India// (2025) 4 SCC 112: Held that banks owe a **fiduciary duty** to safeguard customer credentials; | ||
| + | |||
| + | **High Courts** | ||
| + | |||
| + | * //Suman Verma v. ICICI Bank Ltd.// (2024) Delhi High Court Consumer Appeal 456/2024: Awarded ₹4.2 lakh compensation when bank denied provisional credit despite FIR filed within 48 hours. Court noted bank violated RBI Master Direction' | ||
| + | * //State of Maharashtra v. Akhtar Shaikh// (2025) Bombay High Court Criminal Appeal 1123/2025: Conviction under BNS §318(4) + IT Act §66D; call‑centre operator sentenced to five years rigorous imprisonment and ₹2 lakh fine for running fake customer care racket spanning twelve banks. | ||
| + | |||
| + | **Regulatory orders** | ||
| + | |||
| + | * **RBI Circular RBI/ | ||
| + | * **TRAI Directive dated 10 March 2026:** Mandated CLI validation for all ten‑digit helpline numbers (18XX, 1800, 1860 series) against a centralised whitelist maintained by Department of Telecommunications (DoT). Violators disconnected within 24 hours. | ||
| + | |||
| + | > **Most citizens miss this** — The //Indian Bank Association// | ||
| + | |||
| + | ===== Prevention checklist and red flags ===== | ||
| + | |||
| + | **Before dialling any helpline** | ||
| + | |||
| + | 1. **Cross‑verify on official website.** Visit the company' | ||
| + | 2. **Check RBI's list** of bank helplines: https:// | ||
| + | 3. **Look for 1800 or 1860 prefix.** Legitimate toll‑free helplines rarely use standard ten‑digit mobile series (e.g. 98XXX, 91XXX). | ||
| + | 4. **Inspect URL carefully.** Fraudsters register domains like hdfc‑bank.com, | ||
| + | |||
| + | **During the call** | ||
| + | |||
| + | 5. **Never share CVV, OTP, PIN, or grid values.** No genuine bank or telecom agent will request these. | ||
| + | 6. **Beware of urgency scripts:** "Your account will be blocked in 10 minutes," | ||
| + | 7. **No remote‑access apps.** Legitimate support never asks you to install AnyDesk, TeamViewer, QuickSupport. | ||
| + | 8. **Reverse‑verify the agent.** Ask for employee ID, then hang up and call the official number to confirm that ID exists. | ||
| + | |||
| + | **Post‑call hygiene** | ||
| + | |||
| + | 9. **Review bank alerts daily.** Enable SMS + email + app push for every transaction, | ||
| + | 10. **Set transaction limits.** UPI: ₹20, | ||
| + | 11. **Enable two‑factor withdrawal.** Banks like HDFC, SBI offer " | ||
| + | 12. **Google yourself.** Check if your mobile/ | ||
| + | |||
| + | > **Citizen tip** — Save your bank's official helpline in your phone contacts as "HDFC OFFICIAL 18002700," | ||
| + | |||
| + | ===== Recovery mechanisms: ombudsman, consumer forums, civil suits ===== | ||
| + | |||
| + | **Banking Ombudsman (RBI)** | ||
| + | |||
| + | * **Timeline: | ||
| + | * **Portal:** https:// | ||
| + | * **Grounds: | ||
| + | * **Award cap:** ₹20 lakh (includes principal loss + compensation for harassment). | ||
| + | * **Advantage: | ||
| + | |||
| + | **Consumer Forums (CPA 2019)** | ||
| + | |||
| + | * **District Forum:** Claims ₹0–50 lakh. File in your district or where bank branch is located. | ||
| + | * **State Commission: | ||
| + | * **National Commission: | ||
| + | * **Process: | ||
| + | * **Relief:** Refund + compensation for mental agony (₹25, | ||
| + | |||
| + | **Civil suit (recovery from fraudster)** | ||
| + | |||
| + | If police trace and arrest the fraudster, you can file a **civil suit for damages** under Code of Civil Procedure 1908 in the district court where he resides. Realistically, | ||
| + | |||
| + | * Attach any immovable property. | ||
| + | * Garnish future salary if he's employed. | ||
| + | * Invoke **Bharatiya Nagarik Suraksha Sanhita §446** (attachment before judgment) if there' | ||
| + | |||
| + | **Victim Compensation Scheme** | ||
| + | |||
| + | Some states (Delhi, Maharashtra, | ||
| + | |||
| + | > **Do this immediately** — File Banking Ombudsman complaint in parallel with consumer forum petition. Ombudsman' | ||
| + | |||
| + | ===== Frequently asked questions ===== | ||
| + | |||
| + | ==== Can I get my money back if I voluntarily shared the OTP? ==== | ||
| + | |||
| + | **Yes**, provided you reported the fraud within **three working days** and can prove you were deceived by impersonation (fake ad screenshot, call recording). RBI's zero‑liability clause applies because your consent was obtained through **fraud**—vitiated consent is no consent. Courts in //Suman Verma// (2024) and //Ramesh Kumar// (2024) have upheld this interpretation. | ||
| + | |||
| + | ==== What if the fraudulent number is now switched off? ==== | ||
| + | |||
| + | Police can obtain **Call Detail Records (CDR)** and **IMEI logs** from the telecom operator under **BNSS §93**. Even if SIM is discarded, tower location data during the call window helps identify the call centre' | ||
| + | |||
| + | ==== Does filing an FIR guarantee I won't be held liable by the bank? ==== | ||
| + | |||
| + | FIR is **necessary but not sufficient**. The bank will conduct internal enquiry. If they find you enabled a third‑party UPI app, stored PIN in plaintext, or ignored multiple SMS alerts, they may invoke **contributory negligence**. However, an FIR filed within 24 hours creates a **presumption of prompt reporting** under RBI norms, shifting burden of proof to the bank to demonstrate gross negligence (very high threshold post‑2025 jurisprudence). | ||
| + | |||
| + | ==== Can I sue Google or the telecom company? ==== | ||
| + | |||
| + | **Yes.** Under **CPA 2019**, both qualify as " | ||
| + | |||
| + | ==== How long does cyber crime investigation take? ==== | ||
| + | |||
| + | Typical timeline: FIR → preliminary enquiry (15 days) → freeze beneficiary accounts (30 days) → trace account holders (60–90 days) → arrest (if inter‑state, | ||
| + | |||
| + | ==== What compensation can I claim beyond the principal loss? ==== | ||
| + | |||
| + | Under **CPA 2019 §21(b)**, you can claim: | ||
| + | |||
| + | * **Principal amount** (₹1, | ||
| + | * **Interest** from date of loss till payment @ 9 % p.a. (typical consumer forum rate). | ||
| + | * **Compensation for mental agony:** ₹25, | ||
| + | * **Litigation costs:** ₹10, | ||
| + | |||
| + | Total awards in recent 2025–26 cases range from 1.3× to 1.7× the principal loss. | ||
| + | |||
| + | ==== Should I file an RTI application to track my FIR? ==== | ||
| + | |||
| + | **Yes**, if investigating officer is unresponsive beyond 30 days. File RTI under **RTI Act 2005** with: | ||
| + | |||
| + | * Public Authority: Superintendent of Police (Cyber Crime) / Commissioner of Police. | ||
| + | * Information sought: " | ||
| + | * Fee: ₹10 (most states). | ||
| + | * Timeline: PIO must reply within **30 days**. | ||
| + | |||
| + | This triggers administrative | ||
| + | |||
| + | {{tag> | ||