Halloween to Cyber Monday sale: 30% off your first year of LMS Advisor, cloud or self-hosted.30% off your first year Ends Dec 1, 2026 Claim the offer

DPDP Act 2023 and DPDP Rules 2025: compliance guide for IT companies

India's Digital Personal Data Protection Act explained for software, SaaS and IT service companies, with the Rules that fill in the detail and the dates you need to plan for.

By Published Last reviewed 21 min read
DPDP Act India data protection compliance guide thumbnail with a fingerprint icon

DPDP Act at a glance

Full name
Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (India)
Type
Law
Mandatory or voluntary
Mandatory by law for organizations in scope
Owner
Ministry of Electronics and Information Technology (MeitY); Data Protection Board of India
Where it applies
India, plus processing abroad for offering goods or services to people in India
Current version
Rules notified in November 2025. Board provisions apply now, consent manager rules from about 13 November 2026, and the main duties from about 13 May 2027. A proposal to shorten the 18 months to 12 had not been notified as of our last check.
Key dates
Rules notified 13 November 2025. Consent manager rules from about 13 November 2026. Most duties from about 13 May 2027.
Highest penalty
Up to 250 crore rupees for failing to take reasonable security safeguards
Breach reporting
Inform affected people and the Board without delay, with a detailed report to the Board within 72 hours

The DPDP Act (Digital Personal Data Protection Act, 2023) is India's data protection law. It governs how organizations process digital personal data of individuals and sets up the Data Protection Board of India to enforce it. The Digital Personal Data Protection Rules, 2025, notified on 13 November 2025, fill in the detail and set a phased start, with most duties applying from about 13 May 2027.

For Indian software, SaaS and IT services companies, the DPDP Act affects both the data you collect for your own business and the data you process for clients. Indian enterprise customers are already adding DPDP clauses to vendor contracts. This guide walks through the Act section by section, the Rules that apply to each duty, and how to prepare in the time left. Section and rule numbers are given so you can check each point against the official text, linked in the sources.

What is the DPDP Act and what does it cover?

The DPDP Act was passed by Parliament in August 2023 as Act No. 22 of 2023. It applies to the processing of digital personal data, meaning personal data collected in digital form, or collected in non-digital form and later digitized (Section 3).

  • Personal data is any data about an individual who is identifiable by or in relation to that data (Section 2(t)).
  • Processing is a wholly or partly automated operation on personal data, such as collection, storage, use, sharing, disclosure or erasure (Section 2(x)).

The Act does not apply to personal data processed by an individual for personal or domestic purposes, or to personal data that the person or someone under a legal obligation has made publicly available (Section 3(c)).

Unlike the GDPR, the Act does not create a separate class of sensitive personal data. All personal data is treated alike, with extra rules for children, persons with disabilities and Significant Data Fiduciaries.

Is the DPDP Act mandatory, and when does it apply?

Yes, the DPDP Act is binding law. Its duties are being switched on in phases under the commencement notification (G.S.R. 843(E)) and Rule 1 of the DPDP Rules:

DPDP Act and Rules: when each part applies

MilestoneDateWho it applies to
Rules notified. Board provisions (Rules 1, 2 and 17 to 21) apply immediately2025-11-13The Data Protection Board of India
Consent manager registration and duties (Rule 4) apply, one year after notification2026-11-13Consent managers and fiduciaries that use them
Main duties apply, 18 months after notification: notice, consent, security, breach reporting, retention, children, rights, Significant Data Fiduciaries, cross-border (Rules 3, 5 to 16, 22 and 23)2027-05-13All data fiduciaries and their processors

The dates for the later phases are counted from publication in the Gazette, so check the exact day with your legal team. Reports in 2026 said the government was considering shortening the 18-month period. As of our last review no amendment had been notified, so plan for 13 May 2027 and watch for a change.

