The recent decision by the Election Commission (EC) to withhold the technical specifications—specifically the name and version—of the software utilized during the Special Intensive Revision (SIR) of electoral rolls has ignited a debate over the boundaries of administrative transparency. By invoking exemptions under the Right to Information (RTI) Act related to trade secrets, intellectual property rights, and commercial confidence, the poll body has effectively shielded its digital infrastructure from public scrutiny.
The Intersection of Technology and Governance
The controversy stems from an RTI application filed by activist M.A. Mujeeb Ayyub, which sought clarity on whether artificial intelligence (AI), machine learning, or automated predictive analytics were employed to flag anomalies in voter records. While the EC maintained that no new software was procured specifically for this exercise and that Electoral Registration Officers retain final decision-making authority, the refusal to disclose the underlying technological framework mirrors past stances taken by entities like Bharat Electronics Ltd and Electronics Corporation of India Ltd regarding EVM source codes.
Fiscal and Compliance Implications
From a fiscal governance perspective, the use of proprietary software in public sector operations necessitates a rigorous audit of public outlay. When government bodies utilize third-party commercial software, the procurement process must align with stringent statutory filing requirements to ensure that public funds are not being misallocated through non-transparent vendor contracts. The classification of such software as a ‘trade secret’ introduces a layer of complexity for auditors attempting to verify whether the value derived from these digital tools justifies the associated tax and service expenditures.
Furthermore, the reliance on automated systems for massive administrative tasks like voter-roll management brings the issue of GST compliance in the app economy to the fore. If the EC or its associated contractors are providing software-as-a-service (SaaS) or maintenance support, the tax treatment must be clearly delineated. The ambiguity surrounding the intellectual property rights of the software used by constitutional bodies can complicate the tax audit trail, particularly when distinguishing between off-the-shelf software and customized, high-value developments that attract specific indirect tax liabilities.
The Burden of Transparency
The EC’s assertion that specific queries regarding automated decision-support systems do not qualify as ‘information’ under Section 2(f) of the RTI Act highlights a recurring tension between proprietary digital assets and the public’s right to verify the integrity of democratic processes. As public institutions increasingly integrate sophisticated analytics, the demand for fiscal and compliance transparency will only grow. Without a standardized framework for the auditability of state-utilized software, the conflict between protecting trade secrets and ensuring institutional accountability is likely to persist, potentially impacting future procurement strategies and the scrutiny of government-led digital initiatives.
Frequently Asked Questions
The EC cited commercial confidence, trade secrets, and intellectual property rights exemptions under the Right to Information (RTI) Act.
No, the EC stated that no new software had been developed or procured for the SIR exercise.
Electoral Registration Officers (EROs) decide whether to include or exclude an elector based on facts and records.
The applicant sought to identify the software, application, algorithm, or AI platform used to detect errors and whether these systems automatically flagged records for deletion.
The EC stated that queries regarding the workflow followed after records were flagged sought a clarification that does not qualify as information under Section 2(f) of the RTI Act.
Yes, Bharat Electronics Ltd and Electronics Corporation of India Ltd have previously declined to share EVM source codes in response to RTI queries.
