Sector guidesUpdated 22 November 20269 min read

DPDP for Online Gaming Intermediaries

Online gaming intermediaries with at least 50 lakh registered users face three-year inactivity erasure, and every gaming platform must handle minors, in-game tokens and logs under DPDP.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Third Schedule threshold
≥ 50 lakh registered users in India
Inactivity erasure period
Three years (whichever-is-latest rule)
Pre-erasure notice
At least 48 hours (Rule 8(2))
Carve-outs
Account access; virtual tokens usable for money/goods/services
Children
Under 18; Rule 10 parental consent
Applies from
13 May 2027

Quick answer

Online gaming intermediaries with at least 50 lakh registered users in India must erase a player's personal data three years after she last engaged or exercised her rights, or from commencement of the Rules, whichever is latest, with 48 hours' notice, under Rule 8 and the Third Schedule. Account access and in-game virtual tokens usable for money, goods or services are carved out. Obligations apply from 13 May 2027.

  • The Third Schedule threshold for online gaming intermediaries is 50 lakh registered users in India, far lower than the 2 crore for e-commerce and social media.
  • An online gaming intermediary is any intermediary enabling users to access one or more online games.
  • Virtual tokens issued by the platform that can be used for money, goods or services are excluded from inactivity erasure.
  • Players under 18 need verifiable parental consent, and section 9(3) bars tracking, behavioural monitoring and targeted ads directed at them.
  • Every gaming platform must retain processing logs for at least one year under Rule 8(3), then erase them.

Who this is for: Online gaming platforms and studios, Esports and casual gaming apps, Game backend and live-ops engineers, Trust and safety teams, Data Protection Officers

What does DPDP require of online gaming intermediaries?

Item 2 of the Third Schedule to the DPDP Rules covers a Data Fiduciary who is an online gaming intermediary having not less than fifty lakh registered users in India.

  • Purposes covered: all purposes, except (a) enabling the Data Principal to access her user account, and (b) enabling her to access any virtual token issued by or on behalf of the fiduciary, stored on its digital facility or platform, that may be used to get money, goods or services.
  • Time period: three years from the date she last approached the fiduciary for the specified purpose or exercised her rights, or the commencement of the DPDP Rules, 2025, whichever is latest.

Rule 8(1) requires erasure at the end of that period unless law requires retention, and Rule 8(2) requires notice at least 48 hours before, telling the player her data will be erased unless she logs in, contacts the platform or exercises her rights.

The Schedule's definitions:

  • "Online gaming intermediary" means any intermediary who enables the users of its computer resource to access one or more online games.
  • "User" means any person who accesses or avails of the intermediary's computer resource for hosting, publishing, sharing, transacting, viewing, displaying, downloading or uploading information.

These obligations apply from 13 May 2027. Other laws and rules that specifically regulate online games continue to apply alongside DPDP; check the current position for your game category.

The 50 lakh threshold and how to count

The gaming threshold is a quarter of the e-commerce and social media thresholds:

ClassThird Schedule threshold
E-commerce entity≥ 2 crore registered users in India
Online gaming intermediary≥ 50 lakh registered users in India
Social media intermediary≥ 2 crore registered users in India

Many mid-sized Indian gaming apps cross 50 lakh registrations quickly through installs and guest-to-account conversion, so assume you are in scope unless your numbers clearly say otherwise.

Counting questions to document:

  • Guest accounts. Device-bound guest profiles that later link to a phone number or social login — decide whether and when they count as registered.
  • Multi-title studios. If several games share a single account system, take advice on whether registrations are counted per intermediary or per title.
  • Duplicate and banned accounts. Record how they are treated.
  • "In India". Use the signals you rely on for other Indian compliance — registered mobile number, billing country, or location at registration — consistently.

Below the threshold, you still owe general erasure under section 8(7) when consent is withdrawn or the purpose is no longer served.

In-game currencies, wallets and the token carve-out

The carve-out for virtual tokens is central for gaming. Personal data needed to let the player access "any virtual token that is issued by or on behalf of the Data Fiduciary, is stored on the digital facility or platform of such Data Fiduciary, and may be used to get money, goods or services" is not subject to inactivity erasure.

Practical classification:

ItemLikely treatment
Wallet balance or winnings withdrawable as moneyCarve-out applies
Purchased in-game currency redeemable for itemsCarve-out likely applies (usable for goods or services)
Purchased skins and items held in inventoryTake advice; arguably goods obtained, not a token
Free cosmetic achievements and XPNot a token; normal erasure
Match history, chat logs, telemetryNormal erasure

Even within the carve-out, keep only what is needed to give access: the account identifier and the token balance or inventory. Erase surrounding behavioural and social data — friend graphs, chat, match telemetry — on schedule.

Engineering: separate the token ledger from the player profile so you can erase one without breaking the other, and keep the ledger's audit trail for as long as financial or other laws require.

Minors: parental consent and no behavioural profiling

Games attract under-18 players, and DPDP treats anyone under 18 as a child.

  • Verifiable parental consent (s. 9(1), Rule 10). Before processing a child's data, obtain verifiable consent of a parent confirmed to be an identifiable adult, using details you hold, details provided, or a virtual token from an authorised entity such as through DigiLocker.
  • No detrimental processing (s. 9(2)). Monetisation and engagement designs that exploit children are a risk under this provision, which has no exemption.
  • No tracking, behavioural monitoring or targeted ads (s. 9(3)). Live-ops segmentation, churn prediction, dynamic offers based on spend behaviour, and personalised ads for child accounts all sit within the prohibition.

