- 3 years ago
Category
🗞
NewsTranscript
00:00 Hi there, you're with BQ Prime and this is The Fine Print. We are discussing the Digital Personal
00:05 Data Protection Bill 2023 which the government introduced in the Lok Sabha today. What does this
00:11 newest version of the privacy law mean for businesses, citizens of India and all the
00:19 stakeholders in the process? To answer that I have with me Rahul Madan, partner at TriLegal.
00:25 Rahul, welcome to The Fine Print, yet another show where we are discussing whether this latest
00:31 version makes the cut to the ideal privacy law that we want for this country and its citizens.
00:38 Your first high-level assessment of the bill, you've always been an advocate of a principle-based
00:43 law. It sort of largely is along those lines. First, your macro view of the version
00:51 that got people today. So look, I've been waiting for this now for over a decade.
00:57 You've grown old with it, Rahul. I have grown old with it and I'm almost afraid to jinx it but
01:06 this is close to that principle-based framework that I was hoping that we would have.
01:14 I think obviously there are things that I would like to change in this but if you ask me
01:19 for a macro view, I think that this is a good legislation to start with. If we compare it to
01:27 the one that was most recently made public, that is the 2022 draft that we've had the opportunity
01:33 to look at in some detail, it is slightly different from that. So it's not like a huge
01:40 change from that. I think some of the changes are new and I'm a little concerned by some of
01:46 those changes but then if you just look at the macro view, what we want, we wanted something
01:49 simple to start with. We wanted something that would lay down the principles so that a country
01:54 that's just starting on its data protection journey could get used to the new impositions
02:03 on them in a general way and then layer on top of that complexity as we go down and I think this
02:09 gives us a good starting point to do that sort of an approach to building data protection. Just
02:17 such that we're clear, the contradiction, the contradistinction, the other approach that was
02:23 in play was going straight to a GDPR style framework which is very compliance heavy
02:29 and I've long maintained that I think that would be difficult for us to do at the current stage of
02:36 our evolution in data protection. So from that perspective, I'm actually quite happy with the law.
02:42 Okay, I don't want to do a spot the difference kind of thing conversation with you between 2022
02:47 and this version but I do want to use that as a reference point to understand some of the changes
02:53 that have now come in. The one sort of big furor was against the language which said that in some
03:00 cases from consumers point of view, it would have been a deemed consent scenario
03:07 where you have voluntarily given information and the data fiduciary or the person you're giving
03:12 or entity you're sharing that data with will then use it because you have voluntarily shared it
03:19 with that entity. In some of the examples, if I can point out, you've called a real estate broker,
03:25 you want a PG accommodation. Now when that broker then calls you back, you can't
03:31 or that broker that firm calls you back, you can't say you violated my data. Now that
03:36 deemed consent as you read it is not something that is being done away with, it's just been sort
03:42 of reworded or rebranded as legitimate purpose. Can you help us understand, I mean, what the
03:48 implications of this change language are? Yeah, look, I mean, I think when we saw deemed consent
03:55 in the previous draft, we were a little concerned because it felt like there was like a violation
04:01 being done on our autonomy because we haven't consented but someone has deemed that we have
04:06 consented, feels terrible. It feels like someone is doing for us something which we should have
04:12 done ourselves and if you actually read the provisions under deemed consent, you read the
04:17 provisions of the law under that heading, that was not what it was doing and so I think the problem
04:24 in the last draft was really with the title and I think that it was an unfortunate choice of words
04:30 and I think they've rectified that by moving to something called legitimate uses. Now the concept
04:37 of legitimate grounds of processing is a well-understood concept around the world. It
04:42 essentially says that there are many grounds for processing, consent is one of those grounds,
04:46 another one of those grounds is a legitimate ground for processing and it essentially says
04:50 that when there is a legitimate interest to process the information that you should be
04:56 allowed to do that. A classic example is that if you are being carried into an outpatient department
05:03 like after an accident, they may want to actually legitimately process your information, see what
05:09 your allergies are and things like this to make sure that they don't give you a medicine that
05:13 would actually kill you and sort of save you and that's the classic definition of legitimate grounds
05:18 of processing and I think that's what they intended. Now the example that you gave
05:22 which is that if there's a real estate broker to whom you've provided your information and that
05:28 person calls you back to tell you, look you wanted a house and there is a house available.
05:33 I think the provision has now been changed to say that in those circumstances you can't go and sue
05:42 the real estate broker for using your number to contact you because you gave it to him in the
05:47 first place for this purpose and so that is what 7.1 has 7.1a has now been restricted to say that
05:53 look if you have provided your purpose your information voluntarily and for a specified
05:59 purpose and they process that information for that specified purpose then you don't have a grounds to
06:05 say you didn't get my consent, you didn't show me the notice, all of those other things. So it is a
06:09 fairly narrow interpretation compared to the GDPR interpretation of legitimate grounds of processing
06:14 but it actually is intended to deal with those situations like for instance the other example
06:21 illustration they give is that you go to a restaurant and you say you book a make a
06:26 reservation at a restaurant and say that when the reservation opens up please give me a call
06:30 and if the guy does call you when the reservation opens up you can't sue him to say why did you call
06:36 me because you gave me the number to call you, I've done it for the specified purpose and you
06:40 voluntarily provided the information. I didn't do the whole privacy policy and consent and all
06:45 of those things but I shouldn't be punished for doing and I think that's the intention
06:50 there and I think there's no mention of this concept of being consent which makes it a lot
06:55 less icky. I think all of us really felt violated because someone was consenting
07:01 on our behalf and that's not there anymore. So one is where situations and we discussed
07:06 this offline where I've shared the information and for a legitimate purpose that information is
07:11 getting used but what you and I probably can safely say you and I both are plagued by in today's
07:17 environment is places where I've never done business, places where I've never given my
07:23 personal information and those entities then sort of calling me and as they're broadly called
07:29 I'm called to offer services goods etc etc. Now is there anything in this law that says that I
07:36 as a consumer when I'm very sure that I have not shared my information with a bakery, I have never
07:43 dealt with that bakery and that bakery is sending me now marketing messages or a particular financial
07:48 institution. Can I go to the previous redressal mechanism of this entity and ask them where did
07:55 you get my information and fail and if they fail to give me a legitimate answer I can take it up
08:01 with the data protection board? A simple answer is yes. And what are the sort of consequences of
08:10 that might follow? All the consequences that follow through. I mean I'm sorry to
08:15 like this simple answer yes but that's exactly what it is. I want a simple answer for this.
08:20 Because it's very simple right now you can you have to when you process personal data
08:27 you have to process personal data for a specified purpose, you're not allowed to process it for
08:31 anything other than a specified purpose. You can't contract out of it by saying that look
08:36 you waive your right to only be limited by the specified purpose. So there's many
08:42 belts and braces in this law more than the previous the 2022 version as well which is doubling down on
08:47 this principle that you must define the specific purpose for which you're collecting data
08:53 and you can only process data for that specified purpose. And then there's another provision which
08:58 says that you know it is the onus is on you to show if someone is questioning why you have reached
09:05 out to them to show that you have actually provided notice and got consent in order to allow you to
09:11 question to reach out to that person. So your bakery for example, if the bakery is reaching out
09:16 to you and you say why are you reaching out to me the onus is on the bakery to say look you actually
09:21 were given notice that this is what I will process this information for and you consented and it's
09:26 only then that the bakery will be able to win in the data protection board or in any grievance
09:32 regression process where they are challenged. And so I think that is very very clear in this law
09:39 and what does this mean I think we must always look to what does this mean to our daily lives.
09:45 We all know that we are constantly being called by various telemarketers to say you know can I
09:51 sell you this plan etc. Everyone is going to have to rethink the way they do telemarketing.
09:56 They're going to need to clearly maintain a record of the consent that's provided and the specific
10:04 purpose for which it was the consent was provided to make sure that when they call this person if
10:10 they are questioned they actually have a paper trail to say yes I have I can legitimately call
10:15 you. A lot of businesses today rely on these sorts of cold calls. I think a lot of those
10:22 business almost all of those businesses are going to have to shut down because I don't see any way
10:26 in which they can function when they are buying lists of you know just lists of phone numbers and
10:33 just randomly calling through those lists there's no way that they can establish these things that
10:37 the law now requires them to establish. Okay that's very heartening though and sort of encouraging to
10:44 hear that as citizens you know the law is actually doing something for us. Let me now come to some of
10:51 the obligations that your clients will have to sort of now look at more closely and in that there
10:58 are an extensive list of obligations for data fiduciaries. Do you want to flag some of the
11:04 important ones that businesses companies will now need to prepare for? I think we went through one
11:12 and I think the first one really is this whole sort of chain when you're now using
11:18 data you've got to have in place the processes and the mechanisms to make sure that you can process
11:25 the data in the way that you're doing with regard to a particular individual. Now that's actually
11:29 not an inconsiderable lift because right now we don't have any of those processes in place and
11:35 when I advise my clients I very often tell them look these are the types of things that you're
11:38 going to have to change when you do this. There is now an obligation to provide the notice and
11:46 consent in all the languages in the HLU. When I say now it was there in the previous version as well
11:51 but the point is that when this law comes into force the moment it comes into force anyone can
11:55 come to you and say you need to give this to me in a language one of the languages of the HLU
12:01 and if you can't do that then you're in violation of this law. So companies are going to have to
12:05 start now putting in place these mechanisms to have these translations in place so that everyone
12:12 can understand what is being done with their data. I think that there are these sorts of
12:21 additional steps that companies need to take in their internal organization. They're going to
12:28 need to have to set up data protection office, they're going to have to set up grievance reversal
12:33 mechanisms. These are the sorts of things that certain types of companies absolutely
12:38 mandatorily have to do but it is a new lift. So I think a lot of people keep saying that
12:46 we comply with GDPR and so we are okay with all of these things but I think there are many new
12:52 ways in India is requiring companies to operate that they are going to have to look at.
12:58 There's another, I'm going to say strange provision we mentioned it earlier which is
13:04 that you cannot contract out of the obligations in the act. Now what does that mean for companies?
13:11 They're going to have to look at their privacy policies and they're going to have to look to
13:15 see if there's something that they have put into the privacy policy as something that they wanted
13:19 in order to be able to perform some of their services and see if that complies with the
13:24 provisions of the law because if it doesn't comply with the provisions of the law putting it in the
13:28 privacy policy is irrelevant because it is invalidated the moment the law comes into force.
13:32 Now these are things that in many ways go against the way in which companies think
13:38 right now. The companies think that look there is an obligation but if you and I contractually agree
13:43 that we will do such and such the fact that the obligation exists doesn't matter because we've
13:48 had a private contract in order to get out of that provision of the law but this legislation
13:52 actually says you cannot do it. I think one of the examples that and correct me if I'm wrong
13:58 that this bill gives us that if I waive my right to complain to a data protection board
14:04 if that provision will fall through and will be frowned upon. Exactly, so you can't say that
14:11 I agree that if there's a dispute between us I will not go to the data protection
14:17 I mean you can say that if you want but it makes no difference because they can still go to the
14:20 data protection board. Now that's it seems like a silly thing to say but there are many
14:25 other subtle things that companies today are doing that they're saying we agree
14:30 that this will not apply, you can't do that and I think that's a real wake-up call
14:35 for companies. I would say that companies will have to take out their privacy policies and whatever
14:41 their grounds of processing are today and look at everything that they've got in those privacy
14:46 policies compare it to what the provision of the law says and see whether they can continue to keep
14:50 it or not because a lot of their internal business processes not just the
14:57 data protection related things but just other business processes depend on these things and if
15:02 they want to rely on it they're going to need to know that at some point in time if someone complains
15:07 then they are not going to be able to follow this thing that's in the contract they have to go by
15:10 what's in the law. Also I think in our offline conversation you mentioned the erasure
15:16 requirement now that was also sort of concerning for you. Yeah so there's always been an erasure
15:23 provision and that's there in sort of every data protection law which essentially... And also
15:28 that purpose has been met kind of condition to be sort of met right before when you say that
15:35 I collected your data now the purpose of that data is being served and now I have to delete it.
15:42 Yeah so I mean I think that's sort of the way in which it always applies let's say you've
15:47 collected my data let's go back to that real estate example the real estate broker collected
15:53 my personal data in order to find me a house found me a house and now I have the ability to go to
15:59 that real estate broker and say please now delete my information because the purpose has been served
16:04 now don't hold this information for me and at some later point in time try and upsell me another
16:07 house that's not the purpose you have to delete it but there is a further nuance to this in this law
16:12 which is essentially something like an automatic erasure that after a certain period of time
16:19 that you are required to delete this information if the data principle has not come back to you
16:27 and used it like let me just let's take for example I'm on some social media app and I'm
16:34 creating videos and then I stopped creating videos you know I grew up and I didn't want to create
16:39 these videos anymore and then 12 months passes and I haven't created a video for 12 months and
16:44 let's say that the period of time is 12 months of inaction now the company has to go back and say
16:51 look whatever data was being collected as a result of this whatever permissions I got from you to use
16:58 your camera and to use your microphone I now have to basically I have to stop that provision or
17:07 if there's data that I've collected which is in relation to providing you a particular feature
17:12 you haven't availed that feature for 12 months I now have to delete all that information
17:18 this is I love it I mean quite frankly if you ask me this is operationalizing what
17:27 is the implicit meaning in what we've said right because essentially don't hold data for longer
17:32 than it is required what is happening in India now it's setting a stopwatch and companies big
17:38 and small and I think the big companies as always will be able to deal with the problem
17:41 the small companies going to be an extraordinary leader because they're going to now have to
17:45 think about creating some process by which they start counting from the last activity
17:52 and then 12 months after that last activity and I'm making this up it could be 12 months ago 12
17:58 years I don't know what it is but there is some period of time after which they have to now start
18:02 going back and deleting one day at a time data that was created 12 months ago and that's not
18:09 it's a non-trivial thing to do when you're engineering a system. Yeah I want to sort of
18:17 now come to another provision which you know is the rationale of it is a little difficult to gauge
18:26 which is that the government wants to on the basis of recommendations of the data protection board
18:32 can now block access to information websites etc. Now the information technology act already
18:41 gives the government this power we have you know I can name it twitter fighting it in Karnataka
18:48 high court that has creeped into this sort of bill as well how concerned should we be about this.
18:57 Yeah look I mean I find that provision the most inexplicable in this draft it was not there in
19:02 any previous draft it's never been discussed it's also very broad and in its breadth is not limited
19:10 to personal data it just is you know access to deny access to any computer resource that is
19:22 generating or has stored any information so it doesn't restrict it to personal information.
19:28 So it seems completely out of place in a law like in a law that is supposed to protect personal
19:35 data. So I'm in my head trying to figure out what could have been the intention and just to be
19:41 charitable I would imagine that one possible mischief that it was intended to sort out was
19:49 if someone has created a website and they are publishing personal information without consent.
19:55 Certainly I think the government needs to shut that down and so a blocking order to such a website
20:03 where it is publishing in a in sort of a public access kind of a way personal information
20:09 of one or many citizens of the country there should be a right to shut that down.
20:17 But I don't think that's what this is saying maybe that was the intention but this is much
20:22 much broader and this sounds like just a general blocking provision. So one for me it is out of
20:28 place in this law this is a law to protect personal data if you look at the statements
20:32 of objects and reasons I went through all of that and I could find no way in which
20:35 this particular provision could be squeezed into that framework. Second we've actually got other
20:42 provisions of law that address this mischief and so to have the same remedy in multiple
20:49 legislations is actually not good for the country. It creates uncertainty it's not it doesn't
20:54 contribute to the ease of business. I don't know from which side I'm going to be slapped
20:58 if I get a blocking order under the IT Act or the new digital India Act when it comes.
21:05 I don't know if tomorrow I'll get another blocking order from this act and that's really not the
21:11 correct way to operate when you're looking for ease of business. So I would say that would be my
21:17 big concern with this. The practical difficulty or rather the remedy that now the government
21:25 has given itself even under privacy law to block access to some of the information and what I find
21:31 interesting here is that there were news about government institutions
21:37 publishing or rather their sites having passport details, Aadhaar details of citizens
21:44 but interestingly this version of the bill says that the government and its agencies
21:51 are exempt from prosecution under the law.
21:53 I mean I don't think it says exempt from prosecution I think it says there are certain
21:59 grounds under which they could exempt. Good faith right now good faith is like a very motherhood
22:05 sort of word in that sense. A lot of our legislations are apple pie and motherhood so
22:10 we have to basically, the point on the exemption is
22:17 look I think there are some of those provisions are completely legitimate. So in order to
22:22 process, if you have to process information in order to pursue a legal claim or if there's like a
22:29 statutory authority that's required to enforce a law, you can't now prevent that statutory
22:34 authority from enforcing the law because they are processing personal information. There are a whole
22:38 bunch of things which are completely legitimate but I think subsection two is a
22:44 little broader. Now the breadth of that refers to all those things that we see from the
22:50 constitution down which is integrity of the country, security, public order, all of those
22:56 sorts of things. It's not uncommon for those sorts of provisions to be put in legislations
23:02 just as it's not uncommon for legislations to be struck down because they have those provisions and
23:07 then they've been used in a completely arbitrary manner. So I think what we're going to need to do,
23:12 I don't think these provisions will be struck down as is but everyone needs to abide by the
23:19 Puttaswamy test, the test in the nine judge privacy bench and so we'll have to see how
23:24 these things are implemented. I think at this point in time just having that provision there is not,
23:30 the mischief has not yet happened but we could see where the mischief happens, how it happens etc.
23:35 Yeah, I mean you would think that a law that has taken such a long road of consultative process,
23:42 these surprises or these googly's will not come in the version that's about to become law
23:47 but one could only hope. Two final sort of points or aspects that I want to discuss with you,
23:54 both of which I think you're sort of largely happy with that the data protection board will
24:01 work as a digital office and so will the appellate forums and the sort of consent manager
24:06 entity that was there in the earlier version as well but now it's been recognized
24:11 in some fashion in terms of registration etc. Yeah look I mean I really like the digital office
24:17 thing. I've been saying for a long time that one of the ways in which we can unclog, uncongest
24:23 our dispute resolution process is really with these sorts of innovations. I've written in the
24:27 past about online dispute resolution. I've written on numerous occasions on using a technolegal
24:33 approach. So all of that is actually mentioned up front and center. They've actually used the
24:38 word technolegal in the law. This is the first time I'm seeing that in a draft law. So I'm really
24:45 happy with that and I'm saying this because you know just because we're talking about data, we're
24:50 talking about personal data, the volume and velocity of information is going to be of such a high
24:55 magnitude that there is quite frankly no other way to do this. You have to create digital offices
25:01 to run and the interesting thing is even the appellate board. What does that mean to create a digital
25:05 office that everything happens digitally? Look I mean quite frankly I'm really curious to see what
25:10 the data protection board does with this because they have a blank canvas. If I was
25:16 architecting some of these things, I would just go wild with all the things that we could
25:20 do. We could just have completely non-oral hearings. Why do people need
25:27 to win a case because their advocacy is good? It's not required in today's day and age. Why don't
25:32 we just submit briefs, have everything go asynchronously by paper and find the
25:39 resolve the dispute also just in writing. We can scale that really efficiently.
25:45 These are all digital systems and so evidence no longer needs to be
25:51 adduced in the traditional way in which evidence is reduced. We can just go into the innards of
25:56 the system and figure out from the system itself what the evidence is as to who did what. Why can't
26:00 we think in that manner? So I keep saying that look we have to allow for this to happen.
26:07 When we allow for this to happen, believe you me, there are going to be innovations in evidence, in
26:13 this dispute resolution that will blow your mind. I'm really glad to see that we've made a start
26:19 here. Of course, what would be the worst of all worlds is if we have a digital office but the
26:24 person who's running the digital office decides to do it completely in the way that we've done
26:28 it for the last century. That would be very unfortunate but I'm hopeful that we've
26:33 got an option to do something good. Then on consent manager, of course, we're now
26:39 reaching the end of India's G20 presidency and you and I have spoken about digital public
26:45 infrastructure a lot. So the consent manager and all of these frameworks are very much integral to
26:51 that conceptualization. Of course, we've had the reference to the consent manager from almost the
26:57 very first Srikrishna draft but they've always referred to the consent manager as a type of data
27:02 fiduciary. Now I see them almost putting the consent manager as a separate institutional
27:07 entity in the whole framework. I think that actually gives it some credence and credibility.
27:13 It's also now the consent manager is not just anyone standing up and saying, "Look, I want to
27:18 be a consent manager and manage your consent." You need to be registered with the Data Protection
27:22 Board so it's giving it some sort of imprimatur, as it were, of a supervisory regulatory authority,
27:28 which is also making it a little more serious. I like all of these kinds of innovations that we're
27:33 seeing in this draft. All right, Rahul Mathew, we'll leave it here. Always a pleasure to get
27:41 insights from you on the progress that we are making or not on privacy law in this country.
27:47 Thank you very much for joining us with your initial thoughts and in the weeks to come,
27:51 as we examine the fine print of this bill more, we'll keep coming to you with expert insights.
27:58 Thank you so much for joining us here on The Fine Print. Thank you. My pleasure as always.
28:05 [MUSIC]
28:15 [BLANK_AUDIO]