When the main provisions start, Section 44 of the DPDP Act also removes Section 43A from the IT Act, 2000. That ends the older "reasonable security practices" regime under the 2011 SPDI Rules, which Indian IT companies have used until now.

Plain answer: the DPDP Act is mandatory. Most duties bite from about 13 May 2027, and that is the date to plan for. Contracts signed now with Indian clients often already require you to meet it by then.

Who must comply with the DPDP Act?

The Act applies to the processing of digital personal data within India, and to processing outside India if it is connected with offering goods or services to data principals in India (Section 3(a) and (b)). The roles are:

  • Data fiduciary: anyone who alone or with others decides the purpose and means of processing (Section 2(i)). This is the GDPR's controller.
  • Data processor: anyone who processes personal data on behalf of a data fiduciary (Section 2(k)).
  • Data principal: the individual the data relates to. For a child, it includes the parent or lawful guardian, and for a person with disability, the lawful guardian (Section 2(j)).
  • Significant Data Fiduciary: a fiduciary or class of fiduciaries the government notifies based on factors such as volume and sensitivity of data, risk to data principals and national interest (Section 10).
  • Consent manager: a person registered with the Board who acts as a single point of contact for data principals to give, manage, review and withdraw consent (Section 2(g)).

For an IT company the roles split like this:

  • You are the data fiduciary for your own employees, job applicants, website visitors, marketing leads and customer account contacts.
  • You are usually the data processor for the personal data your clients put into your software or give you under a services contract. The client stays the fiduciary and remains responsible under Section 8(1), so it will pass duties to you by contract.

Processing of data principals outside India under a contract with a foreign person is exempt from most of the Act (Section 17(1)(d)). That matters for Indian IT services firms processing data of foreign residents for foreign clients, although those clients' own laws, such as the GDPR, still apply.

Why does the DPDP Act matter for IT and SaaS companies?

  • Large penalties. Up to 250 crore rupees per instance for failing to take reasonable security safeguards.
  • Client contracts. Fiduciaries must use processors only under a valid contract (Section 8(2)) and must make sure processors protect data (Section 8(5) and Rule 6). Expect DPDP data processing addenda in renewals.
  • Product changes. Consent flows, notices, withdrawal, rights requests, erasure and log retention all need product support.
  • A fixed deadline. Unlike voluntary standards, there is a date by which the work must be done.
  • Customer trust. Indian consumers and enterprises now know their rights, and the Board will take complaints online.

When can you process personal data under the DPDP Act?

Section 4 allows processing only for a lawful purpose, and only on one of two grounds:

Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the personal data necessary for the specified purpose. Any part of a consent that infringes the Act is invalid to that extent. Withdrawing consent must be as easy as giving it, and after withdrawal you and your processors must stop processing within a reasonable time unless the Act allows otherwise.

Certain legitimate uses (Section 7)

The Act lists situations where consent is not needed. Those most relevant to businesses are:

  • Where the data principal voluntarily provided the data for a specified purpose and has not said they do not consent to its use for that purpose (Section 7(a)).
  • Fulfilling an obligation under a law, or complying with a judgment, decree or order (Section 7(d) and (e)).
  • Medical emergencies, epidemics and disasters (Section 7(f) to (h)).
  • Purposes of employment, or to safeguard the employer from loss or liability, such as preventing corporate espionage, protecting trade secrets or providing services to employees (Section 7(i)).

There is no general "legitimate interests" ground like the GDPR's. If your purpose does not fit Section 7, you need consent.

Notice (Section 5 and Rule 3)

Every request for consent must come with, or be preceded by, a notice. Rule 3 requires the notice to be understandable on its own, in clear and plain language, and to give an itemized description of the personal data and the specified purposes, a link to withdraw consent as easily as it was given, and how to exercise rights and complain to the Board. Notices must be available in English or any language in the Eighth Schedule to the Constitution (Section 5(3)).

What are a data fiduciary's obligations?

