Naavi.org

The DPDPA 2023 has completely changed the outlook of the industry in the Use and Management of Data. So far, like every other business entity that has adopted itself to the “Data Driven” business strategy, the industry was concerned only with “Information Security” or “Cyber Security”, preventing Cyber criminals access data in their custody and commit frauds.

In late 2018, J W Marriot chain had “become aware” of a data breach of its reservation system which had actually happened in 2014 in the network inherited from “Starwood” hotels which had been purchased by the Marriott in 2016. Over 500 million guest data with credit card and passport details had been accessed by hackers. Investigations revealed that one of the Competing bidders for the takeover of Starwood could have been responsible for the breach. The involvement of the Chinese Military was also traced. It was therefore a business rivalry and foreign state sponsored attack. This was considered an “Information Security Issue” and the damage to individuals was collateral.

However in terms of the damage to the Company, the penalty imposed by the UK ICO was more than $120 million under GDPR and was much more than the direct loss suffered most of which was covered by the Cyber Insurance.

The Insurance industry is deeply divided on whether the administrative penalties can be covered by Insurance and in the instant case J W Marriott did not contest the fine and it is reported that it ultimately settled the penalty at around $52 million.

Indian Hospitality industry so far was not much concerned about such data breaches since the industry was protected by weak enforcement and weaker judicial system in India.

The the current law of ITA 2000 required an affected party to claim damages for it to be liable for such data breaches but the “Valuation” of personal data for claiming damages continues to be a grey area and it would require decades of litigation for a PIL to materialize (eg: Bhopal Gas Tragedy case). Hence industry was taking it easy. Most large hotel chains today have lakhs of personal data including Aadhaar data, PAN data, Driving license data etc and they are retained for decades.

Now with DPDPA 2023 coming into force, the “Risk of DPDPA Non Compliance” hangs over the heads of all the members of the hospitality industry though to the limited extent of around Rs 250 Crores to say around Rs 500 crores if multiple breaches or non compliance is recorded.

Under DPDPA 2023, the Hospitality industry players will be given a new responsibility as “Data fiduciaries” and responsible for the protection of the “Privacy Rights” of their customers.

Industry should therefore wake up and start taking steps to mitigate the DPDPA non compliance Risk.

After shedding the complacency and deciding to secure the personal information under their custody, the industry should not fall into the second trap of complacency that they are secured by being certified for ISO 27001 or GDPR. They need to look for Certification under the India specific Compliance frameworks such as DGPSI.

In this context it is timely that ETCISO is hosting an event on 18th February 2025 at 4.00 pm to 6.00 pm in Bengaluru (Park Hotel).

Naavi

Data Fiduciaries who are deploying AI products for Personal Data Processing needs to take note that DPDPA Rule (no 12) expects that

“(3) A Significant Data Fiduciary shall observe due diligence to verify that algorithmic software deployed by it for hosting, display, uploading, modification, publishing, transmission, storage, updating or sharing of personal data processed by it are not likely to pose a risk to the rights of Data Principals.”

While some data fiduciaries may find comfort that this only relates to “Significant Data Fiduciaries” and not others, the determination of which data fiduciary is a “Significant Data Fiduciary” may itself may require an assessment of the “Sensitivity” of processing and the harm likely to be caused to the data principal.

The Officer of MeitY designated for this purpose may declare certain classes of data fiduciaries or specific data fiduciaries as “Significant Data Fiduciary”. However if any data fiduciary thinks that if the designated official has not declared a specific category of data fiduciaries as “Significant Data Fiduciaries”, they may not be fully correct.

The need to make an assessment of the Risk of processing still lies with the data fiduciary since he is a “Fiduciary” and not a “Controller”. It is the responsibility of every data fiduciary to do a self evaluation of his processes and document why he is not a significant data fiduciary.

In this context, deployers of AI will have a unique challenge. In case they are using an Open Source AI, it is their responsibility to understand the risk and declare if there is a high risk to a data principal. If however they are unaware of the code of the algorithm then they need to depend on the provider of the algorithm.

Due diligence in this regard means that the data fiduciary obtains an assurance along with indemnity and include it in the contract. Alternatively the provider should be declared as a “Joint Data Fiduciary” so that the responsibility of compliance will be on the provider also.

In the context of proprietary algorithms, the deployer being unaware of how the algorithm processes the personal data, the risk is not quantifiable. In such a case any data fiduciary should presume that the “Unknown Risk” could be high risk and therefore the process renders them as “Significant Data Fiduciary”.

In other words “Deployers of all Proprietary AI algorithms need to be automatically tagged as “Significant Data Fiduciaries”. If use of AI is ubiquitous, then a large number of Data Fiduciaries will be Significant Data Fiduciaries.