What remains possible:

  • Age assurance to confirm a player is not a child — Fourth Schedule Part B item 6.
  • Safety processing to keep harmful content and ads away from children — Part B item 5.
  • Gameplay that adapts within a session without building a behavioural profile.

Penalties for breaching children's obligations reach ₹200 crore per instance. See AI products for children and age verification and DigiLocker tokens.

Anti-cheat, fraud and log retention

Gaming platforms collect heavy telemetry for anti-cheat, fraud and payment-risk purposes: device fingerprints, input patterns, IP histories, transaction graphs.

  • Rule 6 safeguards. Treat telemetry stores as personal data stores — encryption, access control and monitoring apply. Restrict who can query a player's full history.
  • Rule 8(3). Personal data, traffic data and processing logs must be kept for at least one year from processing for Seventh Schedule purposes, then erased unless another law requires longer. Telemetry and payment logs fall within this.
  • CERT-In. ICT system logs must be kept for a rolling 180 days within India, and specified incidents reported within 6 hours.
  • Purpose separation. Anti-cheat data used to protect the game is not automatically available for marketing segmentation. Keep purposes separate in pipelines.
  • Children's telemetry. Anti-cheat for child accounts should be limited to what fair play and security require; avoid using it to build engagement profiles.

Account takeover and wallet fraud make gaming a frequent breach target. Rule 7 requires notice of every breach to affected players without delay and a detailed Board report within 72 hours. See the breach response playbook.

Gaming readiness plan to 13 May 2027

  1. Confirm threshold status and document the user-count method.
  2. Split data domains: account, token ledger, social graph, chat, telemetry, payments, marketing.
  3. Build the engagement ledger — login, match played, purchase, support contact, rights request — as the Third Schedule clock.
  4. Ship pre-erasure notices through in-game inbox, push and registered contact, at least 48 hours before erasure.
  5. Implement age assurance and parental consent for under-18 players.
  6. Disable behavioural segmentation and targeted offers for child accounts.
  7. Configure one-year log retention and erasure across telemetry and payment systems and processors.
  8. Publish rights channels with identifiers such as player ID, registered mobile or email, and a grievance period of at most 90 days.
  9. Update notices under Rule 3 to itemise gameplay, social, payment and telemetry data.

Large gaming platforms should also prepare for possible Significant Data Fiduciary notification, which would bring annual DPIAs and audits under Rule 13. See retention and erasure under Rule 8.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Check the 50 lakh registered-user threshold

    Count registered users in India with a documented method covering guest, duplicate and multi-title accounts.

    Third Schedule item 2

  2. Separate the token ledger from player profiles

    Keep wallet and in-game token balances apart so other data can be erased without affecting them.

    Third Schedule item 2(b)

  3. Track last engagement per player

    Record logins, matches, purchases, support contacts and rights requests as the erasure clock.

    Rule 8(1)

  4. Send 48-hour pre-erasure notices

    Notify players through registered channels and in-game inbox before the three-year point.

    Rule 8(2)

  5. Obtain verifiable parental consent for minors

    Verify parents as identifiable adults before processing under-18 players' data.

    Rule 10

  6. Turn off behavioural offers for child accounts

    Stop spend-based segmentation, churn targeting and personalised ads for under-18s.

    DPDP Act s. 9(3)

  7. Retain telemetry and payment logs for one year

    Keep processing logs at least one year, then erase, and keep ICT logs 180 days in India.

    Rule 8(3); CERT-In Directions

  8. Secure anti-cheat data

    Restrict access to player telemetry and prevent reuse for marketing.

    Rule 6(1)(b)

  9. Publish rights and grievance channels

    List player identifiers needed and a grievance period of at most 90 days.

    Rule 14

Key dates

  1. DPDP Rules notified

  2. Rule 8, Third Schedule item 2 and children's rules apply

Answers

Frequently asked questions

What is the DPDP threshold for online gaming platforms?

Item 2 of the Third Schedule applies to online gaming intermediaries with not less than 50 lakh registered users in India. They must erase personal data three years after the player last engaged or exercised her rights, or from commencement of the Rules, whichever is latest, with at least 48 hours' prior notice.

Will DPDP erase players' in-game currency?

No. The Third Schedule excludes processing needed to let the player access her user account and any virtual token issued by or on behalf of the platform, stored on it, that can be used to get money, goods or services. Wallet balances and redeemable in-game currency remain accessible.

What counts as an online gaming intermediary under the DPDP Rules?

The Third Schedule defines it as any intermediary who enables the users of its computer resource to access one or more online games. This is broad and covers casual, esports and real-money platforms alike. Other laws specific to online gaming continue to apply separately.

Can gaming apps personalise offers for players under 18?

Not through tracking or behavioural monitoring. Section 9(3) of the DPDP Act bars tracking, behavioural monitoring and targeted advertising directed at children, meaning anyone under 18. Spend-based segmentation and personalised offers for child accounts should be switched off from 13 May 2027.

How long must gaming platforms keep player logs?

Rule 8(3) requires every Data Fiduciary to keep personal data, traffic data and processing logs for at least one year from processing, then erase them unless another law requires longer. CERT-In's 2022 Directions separately require ICT system logs to be kept for a rolling 180 days within India.

Does logging in reset the three-year erasure clock?

Yes. Rule 8(2) says data will be erased unless the Data Principal logs into her user account or otherwise initiates contact for the specified purpose or exercises her rights. Each login, match or purchase should update the player's last-engagement date.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 8 and Third Schedule item 2 (official text)
  • Digital Personal Data Protection Rules, 2025 — Third Schedule Note (b) and (d)(ii) (official text)
  • Digital Personal Data Protection Act, 2023 — Section 9 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.