Section 8 sets the general duties of every data fiduciary. With the Rules, they are:

DutyWhereWhat it means for an IT company
Responsibility for processorsSection 8(1) and (2)You remain responsible for processing done on your behalf, and may use a processor only under a valid contract.
AccuracySection 8(3)Keep data complete, accurate and consistent where it is used to make a decision about the person or is shared with another fiduciary.
Technical and organizational measuresSection 8(4)Implement appropriate measures to make sure the Act and Rules are actually observed.
Reasonable security safeguardsSection 8(5), Rule 6Protect personal data, including data held by your processors, to prevent breaches.
Breach intimationSection 8(6), Rule 7Inform the Board and each affected data principal of every personal data breach.
ErasureSection 8(7) and (8), Rule 8Erase data, and make processors erase it, when consent is withdrawn or the purpose is no longer served, unless law requires retention.
Contact personSection 8(9), Rule 9Publish the business contact of a data protection officer (if you have one) or a person who can answer questions about processing.
Grievance redressalSection 8(10), Rule 14Run an effective grievance system and respond within the period you publish, which Rule 14 caps at 90 days.

What security safeguards do the DPDP Rules require?

Rule 6 sets the minimum content of "reasonable security safeguards". A data fiduciary must protect personal data in its possession or control, including processing by a processor, with measures that include at least:

  • Securing personal data through encryption, obfuscation, masking or virtual tokens.
  • Controlling access to the computer resources it uses.
  • Visibility into access through logs, monitoring and review, so that unauthorized access can be detected, investigated and fixed.
  • Measures for continued processing if confidentiality, integrity or availability is compromised, such as backups.
  • Keeping those logs and personal data for one year for detecting unauthorized access and investigating it, unless a law requires otherwise.
  • Contract terms with processors requiring them to take reasonable security safeguards.
  • Appropriate technical and organizational measures to make sure the safeguards are observed.

The Rules do not name a security standard. Many Indian IT companies already run ISO 27001, which gives a documented, auditable way to show these safeguards. If you are also covered by CERT-In's directions, remember they have their own six-hour incident reporting rule and 180-day log retention requirement, which run alongside the DPDP rules.

How does breach reporting work under the DPDP Act?

A personal data breach is any unauthorized processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability (Section 2(u)). There is no harm threshold: every breach is reportable.

  1. To each affected data principal, without delay: a description of the breach, its likely consequences, the measures taken or being taken, safety steps the person can take, and a business contact who can answer questions (Rule 7(1)).
  2. To the Board, without delay: a description of the breach, including its nature, extent, timing, location and likely impact (Rule 7(2)(a)).
  3. To the Board, within 72 hours of becoming aware, or a longer period the Board allows on request: updated and detailed information, the facts and circumstances and reasons for the breach, mitigation, findings on the person who caused it, remedial measures, and a report on the intimations given to data principals (Rule 7(2)(b)).

As a processor, you are not named in Rule 7, but your client cannot meet these timelines without you. Expect contracts to require you to tell the client within a few hours and to support its reports.

How long can you keep personal data?

Section 8(7) requires erasure once the data principal withdraws consent or it is reasonable to assume the specified purpose is no longer being served, whichever is earlier, unless retention is needed to comply with law. Rule 8 adds:

  • For the classes in the Third Schedule, the purpose is treated as no longer served if the person has not approached you or exercised their rights for three years. The classes are e-commerce entities with at least two crore registered users in India, online gaming intermediaries with at least fifty lakh registered users, and social media intermediaries with at least two crore registered users.
  • At least 48 hours before erasing on that basis, you must tell the person their data will be erased unless they log in or contact you.
  • Personal data, related traffic data and logs of processing must be kept for at least one year from the processing, for the purposes in the Seventh Schedule, such as investigations, unless another law requires longer.

What are the rules for children's data?

