Kerala’s draft State Data Policy 2026 marks a shift from treating government data as information held separately by departments to treating it as an administrative resource that can be catalogued, exchanged and, in some cases, accessed by private entities for a fee. The policy has received in-principle approval and proposes a common framework for classifying, sharing, accessing, storing, retaining and using data held by government institutions.
The proposed framework is important because it does not simply announce a data-sharing platform. It sets out an institutional system around that platform: departments will have to appoint chief data officers, establish data management cells, prepare inventories of datasets and identify categories that cannot be shared. An apex-level committee chaired by the chief secretary and a state-level committee chaired by the information technology department secretary will oversee the process.
Under the draft, startups, industries and other private entities could obtain government data classified as “internal” by paying a fee and securing the approval of the apex committee. Departments would exchange data with one another without charge. The fees collected from private access are intended to cover the government’s costs of gathering and maintaining the data, according to the department order reported by the Times of India.
The distinction between internal data and protected data is central to how the proposed system would work. Personal, confidential and restricted datasets are barred from sale or sharing. The policy also requires departments to prepare “negative lists” identifying categories of data that must be excluded from sharing. These lists are to be drafted within six months, reviewed by the state-level committee and then submitted to the apex committee for final approval.
This arrangement places classification at the centre of data governance. The proposed exchange will not automatically make every government dataset available. Instead, access will depend on how a department classifies the information, whether it appears on an exclusion list, the approval process and the eventual financial and technical rules governing the platform.
That institutional design reflects a practical problem in government data systems: information is often generated by individual departments for specific administrative purposes, while its wider usefulness depends on standardised formats, clear ownership and controlled access. Kerala’s draft attempts to address that problem by requiring every department to create a dataset inventory register and designate officials responsible for data management.
The policy was prepared by the Kerala State IT Mission after feedback was sought from government departments and the public. The proposed state data exchange platform had already received administrative sanction in July 2025. KSITM has been assigned the technical coordination role and has been asked to prepare detailed cost estimates for different data-retention periods.
The retention question is more consequential than it may initially appear. Data access is not governed only by who can view a dataset. It also depends on how long the information remains online, how it is stored, when it is removed and who is accountable for maintaining it. The apex committee is expected to decide the platform’s financial framework and the period for which data can be retained online. The available details do not establish the final retention periods or the fees that private users would pay.
The draft therefore combines two objectives that can sometimes pull in different directions. The first is to make public data more usable for startups, industries and other private players. The second is to prevent sensitive information from entering a wider circulation without adequate control. Whether those objectives can coexist will depend on the quality of classification, the clarity of the negative lists and the ability of committees to enforce their decisions across departments.
The proposed committees provide a formal chain of responsibility. The apex-level data governance committee will be chaired by the chief secretary, with the IT department secretary as convener. Its members will include senior officials from 10 departments, the KSITM director and the state informatics officer of the National Informatics Centre. An IT industry expert, an academic and a representative of a civil society organisation working on open data will participate as special invitees.
The state-level committee will be chaired by the IT department secretary and convened by the KSITM director. Representatives of the finance and planning departments and the state informatics officer will be part of it. This arrangement places the policy within the state’s existing administrative structure rather than assigning the data exchange solely to a technology agency.
That matters because data-sharing decisions can have financial, legal and administrative consequences beyond the operation of a digital platform. Finance and planning officials will be involved at the state-level, while the apex committee will determine the platform’s financial framework. The order also specifies that any expenditure will be incurred only after the required administrative and financial sanctions are obtained.
The policy’s proposed fee model also raises a question about the meaning of paid access to government data. The stated purpose of the fees is cost recovery for data gathering and maintenance, rather than an unrestricted commercial sale of public information. However, the available material does not specify how costs will be calculated, whether fees will vary by dataset or user, or whether any categories of users will receive concessions.
Those details will affect who can practically use the exchange. A large industry, a research institution and a small startup may not have the same capacity to pay for data access or to interpret complex government datasets. The draft’s broad reference to startups, industries and other private players establishes who may seek access, but it does not yet show how equitable or affordable that access will be.
The proposed inventory registers could become one of the most useful administrative outputs of the policy even before the exchange is fully operational. A department cannot consistently decide what to share, retain or exclude without first knowing what datasets it holds, who maintains them and how they are classified. Requiring departments to document those holdings creates a basis for more consistent decisions across government.
At the same time, the policy places a substantial implementation burden on departments. Each department must nominate a chief data officer, share the officer’s details with KSITM, create a data management cell, prepare an inventory and draft a negative list within six months. The policy will therefore require administrative coordination before private users can reliably benefit from the proposed exchange.
The source material does not provide a consolidated estimate of the number of datasets that would be placed on the platform, the departments that will initially participate or the sectors expected to receive priority. It also does not establish when private access will begin. The draft is to be finalised after the committees consider the modified version, which means the operating rules remain under development.
This makes the current announcement less a launch of a completed public-data marketplace and more the creation of a governance route for one. The state has approved the draft in principle, but key decisions on exclusions, retention, costs and final implementation are still pending. The distinction is important for understanding what has changed and what has not.
For Kerala’s urban and economic systems, the policy could influence how information produced by public institutions is used outside government, but the evidence currently available does not establish specific applications or outcomes. The policy’s immediate significance lies in the administrative infrastructure it proposes: common classifications, inventories, designated officers, committees and a digital exchange platform.
The larger question is whether a data exchange can improve public administration without weakening control over sensitive information. Kerala’s draft answers part of that question by excluding personal, confidential and restricted datasets and by requiring negative lists. It leaves other parts to the committees, including the fee structure, online-retention periods and final approval of excluded categories.
The next stage will therefore be procedural rather than promotional. Departments must organise their data holdings, nominate responsible officials and prepare exclusion lists. The state-level committee will review those lists, the apex committee will consider final approval and KSITM will develop the technical and cost framework. Only after those steps, and the required administrative and financial sanctions, will the policy’s practical reach become clearer.
