25.01.2018 Views

white_paper_on_data_protection_in_india_171127_final_v2

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1. It is recognised that the process<strong>in</strong>g of certa<strong>in</strong> types of pers<strong>on</strong>al <strong>data</strong> has a greater<br />

likelihood of caus<strong>in</strong>g harm to the <strong>in</strong>dividual, due to the <strong>in</strong>herent nature of the<br />

<strong>in</strong>formati<strong>on</strong>.<br />

2. The exist<strong>in</strong>g categories of <strong>in</strong>formati<strong>on</strong> def<strong>in</strong>ed as ―sensitive‖ under the SPDI Rules may<br />

be re-exam<strong>in</strong>ed to determ<strong>in</strong>e whether those categories are sufficient or need to be<br />

modified. These categories need to be exam<strong>in</strong>ed keep<strong>in</strong>g <strong>in</strong> m<strong>in</strong>d India‘s unique socioec<strong>on</strong>omic<br />

c<strong>on</strong>text, where <strong>in</strong>dividuals have faced discrim<strong>in</strong>ati<strong>on</strong> and harm due to various<br />

reas<strong>on</strong>s currently not captured <strong>in</strong> the def<strong>in</strong>iti<strong>on</strong>.<br />

3. There may be a need to provide heightened grounds of protecti<strong>on</strong> for the process<strong>in</strong>g of<br />

such types of <strong>data</strong>.<br />

6.5 Questi<strong>on</strong>s<br />

1. What are your views <strong>on</strong> how the process<strong>in</strong>g of sensitive pers<strong>on</strong>al <strong>data</strong> should be d<strong>on</strong>e?<br />

2. Given that countries with<strong>in</strong> the EU have chosen specific categories of ―sensitive<br />

pers<strong>on</strong>al <strong>data</strong>‖, keep<strong>in</strong>g <strong>in</strong> m<strong>in</strong>d their unique socio-ec<strong>on</strong>omic requirements, what<br />

categories of <strong>in</strong>formati<strong>on</strong> should be <strong>in</strong>cluded <strong>in</strong> India‘s <strong>data</strong> protecti<strong>on</strong> law <strong>in</strong> this<br />

category?<br />

3. What additi<strong>on</strong>al safeguards should exist to prevent unlawful process<strong>in</strong>g of sensitive<br />

pers<strong>on</strong>al <strong>data</strong>?<br />

Alternatives:<br />

a. Process<strong>in</strong>g should be prohibited subject to narrow excepti<strong>on</strong>s.<br />

b. Process<strong>in</strong>g should be permitted <strong>on</strong> grounds which are narrower than grounds for<br />

process<strong>in</strong>g all pers<strong>on</strong>al <strong>data</strong>.<br />

c. No general safeguards need to be prescribed. Such safeguards may be<br />

<strong>in</strong>corporated depend<strong>in</strong>g <strong>on</strong> c<strong>on</strong>text of collecti<strong>on</strong>, use and disclosure and possible<br />

harms that might ensue.<br />

d. No specific safeguards need to be prescribed but more str<strong>in</strong>gent punishments can<br />

be provided for <strong>in</strong> case of harm caused by process<strong>in</strong>g of sensitive pers<strong>on</strong>al<br />

<strong>in</strong>formati<strong>on</strong>.<br />

4. Should there be a provisi<strong>on</strong> with<strong>in</strong> the law to have sector specific protecti<strong>on</strong>s for<br />

sensitive <strong>data</strong>, such as a set of rules for handl<strong>in</strong>g health and medical <strong>in</strong>formati<strong>on</strong>,<br />

another for handl<strong>in</strong>g f<strong>in</strong>ancial <strong>in</strong>formati<strong>on</strong> and so <strong>on</strong> to allow c<strong>on</strong>textual determ<strong>in</strong>ati<strong>on</strong><br />

of sensitivity?<br />

5. Are there any alternative views <strong>on</strong> this which have not been discussed above?<br />

116

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!