A child under the Act is anyone under 18 (Section 2(f)). This affects edtech, gaming, social and consumer apps, and also B2B products used by schools.

  • You need verifiable consent of a parent or lawful guardian before processing a child's personal data (Section 9(1)).
  • You must not process data in a way likely to cause a detrimental effect on a child's well-being (Section 9(2)).
  • You must not track or monitor children's behavior, or target advertising at them (Section 9(3)).
  • Rule 10 requires due diligence to check that the person giving consent is an identifiable adult, using reliable identity and age details already held or a virtual token from an authorized entity, such as a DigiLocker-based token.
  • The Fourth Schedule exempts some classes and purposes from parts of Section 9, including clinical establishments and health professionals, educational institutions, and childcare and transport providers for safety tracking, within set limits.
  • Rule 11 sets the equivalent process for verifiable consent from the lawful guardian of a person with disability.

What rights do data principals have?

Sections 11 to 14 give data principals these rights, with the process set by Rule 14:

  • Access to information about the personal data processed, the processing activities, and the identities of other fiduciaries and processors it was shared with (Section 11).
  • Correction, completion, updating and erasure of personal data (Section 12).
  • Grievance redressal by the fiduciary or consent manager, which must be used before complaining to the Board (Section 13).
  • Nomination of another person to exercise rights in the event of death or incapacity (Section 14).

Rule 14 requires you to publish on your website or app how to make a request and what identifier you need, and to respond to grievances within the period you publish, no longer than 90 days. There is no right to data portability and no right to object to automated decisions, which differ from the GDPR. Data principals also have duties under Section 15, such as not filing false or frivolous complaints, with a penalty of up to 10,000 rupees.

What extra duties apply to Significant Data Fiduciaries?

The government can notify a fiduciary or class of fiduciaries as Significant Data Fiduciaries (SDFs). As of our last review, no list of SDFs had been notified. If you are named, Section 10 and Rule 13 require you to:

  • Appoint a data protection officer based in India who represents the SDF, is responsible to the board of directors or similar governing body, and is the point of contact for grievances.
  • Appoint an independent data auditor.
  • Carry out a data protection impact assessment and an audit once every twelve months, and have the person who did them report significant observations to the Board.
  • Check that technical measures, including algorithmic software used to host, display, upload, modify, publish, transmit, store, update or share personal data, are not likely to pose a risk to data principals' rights.
  • Make sure personal data and traffic data that the government specifies, on a committee's recommendation, is not transferred outside India.

Large IT and SaaS companies serving Indian consumers, and their processors, should watch for SDF notifications, because SDF clients will pass these duties into vendor contracts.

Can you transfer personal data outside India?

Yes, in general. Section 16 lets the central government restrict transfers to specified countries by notification, which is a negative list approach. No such list had been notified as of our last review. Rule 15 adds that transfers are subject to any requirements the government sets by general or special order for making data available to a foreign state or its agencies. Stricter sector laws still apply, such as RBI's rule on storing payment system data in India (Section 16(2)).

For Indian IT services companies serving foreign clients, the bigger question is usually the client's law. EU clients, for example, need a GDPR transfer mechanism to send data to India. See our GDPR guide.

What training does the DPDP Act require?

The Act and Rules do not contain a clause that says "train every employee". Training still follows from the duties:

  • Section 8(4) requires appropriate technical and organizational measures to ensure effective observance of the Act. Staff who do not know the rules cannot observe them.
  • Rule 6 requires organizational measures to make sure security safeguards are observed, and breach detection depends on people reporting what they see.
  • Rule 7 sets breach timelines that only work if staff know to escalate at once.
  • Rule 14 requires a working process for rights requests and grievances, which support and HR teams must know how to handle.
  • Section 10 requires SDFs to run DPIAs and audits, and auditors usually check staff awareness.

A practical DPDP training plan for an IT company covers everyone at onboarding and once a year, with role-based modules for support, HR, marketing, product and engineering. Topics include what counts as personal data, consent and notice, legitimate uses for employee data, spotting and reporting a breach, handling access and erasure requests, children's data, and safe use of AI tools with client data.

