DPDP Compliance Decoded: Sectoral Nuances and Regulatory Expectations

Part IV: Online Entertainment: OTT, Gaming and Digital Media
In furtherance to our article titled “A Guide to Healthcare, Pharma and Medical Devices,” in our fourth and last article of the series we seek to examine the impact of the Digital Personal Data Protection Act, 2023 (“DPDP Act”), on the online entertainment industry, including over-the-top (“OTT”) platforms, gaming companies, and digital media businesses.
Every personalized recommendation on an online platform providing entertainment services like YouTube, Netflix, Spotify, Steam etc., is made possible by continuous collection, use, and processing of digital personal data of the users, i.e., what users watch, search for, play, purchase, and share. The DPDP Act significantly changes the compliance landscape for these businesses. Unlike the earlier Sensitive Personal Data or Information (“SPDI”) framework, which imposed most of its obligations only on specified categories of sensitive digital personal data or information,1 the DPDP Act applies more broadly to digital personal data through which an individual can be identified. The DPDP Act now brings viewing histories, content preferences, inferred interests, payment information, and similar behavioural data within the framework of digital personal data which requires protection. The framework under the DPDP Act also introduces important obligations relating to consent, purpose limitation, data minimization, children’s data, targeted advertising, verifiable parental consent, and erasure.
The principal obligations under the DPDP Act as discussed below are scheduled to take effect from May 2027 onwards. Platforms have time to prepare, but compliance will require changes to be made to their websites and data-retention practices. This analysis examines how the DPDP Act applies to OTT, gaming, and digital media platforms, focusing on the practical questions that arise from their application design, data practices, and everyday user interactions.
Personalization and the Data Behind the Experience
- Entertainment apps offer features like “Spotify Wrapped”, “YouTube Recap” which turn a user’s listening and viewing history into a personalized summary of the year. Alongside this, platforms record smaller interactions such as the songs a user skips, the videos they searched for, the shows they paused and left midway etc., which may help them understand a user’s preferences and tailor their services. Do these actions count as digital personal data under the DPDP Act?
Personalisation is now built into the ordinary experience of using an entertainment platform. A recommendation, playlist, or advertisement may appear organic to the user, but it is often based on a continuing record of what the user watches, skips, searches for, plays, and purchases. For example, YouTube, in the description of their recommendation systems mentions that it identifies watch history, search history, likes, dislikes, and “Not interested” selections as recommendation signals.2
Under the DPDP Act, information may qualify as digital personal data where an individual can be identified by, or in relation to, that information.3 Accordingly, a skipped song recorded against an account linked to an email address, mobile number, or another identifier may constitute digital personal data because the platform can connect that activity to a particular user. The user’s name, therefore, need not appear alongside the skipped song. An account ID, username, or device identifier may be sufficient for such information to qualify as digital personal data if the platform can link it back to the individual.
Platforms may also draw internal inferences from a user’s activity, for example, that the user may respond to an upgrade offer or has an interest in a particular type of content. Even though these inferences are not shown to the user or provided by them directly, they may still constitute digital personal data if linked to an identifiable user.
Truly anonymised and aggregated statistics would stand on a different footing since they cannot be linked back to a particular individual. For example, a streaming platform may report that 62% of its Indian subscribers watched at least one crime series in 2025 without linking that figure to any individual account.
- Entertainment video streaming applications routinely display prompts such as “Because you watched…You might also like…”, using a viewer’s past activity to suggest what they should watch next. Will the DPDP Act prevent platforms from making these personalized recommendations?
Personalised recommendations for adult users are not prohibited under the DPDP Act. A platform may continue to use viewing history to suggest films, programmes, or songs, provided that it has taken specific consent for processing the relevant data and has explained the purpose clearly to the user. The consent being relied upon for such purpose, under Section 6(1) of the DPDP Act has to be free, specific, informed, unconditional and unambiguous with a clear affirmative action.4
A general statement such as “improving your experience” may not adequately explain what the platform intends to do with a subscriber’s data. A more precise disclosure would need to be made stating that the platform will process the user’s viewing history to recommend similar films or programmes. If the same viewing history is used to infer whether the subscriber may be willing to pay for an upgraded subscription it would qualify as a different use case since it is using viewing behaviour not to improve content discovery, but to make a commercial prediction about the user.
The DPDP Act also gives a Data Principal the right to request erasure of digital personal data under section 12(1)5, subject to the statutory exceptions. This is popularly known as the “right to be forgotten”. If a subscriber requests deletion, the platform must consider not only the viewing history stored in the account but also any identifiable recommendation or advertising profiles created from it. The data must be erased unless its retention is necessary for the specified purpose or required by law.
The quantity of digital personal data being processed by platforms is also required to be relooked at. The platforms should assess what information is necessary for meaningful personalisation and avoid retaining more data than the stated purpose requires. The DPDP Act does not bring an end to personalized recommendations. It requires platforms to be more precise about what data they use, why they use it, and how long they need to retain it. Personalisation may continue, but broad or unexplained uses of a user’s data will require closer scrutiny.
- Gaming platforms often make parts of a player’s profile such as their username, avatar or tournament score visible to other users. How does the DPDP Act treat the other information the platform holds about that player?
Section 3 of the DPDP Act excludes digital personal data that a Data Principal makes publicly available, or that another person is required to make publicly available to comply with legal obligations from the applicability of the DPDP Act.6 The exclusion is limited to the information made public by the Data Principal himself or caused to be made publicly available it does not place the individual’s entire account outside the applicability of the DPDP Act.
A gamer may choose to publish a username, profile, or tournament score. That does not make their private chats, device information, purchase history, or the platform’s inferences about their spending habits publicly available. Each category of data must be assessed separately.
- Are OTT platforms with very large user bases likely to be classified as Significant Data Fiduciaries, and what additional compliance burden would that create?
The DPDP Act introduces the concept of ‘Significant Data Fiduciary’. The Significant Data Fiduciary classification is dependent on an assessment by the Central Government on multiple factors including the volume and sensitivity of data and risk to the rights of Data Principal. Given the large volume of digital personal data that is collected by entertainment platforms with very large user bases, such platforms could be classified as Significant Data Fiduciaries. Platforms notified as Significant Data Fiduciaries by the Central Government will be subject to the additional obligations set out in Rule 13 of the Digital Personal Data Protection Rules, 2025. These include annual data protection impact assessments, and audits generally and also specifically concerning specified algorithmic software and its potential impact on Data Principals’ rights.
Platforms that are not notified as Significant Data Fiduciaries will not face these additional requirements. They must nevertheless understand how their recommendation and advertising systems use digital personal data so they can honour consent choices, protect children’s data, and respond to erasure requests.
- Online games commonly use third-party SDKs and tools to record gameplay events, play duration, level progression, virtual-currency transactions, and engagement. These tools may support personalised recommendations, in-game offers, advertising, or fraud detection. If the information is collected by an external Data Processor, does responsibility shift away from the game publisher?
No, outsourcing processing does not transfer the platform’s responsibility. Section 8(1) of the DPDP Act makes the Data Fiduciary responsible for processing of data undertaken on its behalf and under section 8(2) of the DPDP Act7 requires a valid contract when a Data Processor is engaged.8
For instance, the game publisher is the Data Fiduciary because it determines why and how the gameplay data will be used. The analytics provider is a Data Processor only when it processes that data on the Data Fiduciary’s instructions and on their behalf i.e., by recording gameplay events and preparing reports to improve the game’s recommendations or performance. If the analytics provider instead decides to use the gameplay data for its own purposes, such as combining it with information from other games to create advertising profiles, it would be acting as a separate Data Fiduciary for that processing. The analytics provider’s legal status depends on its actual use of the data and not merely on the label assigned to it in the contract.
The analytics provider cannot automatically rely on the publisher’s original notice or consent for this separate use. If it determines its own purposes for using the gameplay data, it would be acting as a separate Data Fiduciary for that processing rather than as a Data Processor. Where consent is relied upon and the new purpose is not covered by the existing notice and consent, the analytics provider, in its capacity as a Data Fiduciary, would need to issue the relevant notice and obtain fresh consent from the Data Principal. If it continues to act only as a Data Processor, the publisher remains responsible for ensuring that the processing stays within the purposes disclosed to, and consented to by, the Data Principal. A general statement that the game does not “sell digital personal data” would not address the issue if a third-party provider uses gameplay or device information for its own purposes.
Consent, Choice and User Control
Once a platform’s data practices are understood, the next question is whether the user has been given a real choice about them. Consent under the DPDP Act is not satisfied merely because a user clicks “accept”. Platforms must consider whether the choice is free, unconditional and unambiguous, whether refusing an optional use affects access to the service, and whether users can later withdraw their consent or request erasure.
- Can a platform make access to its content conditional on agreeing to personalised advertising?
A platform should be cautious before making access to its service conditional on processing that is not necessary to provide that service. Section 6 of the DPDP Act requires consent to be free and unconditional thus, making a subscription dependent on consent to unrelated behavioural advertising difficult to justify simply because the advertising is commercially valuable.9 For example, an online delivery app may require a user’s delivery address and contact number to complete an order. It should not make the service conditional on providing additional digital personal data, or on agreeing to the use of that data for promotional messages, where such data or use is not necessary to fulfil the order.
The same reasoning would apply to an entertainment platform. Making access to a subscription conditional on consent to unrelated behavioural advertising may therefore be difficult to justify merely because the advertising is commercially valuable. Consent to access content and consent to use viewing behaviour for targeted advertising should be assessed as separate purposes. The platform should be able to record and respect those separate choices. Treating playback, recommendations, and advertising as one bundled purpose cannot be remedied by adding more words to the privacy policy, the service itself must be designed to reflect the choices it offers users. This does not mean that a user who refuses or withdraws consent is guaranteed access to every feature in precisely the same form. Certain features may depend on specific data processing.
- If a platform puts “Accept personalised ads” on the first screen but buries “Withdraw consent”, can that still count as valid consent?
Section 6(4) of the DPDP Act requires withdrawing consent to be as easy as giving it. A platform that obtains consent through one prominent click but makes withdrawal dependent on multiple settings pages, help articles or customer-support requests is likely to face a compliance concern.
The concern is not only limited to the number of clicks but even confusing wording, double negatives or a design that makes “accept” far more visible than “decline” may make it difficult for the user to identify and exercise the option to refuse consent. Platforms must therefore ensure that their consent interfaces clearly present the option to decline and allow consent to be withdrawn through an equally simple process.
- The DPDP Rules introduce a three-year, inactivity-based erasure period for specified online gaming intermediaries with at least fifty lakh registered users in India. Does this mean that, after three years of inactivity, a gaming platform must erase all of a player’s data?
Under Rule 8(1) and Rule 8(2), read with the Third Schedule to the DPDP Rules, 2025, specified Data Fiduciaries must erase digital personal data after the prescribed period of inactivity. This requirement applies, among others, to online gaming intermediaries with at least fifty lakh registered users in India. It is not general permission for every gaming platform to retain all user data for three years. For eligible online gaming intermediaries, the three-year period runs from the later of (i) the last time the user approached the platform for the specified purpose or exercised data right; or (ii) the commencement of the DPDP Rules, 2025. The rule also accounts for continued access to the player’s account or virtual tokens and requires the platform to give at least 48 hours’ advance notice before erasing the data.
Rule 8(3), read with the Seventh Schedule to the DPDP Rules 2025, requires digital personal data, traffic data, and processing logs to be retained for at least one year from processing, unless a longer period is required by law. Therefore, gaming platforms cannot apply a three-year retention period to all user data. If a transaction record must be retained by law, it may be kept for that legal purpose, but the platform cannot automatically use it to predict or influence the user’s next purchase.
Children and Parental Control
Children often form a significant part of the audience for OTT platforms and online games, but their participation raises questions beyond the content they are permitted to access. A parental PIN or children’s profile may restrict what a child can watch, but it does not necessarily determine what data the platform collects or how that data is used. The DPDP Act therefore treats children’s data as a distinct compliance concern, particularly in relation to tracking, behavioural monitoring, targeted advertising, and parental consent.
- Section 9(1) of the DPDP Act requires verifiable parental consent before a platform processes a child’s digital personal data. Does that consent also permit the platform to monitor the child’s behaviour or serve advertising based on that behaviour?
No, verifiable parental consent is a prerequisite for processing a child’s digital personal data and not a waiver of the separate restrictions under Section 9 of the DPDP Act. Section 9(2) of the DPDP Act prohibits processing of data likely to have a detrimental effect on a child’s well-being, while Section 9(3) of the DPDP Act prohibits tracking or behavioural monitoring of children and targeted advertising directed at them. Parental consent cannot, by itself, authorise processing data that these provisions prohibit.10
The same analysis applies to recommendation systems. A platform cannot avoid the restriction on behavioural monitoring merely by describing the resulting output as a content recommendation rather than an advertisement. If the recommendation is generated by continuously tracking and analysing the child’s behaviour, the underlying processing may still fall within Section 9(3) of the DPDP Act.
- Most fourteen-year-olds can simply click “I am over 18”. What does “verifiable parental consent” under Rule 10 of the DPDP Rules require?
Rule 10 does not prescribe a single method of age or identity verification. Rule 10 requires the Data Fiduciary to adopt appropriate technical and organizational measures and exercise due diligence to establish that the person identifying themselves as the parent is an identifiable adult. The rule permits reliance on reliable identity and age details, or a virtual token issued by an authorised entity, including through DigiLocker.
The Rules do not state that a complete identity document must be collected from every viewer, nor do they prescribe that a birth-year declaration will always be sufficient. The adequacy of the method will depend on whether it provides the level of assurance required in the circumstances. Where a token establishes the relevant fact, Rule 10 does not independently require the platform to retain the underlying identity document. Any additional information collected for verification must also be assessed against the DPDP Act’s requirements concerning necessity and responsible processing.
Rule 10 under the DPDP Rules 2025 expressly focuses on verifying that the person identifying themselves as the parent is an identifiable adult but leaves the verification method open. In the following framework, an adult’s assertion of being a parent is not, by itself, the end of the inquiry.
The United States’ Children’s Online Privacy Protection Act (“COPPA”) Rules give more concrete examples of how parental consent may be verified. The options include a signed consent form, a payment-card transaction that notifies the account holder, a telephone call or video conference with trained staff, verification of a government-issued identity document against a database, knowledge-based security questions and, in approved cases, comparison of a parent’s identity photograph with a second photograph using facial-recognition technology.11 Indian law however does not prescribe these methods under Rule 10. It instead leaves the choice of method to the platform but requires verifiable parental consent and due diligence to establish that the person identifying themselves as the parent is an identifiable adult.
Extending the Conversation: Webinar on DPDP Act
In a webinar held on 29 July 2026, Acuity Law, in association with Legal 500, explored the practical impact of the DPDP Act and shared sector-specific insights to help organisations navigate the new framework with confidence.
Authors: Souvik Ganguly and Srividya M S
For any queries or further engagement on the matters discussed in this article, please reach out to Acuity Law at [email protected]
The information contained in this document is not legal advice or legal opinion. The contents recorded in the said document are for informational purposes only and should not be used for commercial purposes. Acuity Law LLP disclaims all liability to any person for any loss or damage caused by errors or omissions, whether arising from negligence, accident, or any other causes.
- Rule 3, Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. ↩︎
- YouTube Help, “Learn more about how YouTube works for you”, under “Recommended videos”, available at: https://support.google.com/youtube/answer/9962575. ↩︎
- Section 2(t), DPDP Act 2023. ↩︎
- Section 6(1) DPDP Act 2023. ↩︎
- Section 12(1) DPDP Act 2023. ↩︎
- Section 3, DPDP Act 2023. ↩︎
- Section 8(2), DPDP Act 2023. ↩︎
- Section 8, DPDP Act 2023. ↩︎
- Section 8, DPDP Act 2023. ↩︎
- Section 9, DPDP Act 2023. ↩︎
- Federal Trade Commission, Complying with COPPA: Frequently Asked Questions, FAQ I.4, available at: https://www.ftc.gov/business-guidance/resources/complying-coppa-frequently-asked-questions; see also 16 C.F.R. § 312.5(b). ↩︎



