- ClassificationCategoryData Protection & PrivacyDomainPrivacyFramework FamilyGlobal Privacy Regulations
- Regulatory ContextTypeRegulationLegal InstrumentRulesSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionAsia-PacificRegion DetailIndiaPublisherGovernment of India, Department of Information Technology (Ministry of Communications and Information Technology)
- VersioningVersionRules, 2011 (G.S.R. 313(E))Effective DateApril 11, 2011 (on publication in the Gazette of India)Issue DateApril 11, 2011
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityMedium
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The Rules are Indian subordinate legislation published in the Gazette of India. The text is free to read; the linked copy is hosted by WIPO Lex.
Framework text is licensed by its publisher and is included only where stated above.
- The IT (RSPP & SPDI) Rules, 2011 require a body corporate holding sensitive personal data in India to publish a privacy policy and obtain consent.
- Made April 11, 2011 under section 43A of the Information Technology Act, 2000, they came into force on publication in the Gazette.
- Rule 3 defines sensitive personal data: passwords, financial information, health condition, sexual orientation, medical records, and biometric information.
- Information freely available in the public domain or furnished under the Right to Information Act, 2005 is excluded.
- Rule 8 prescribes the reasonable security practices and procedures that section 43A otherwise leaves to agreement.
Overview
The Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (G.S.R. 313(E)) require a body corporate that holds sensitive personal data or information to publish a privacy policy, obtain written consent before collecting the data, limit its disclosure and transfer, and keep reasonable security practices. The Central Government made them on April 11, 2011 under section 87(2)(ob) read with section 43A of the Information Technology Act, 2000, and they came into force on publication in the Gazette (Rule 1).
The Rules apply to a body corporate, and a person acting on its behalf, that collects, receives, possesses, stores, deals with or handles information (Rule 4(1)). “Body corporate” has its section 43A meaning: any company, including a firm, sole proprietorship or other association of individuals engaged in commercial or professional activities (Rule 2(1)(c)). Rule 3 defines sensitive personal data or information through eight clauses: passwords, financial information, health condition, sexual orientation, medical records and history, biometric information, and the details of those categories provided to or received by the body corporate. Information freely available in the public domain, or furnished under the Right to Information Act, 2005 or any other law, is excluded.
Organizations implement the Rules by publishing the policy described in Rule 4, collecting consent in writing by letter, fax or email (Rule 5), naming a Grievance Officer who answers within one month (Rule 5(9)), controlling disclosure and transfer (Rules 6 and 7), and running a documented information security program under Rule 8. Section 44(2) of the Digital Personal Data Protection Act, 2023 omits section 43A and section 87(2)(ob), but that omission takes effect eighteen months after publication of G.S.R. 843(E), in May 2027.
Why does it matter?
The Rules turn “reasonable security practices and procedures” into something a body corporate can document and an auditor can test. Section 43A leaves that phrase to an agreement between the parties, to other law or to what the Central Government prescribes, and Rule 8 is the prescription.
Key benefits include:
- A named security standard
Rule 8(2) names IS/ISO/IEC 27001 as one standard that meets the reasonable security requirement.
- A deemed compliance route
A body corporate that has implemented IS/ISO/IEC 27001, or codes of practice approved and notified by the Central Government, is deemed compliant if the standard or codes are certified or audited regularly by an independent auditor approved by the Central Government (Rule 8(4)).
- Written consent tied to purpose
Consent in writing about the purpose of use is required before collection, and the information may be used only for that purpose (Rule 5(1) and (5)).
- A grievance clock
A Grievance Officer's name and contact details are published on the website, and grievances are redressed within one month (Rule 5(9)).
- Disclosure and transfer limits
Disclosure to a third party needs the provider's prior permission unless the contract allows it or a legal obligation requires it (Rule 6(1)), and transfers go only to recipients that ensure the same level of protection (Rule 7).
How does it work?
Before collecting sensitive personal data or information, the body corporate obtains written consent on the purpose of use, collects only for a lawful purpose connected with its function that the collection is necessary for, and takes reasonable steps to make the person aware of the fact and purpose of collection, the intended recipients, and the name and address of the collecting and retaining agencies (Rule 5(1) to (3)). It may not retain the information longer than required for the lawful purpose or by other law (Rule 5(4)). Providers can review and correct their information, decline to provide it and withdraw consent in writing, after which the body corporate may decline to provide the service (Rule 5(6) and (7)).
The privacy policy must be published on the website and give clear statements of practices and policies, the types of data collected under Rule 3, the purpose of collection and use, disclosure under Rule 6 and the security practices under Rule 8 (Rule 4). Disclosure to government agencies mandated by law needs a written request stating the purpose, and sensitive personal data or information must not be published (Rule 6(1) to (3)). A third party that receives the data may not disclose it further (Rule 6(4)).
Under Rule 8(1), a body corporate meets the reasonable security standard if it has implemented security practices and standards and a comprehensive documented information security program and policies with managerial, technical, operational and physical controls commensurate with the information assets and the nature of business. After a breach it must show the agency mandated by law that it implemented those controls. The audit of reasonable security practices is carried out at least once a year or after significant upgrades to its process and computer resources (Rule 8(4)).
Key Elements
- Sensitive personal data or information (Rule 3)
Eight categories, from passwords and financial information to biometric information, excluding public domain information and information furnished under the Right to Information Act.
- Privacy policy (Rule 4)
A published policy covering practices, data types, purpose, disclosure and security practices.
- Collection and consent (Rule 5)
Written consent, lawful and necessary collection, notice of recipients and agencies, retention limit, review, correction, withdrawal and the Grievance Officer.
- Disclosure (Rule 6)
Prior permission unless the contract or a legal obligation provides otherwise, written government agency requests, no publication and no onward disclosure.
- Transfer (Rule 7)
Transfers inside or outside India only to recipients with the same level of data protection and only where necessary for the contract or with consent.
- Reasonable security practices (Rule 8(1))
A documented program and policies with managerial, technical, operational and physical controls, demonstrable after a breach.
- Standards and audit (Rule 8(2) to (4))
IS/ISO/IEC 27001, approved industry codes, deemed compliance with independent audit at least once a year.
What does it cover?
The Rules bind a body corporate and any person acting on its behalf, covering the information of the providers who give it (Rules 4 and 5). Sensitive personal data or information is limited to the Rule 3 categories, and Rule 7 allows transfers to recipients in India or in any other country on stated conditions. The Rules contain eight rules and no penalty clause: consequences arise under the Information Technology Act, 2000, not under the Rules themselves.
What are its objectives?
The Rules contain no preamble. Their provisions pursue these outcomes:
Providers know what is collected, why, by whom and who receives it (Rules 4 and 5(3)).
Sensitive data is collected with written consent and kept no longer than the purpose requires (Rule 5).
Disclosure and onward transfer are controlled (Rules 6 and 7).
Security controls are documented, proportionate to the assets and demonstrable after a breach (Rule 8(1)).
Complaints reach a named Grievance Officer and are answered within one month (Rule 5(9)).
Framework in Context
Section 43A of the Information Technology Act, 2000 makes a body corporate that is negligent in implementing and maintaining reasonable security practices and procedures for sensitive personal data in a computer resource it owns, controls or operates liable to pay compensation to a person who suffers wrongful loss or gain. These Rules supply the definitions of sensitive personal data and of reasonable security practices that section 43A calls for. The Digital Personal Data Protection Act, 2023 omits section 43A in its Section 44(2)(a), with effect eighteen months after publication of G.S.R. 843(E). The Digital Personal Data Protection Rules, 2025 do not mention the 2011 Rules.
Common Framework Mappings
The Rules name only IS/ISO/IEC 27001 (Rule 8(2)), so ISO/IEC 27001 and its control guidance in ISO/IEC 27002 are the direct mapping for Rule 8. The other frameworks below help with consent, policy, disclosure and transfer duties. The mappings are control-level aids, not equivalences.
Mapped frameworks include:
GDPR (General Data Protection Regulation)
ISO/IEC 27001
ISO/IEC 27002
ISO/IEC 27018
ISO/IEC 27701
NIST Privacy Framework
NIST SP 800-53
SOC 2
How SmartSuite Supports India IT SPDI Rules
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Privacy Management, Compliance Management, Cyber & IT Risk, Third Party Risk Management and Internal Audit Management to hold the sensitive data inventory, the Rule 4 privacy policy, consent and grievance records, disclosure and transfer decisions, the documented security program and the annual audit that Rules 3 to 8 call for.
Sensitive Data Inventory
Record which Rule 3 categories each system, vendor and process holds, and the lawful purpose for each.
Privacy Policy Register
Check the published policy against the five Rule 4 content items and keep version history and the website publication date.
Written Consent and Purpose Records
Store consent received by letter, fax or email, the stated purpose, retention limit, correction requests and written withdrawals (Rule 5).
Grievance Officer Log
Track each grievance to its one-month deadline and keep the published Officer name and contact details current (Rule 5(9)).
Disclosure and Transfer Register
Record each third-party recipient, the permission or contract basis, government agency requests and the protection level of each transfer destination (Rules 6 and 7).
Information Security Program and Audit
Hold the documented program and policies, the ISO/IEC 27001 mapping, annual audit results and the evidence to show after a breach (Rule 8).
Related frameworks