Track DPDP training across every team and location. LMS Advisor lets you build or upload your data protection courses, assign them by team with due dates, send reminders, add a scored quiz and export dated completion records. Its web interface is available in nine languages, including Hindi. See compliance training in LMS Advisor.

How do you prepare for the DPDP Act step by step?

  1. Map personal data. List processing activities, the data, the people it relates to, purposes, systems, processors and retention.
  2. Decide your role per activity. Fiduciary or processor. Flag any processing of children's data.
  3. Pick the ground for each purpose. Consent or a Section 7 legitimate use. Write down why.
  4. Rewrite notices and consent flows to meet Section 5 and Rule 3, with an easy withdrawal link and language options.
  5. Close security gaps against Rule 6. Encryption or masking, access control, logging with one-year retention, monitoring and backups.
  6. Build the breach process for intimation without delay and the 72-hour detailed report, and align it with CERT-In's six-hour rule.
  7. Set retention and erasure rules, including the 48-hour warning where the Third Schedule applies.
  8. Publish a contact and grievance process with a response period of no more than 90 days.
  9. Update contracts. Processor terms for your vendors, and DPDP addenda for your clients.
  10. Plan for children's data if your product may be used by people under 18.
  11. Train staff and keep records.
  12. Review before 13 May 2027 and then yearly.

DPDP Act readiness checklist

Tick what you already have. Your progress is saved in this browser.

Data and grounds

  • Inventory of personal data and processing activities
  • Fiduciary or processor role decided for each activity
  • Consent or a Section 7 legitimate use recorded for each purpose
  • Children's data identified, with a verifiable parental consent method

Notices and rights

  • Notices meet Rule 3 and are available in the languages you need
  • Consent withdrawal is as easy as giving consent
  • Published contact person or DPO
  • Rights and grievance process with a published response period of 90 days or less

Security and breaches

  • Encryption, masking or tokenization where appropriate
  • Access control and logging, with logs kept for one year
  • Backups and continuity measures
  • Breach procedure for immediate intimation and the 72-hour report
  • Processor contracts require reasonable security safeguards

People and retention

  • Retention periods set, with erasure in place
  • 48-hour erasure notice where the Third Schedule applies
  • DPDP training completed by all staff, with dated records
  • Role-based training for support, HR, marketing and engineering

What are the penalties under the DPDP Act?

Section 33 and the Schedule to the Act set maximum monetary penalties per instance. The Board decides the amount after an inquiry, considering factors such as the nature, gravity and duration of the breach, the type of data affected, repetition, any gain or loss avoided, and steps taken to reduce the effects (Section 33(2)).

BreachMaximum penalty
Failure to take reasonable security safeguards to prevent a personal data breach (Section 8(5))250 crore rupees
Failure to inform the Board or affected data principals of a personal data breach (Section 8(6))200 crore rupees
Non-fulfilment of additional obligations for children (Section 9)200 crore rupees
Non-fulfilment of additional obligations of a Significant Data Fiduciary (Section 10)150 crore rupees
Breach of a voluntary undertaking accepted by the Board (Section 32)Up to the penalty for the breach it covered
Breach of any other provision of the Act or Rules50 crore rupees
Breach of duties of a data principal (Section 15)10,000 rupees

Appeals against Board decisions go to the Telecom Disputes Settlement and Appellate Tribunal (Section 29). The Act has no criminal offences, and penalties go to the government: it does not set up a route for affected individuals to claim compensation.

How DPDP-ready is your company?