Naavi

As expected, MeitY has yielded to the pressure from the industry and granted extension for submission of comments on DPDPA Rules from February 18 to march 5.

It is reported that by this time more than 10000 comments have already been submitted and this extension may swell it further . Hope this will not delay the finalization further.

Naavi

DPDPA 2023 is a special law for protecting the “Privacy” of individuals in the digital space. It works closely with ITA 2000 in terms of Sections 43, 46 (Adjudication), 72A (Processors), 67C (Retention) and several other sections where “Personal Data” is the subject matter of law.

Additionally the Consumer Protection Act had also imposed certain responsibilities on the use of “Dark Patterns” by Data Fiduciaries making it a criminal offence in certain contexts.

Now TRAI has also amended the Telecom Commercial Communications Customer Preference Regulations (TCCCPR) 2018 to include certain guidelines which incidentally will be considered as “Due Diligence”/”Reasonable Security Safeguards” under DPDPA 2023.

One of the main concerns of the data principals is the unregulated spamming by way of telephone and SMS messaging by different operators. In the Singapore PDPPA 2012, a separate chapter is devoted for handling obligations related to “Do Not Call Registry “.

In India the DND registry has been in place for some time but the consumers had continued to get spam calls until recently when it has shown a decline. Now the recent amendments will further bring the spamming from Telecom companies under control.

Some time back TRAI wanted the display of the name of the caller based on the SIM registration data. But this seems to have been opposed and TRAI is now trying to introduce identifiers to the call numbers and messages so that recipients can distinguish the calls from the number itself.

It is now proposed that the messages would be distinguished by prefixes such as P for Promotional, S for Service, T for transactional and G for Government. For calls, the 140 series will be used for promotional calls, while the 1600 series is allocated for transactional and service calls, allowing recipients to easily identify the nature of the communication.

All senders and telemarketers must undergo physical verification, biometric authentication and mobile numbers linking to enhance security. There is a need to ensure that complaint filing mechanism is simplified and Operators maintain detailed records of complaints and sender information for quick identification of violators.

The telecom operators need to also monitor the call and SMS patterns to identify unusual activity such as high call volumes and short call durations which may signal spam. Operators also need to deploy honeypots to monitor emerging spam trends.

As regards consent requests, if a customer opts out of promotional messages, senders are prohibited from seeking consent once again for 90 days. Further, consent for an ongoing transaction will have a validity limitation of 7 days.

These regulations may be considered necessary due diligence for DPDPA Compliance in the Telecom companies.

The penalties may also be increased with Rs 2 lakhs for first violation, 5 lakhs for second and Rs 10 lakhs for subsequent violations when there is mis reporting of Unsolicited Commercial Communications. (UCC). Repeat offenders may face suspension of all telecom resources with a 15 day suspension to start with and black listing for subsequent violations.

When the spamming is undertaken by any other company such as the Banks, Stock brokers or Insurance agencies since the telemarketing facility is under the regulation of TRAI, the penalties envisaged above may also be made applicable on them though they may come under different sectoral regulators for their operations.

There is one issue however that if there is a penalty imposed under TRAI act for spamming , DPB may not be able to impose its penalties in the same context as it would become “double jeopardy”. When such complaints are received by DPB, it may exercise the option to direct the complaints to the sectoral regulators to the extent possible.

We suppose that these changes could reduce some of the spamming by the Telecom Companies.

Naavi

In a move which should be very useful in fortifying the security of Bank domains, RBI is expected to launch a new TLD bank.in from April 2025.

RBI is also introducing another TLD fin.in to cater to the requirements of the financial sector.

Ref: Times of India

Naavi.org had been one of the first to flag the “Data Laundering” of sensitive personal information that happened through CIBIL transferring its share holding from Indian Banks to Trans Union.

I draw attention to the article “CBI Enquiry is required for finding the truth behind TransUnion taking over CIBIL” . I urge all of you to read this article once again along with the linked earlier articles.

In December 2024, Mr Karti Chidambaram raised the issue of CIBIL scores in the Parliament.

In May 2024, a PIL had been filed in the case of Surya Prakash V Union of India and Others for which the Supreme Court appointed an amicus curie Advocate K Parameshwar

(Refer: W.P.(C) No. 000310 – / 2024 Registered on 07-05-2024: Diary no: 23982/2023; SCIN010239822023)

The petitioner alleges that the Credit Information Companies in collusion with RBI had violated the Data Localisation principle.

It appears that the case is now due for further hearing on 17th February 2025 after the report of the amicus curie and we need to see how the Supreme Court reacts to this sensitive case.

With the current environment of DPDPA 2023, the decision of the Court will assume further significance.

Naavi

P.S: Next hearing on 25th March 2025