The APEC Privacy Framework (2015) sets nine information privacy principles that APEC economies use to protect personal information while keeping data flowing across the region.

The GDPR (Regulation (EU) 2016/679) sets principles, lawful bases, individual rights and accountability duties for personal data, with fines up to EUR 20 million or 4 percent of turnover.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27018:2025 gives guidelines for protecting PII in public clouds acting as PII processors, built on ISO/IEC 27002:2022 with an extended control set.

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.
Frequently Asked Questions For India IT Rules (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information Rules, 2011)
A body corporate, and any person acting on its behalf, that collects, receives, possesses, stores, deals with or handles personal information or sensitive personal data or information (Rule 4(1)). “Body corporate” means any company, including a firm, sole proprietorship or other association of individuals engaged in commercial or professional activities (section 43A, Explanation).
Rule 3 lists passwords, financial information such as bank account, card or payment instrument details, physical, physiological and mental health condition, sexual orientation, medical records and history, biometric information, and details of those categories provided to or received by the body corporate. Information freely available in the public domain or furnished under the Right to Information Act, 2005 is excluded.
No. Rule 8(2) says IS/ISO/IEC 27001 is one standard for reasonable security practices. A body corporate may instead follow an industry code approved and notified by the Central Government (Rule 8(3)). Either route gives deemed compliance only if it is certified or audited regularly by an independent auditor approved by the Central Government, at least once a year (Rule 8(4)).
Consent is obtained in writing by letter, fax or email on the purpose of use before sensitive personal data or information is collected (Rule 5(1)). Providers can withdraw consent in writing (Rule 5(7)). The body corporate designates a Grievance Officer, publishes the name and contact details on its website, and redresses grievances within one month of receipt (Rule 5(9)).
Section 44(2)(a) of the Digital Personal Data Protection Act, 2023 omits section 43A of the IT Act, and clause (c) omits section 87(2)(ob), under which these Rules were made. G.S.R. 843(E) brings Section 44(2) into force eighteen months after publication, in May 2027. The Act and the DPDP Rules, 2025 do not say what happens to the text of the 2011 Rules.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