Answer yes or no for your company today.

  1. We have an inventory of the digital personal data we process.
  2. We know where we are a data fiduciary and where we are a processor.
  3. Each purpose relies on consent or a listed legitimate use, and we recorded which.
  4. Our notices are itemized, in plain language and link to an easy withdrawal option.
  5. We know whether any of our users are under 18.
  6. Personal data is encrypted, masked or tokenized where appropriate.
  7. We keep access logs for at least one year.
  8. We can inform the Board and affected people without delay, and file a detailed report within 72 hours.
  9. Our contracts with processors require reasonable security safeguards.
  10. We have retention periods and actually erase data when they end.
  11. Our grievance process publishes a response time of 90 days or less.
  12. All staff completed DPDP training, and we can show the dates.

Starting out. Begin with the data inventory and the grounds for processing. These decide most of the rest.

On the way. Focus next on breach reporting, retention and processor contracts, which carry the largest penalties.

Well placed. Test the breach process, refresh training and watch for Significant Data Fiduciary and transfer notifications.

How does the DPDP Act compare with the GDPR?

DPDP ActGDPR
Data coveredDigital personal data onlyAll personal data, digital or in filing systems
Sensitive data classNone, but extra rules for children and SDFsSpecial categories with stricter conditions
GroundsConsent or listed legitimate usesSix lawful bases, including legitimate interests
ChildrenUnder 18, verifiable parental consent13 to 16 depending on the country, for online services
Breach reportingEvery breach, without delay, plus a 72-hour reportRisk-based, within 72 hours, people told if high risk
RightsAccess, correction, erasure, grievance, nominationAdds portability, restriction, objection and automated decision rules
TransfersAllowed unless restricted by notificationOnly with adequacy or safeguards
Maximum penalty250 crore rupees per instance20 million euros or 4% of worldwide turnover

Other Indian laws that apply alongside it include the IT Act, 2000, the CERT-In directions, the IT Rules, 2021 for intermediaries, and sector rules such as RBI's IT directions and SEBI's CSCRF.

Key DPDP Act terms

Data fiduciaryThe person who decides the purpose and means of processing. Data processorThe person who processes personal data on behalf of a data fiduciary. Data principalThe individual the personal data relates to, or their parent or lawful guardian. Significant Data Fiduciary (SDF)A fiduciary notified by the government that has extra duties. Consent managerA Board-registered person that lets individuals give, manage and withdraw consent through one platform. Data Protection Board of IndiaThe body that inquires into breaches, imposes penalties and handles complaints, working as a digital office. Legitimate useOne of the situations in Section 7 where consent is not needed.

DPDP Act FAQs

When does the DPDP Act come into force?
In phases. The Board provisions apply from 13 November 2025, consent manager rules from about 13 November 2026, and most duties, including notice, consent, security, breach reporting and rights, from about 13 May 2027.
Does the DPDP Act apply to companies outside India?
Yes, when they process digital personal data outside India in connection with offering goods or services to people in India.
Does the DPDP Act apply to Indian IT companies processing foreign data?
Mostly no. Section 17(1)(d) exempts most duties for processing of personal data of people outside India under a contract with a person outside India. Security safeguards still apply, and the client's own law, such as the GDPR, usually applies too.
What is the DPDP breach reporting deadline?
You must inform affected data principals and the Board without delay, then give the Board a detailed report within 72 hours of becoming aware, unless the Board allows longer.
Is every data breach reportable under the DPDP Act?
Yes. Unlike the GDPR, there is no risk threshold. Every personal data breach must be reported to the Board and the affected people.
What is the maximum penalty under the DPDP Act?
Up to 250 crore rupees per instance, for failing to take reasonable security safeguards to prevent a breach.
Does the DPDP Act have a legitimate interests ground?
No. You need consent or one of the specific legitimate uses in Section 7, such as employment purposes or data the person voluntarily provided for a specified purpose.
Who is a child under the DPDP Act?
Anyone under 18. You need verifiable consent from a parent or lawful guardian and must not track, behaviorally monitor or target ads at children, subject to Fourth Schedule exemptions.
Do we need a data protection officer under the DPDP Act?
Only Significant Data Fiduciaries must appoint a DPO based in India. Every other fiduciary must publish the contact of a person who can answer questions about its processing.
How long must logs be kept under the DPDP Rules?
Rule 6 and Rule 8 require personal data, traffic data and processing logs to be kept for at least one year for investigation purposes, unless another law requires longer.
Can personal data be transferred outside India?
Yes, unless the government restricts transfers to a specified country by notification. No such list had been notified at our last review. Sector rules, such as RBI payment data storage, still apply.
Does the DPDP Act require employee training?
It has no explicit training clause, but Section 8(4) requires measures to ensure the Act is observed, and Rule 6 requires organizational measures for security. Training with records is the usual way to show both.
Is LMS Advisor certified for DPDP compliance?
No. There is no DPDP certification, and LMS Advisor holds no privacy or security certification. It helps you run and record DPDP training across your teams.

