During the period between 27th October 2009 to 15th February 2020, according to data available on the E-courts website, 1988 cases registered included a charge under section 66A of the Information Technology Act, 2000 ( as amended in 2008). Of the above cases, 1189 cases were tagged as disposed of by the E-courts website. However, only 19.8% of the disposed of cases have a judgement uploaded in the case file, as available via the E-courts website.
Due to the non - availability of judgements:
The Information Technology Act, 2000 ( as amended) lists offences in Chapter XI. Even considering the explanatory provisions, there's a total of 30 provisions. On the other hand, looking at the data mined from the E-Courts, there are more than 1000 variations of Section fields listed under the IT act. That is at least 970 provisions more than those in the Act.
On further evaluation of the data mined, we surmise that there is a possible problem with the translation of documents from vernacular languages. For example, while 66क may mean 66c it may be translated as 66k, a provision which does not exist in the IT act. Another issue with translation is observed with the typecase. In some instances, क is translated to c/k while in others to C/K. This problem is also similarly observed for 66A where अ/ ए maybe a/A.
According to a Google Translate search:
अ = a
ए = A
However, during a manual validation process, we came across cases where अ has been used to refer to A.
In Hindi, according to a Google Translate search, both a and A are ए.
A lack of judgements means that there are very few cases where the usage can be correctly ascertained.
The lack of standardisation also extends to Act names, for example:
|66A||Information Technology Act|
|66A||INFORMATION TECHNOLOGY ACT, 2000|
|66A||Information Technology Act, 2000|
|66A||INFORMATION TECHNOLOGY ACT 2000|
|66A||IT (Information Technology) Act|
|66A||Information Technology Act 2000|
|66A||INFORMATION TECHNOLOGY ACT 2008|
These issues make monitoring and evaluation difficult as, to monitor all cases under the provision, one would have to foresee every possible combination of writing the Act and Section search for every such combination.
In one instance we observed a case available on the E-courts website which was not available via the API. Manual verification across all states to test this particular error was not carried out due to time constraints.