Official sources and references

We checked these sources while writing and reviewing this guide. Where a rule is a proposal or a draft, the guide says so.

Next steps

  1. Build your personal data inventory and mark where you are a fiduciary and where a processor.
  2. Record consent or a Section 7 legitimate use for each purpose.
  3. Test whether you can inform the Board without delay and file a detailed report within 72 hours.
  4. Assign DPDP training to every team, with due dates before May 2027. Book a demo to see how LMS Advisor tracks it.
  5. Update processor contracts and client addenda with DPDP security and breach terms.

About this guide

Written by , Enterprise LMS Architect, LMS Advisor.

How we wrote it: every requirement in this guide is taken from the official text or the owner's own documentation, linked in the sources above. Where something is still a proposal or a draft we say so, and we review the guide when a new edition, amendment or deadline lands (last reviewed Oct 30, 2026). This guide is general information, not legal advice. LMS Advisor is a learning management system: we do not sell consulting, implementation or certification services.

Related guides
Law

Information Technology Act, 2000

The IT Act 2000 is India's core law on electronic records, digital signatures, cybercrime and intermediaries. It gives legal recognition to…

Guide coming soon
Regulation

CERT-In Directions

The CERT-In Directions apply to service providers, intermediaries, data centers, body corporates and government bodies. They require reporting of…

Guide coming soon
Law

GDPR

The GDPR is the EU law on processing personal data. It applies to organizations established in the EU, and to organizations elsewhere that offer…

Certifiable standard

ISO/IEC 27001

ISO/IEC 27001 is the international standard for an information security management system (ISMS). It asks you to define a scope, assess information…

Certifiable standard

ISO/IEC 27701

ISO/IEC 27701 sets requirements for a privacy information management system (PIMS) for organizations that act as PII controllers, PII processors or…

Guide coming soon
Regulation

RBI IT governance and cyber security directions

RBI requires banks, NBFCs, payment system operators and other regulated entities to govern IT and cyber risk at board level: an IT strategy and IT…

Guide coming soon
Regulation

SEBI Cybersecurity and Cyber Resilience Framework

SEBI's CSCRF replaces earlier cybersecurity circulars with one framework for stock exchanges, depositories, brokers, mutual funds, portfolio managers…

Guide coming soon
Regulation

IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021

The IT Rules 2021 set due diligence duties that intermediaries must meet to keep safe harbor under Section 79 of the IT Act: publish rules and a…

Guide coming soon
Compliance training with proof

Get your teams DPDP-ready before May 2027

LMS Advisor assigns data protection training to every team with due dates and reminders, gives managers a list of who is overdue, and keeps dated completion records and certificates you can show the Board or a customer.

  • Due dates, reminders and overdue reports for mandatory courses
  • Certificates that expire and renew on your retraining cycle
  • CSV, Excel and PDF exports of who completed what, and when

LMS Advisor is our product. It runs your training and keeps the records. It does not certify you against any standard.

Book a demo

Pick a time for your demo Optional

Times are shown in your own time zone.

This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.