The privacy notice for the writers and the operator

What the writers collects

What the operator collects

The operator collects the data needed to run the platform: registered mobile number, KYC documents (PAN, Aadhaar, bank proof), wallet balance, contest history, and device fingerprint. The operator's privacy notice is published inside the in-app Help tab under "Privacy"; the writers does not mirror those fields.

Sharing

• Writers does not sell reader data.
• The desk does not share reader data with the operator unless the reader explicitly asks the desk to forward a question.
• The operator shares data only with KYC processors, payment gateways, and the grievance officer appointed under the PROG Act 2025 framework.

Reader rights

• Right to access: ask the desk what it holds on you. Response window: 7 working days.
• Right to correction: ask the desk to correct inaccurate data. Response window: 7 working days.
• Right to deletion: ask the desk to delete what it holds on you. Response window: 30 days, subject to legal retention.
• Right to portability: ask the desk for a machine-readable copy of the data it holds on you.

Contact the data protection contact

Use the contact form on /customer-care/. The desk's data protection contact responds within 7 working days.

State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.

The /cookies/ reference is the cookie-by-cookie breakdown. The /responsible-play/ reference is the responsible-play path, including self-exclusion.

What the desk collects, what the operator collects, and your rights

myteam11play.com (the writers) collects only what is needed for the menu, the cookie consent state, and the optional analytics you opt into. The desk does not collect identifiers beyond a hashed session token, does not share data with advertising networks, and does not track you across other sites. The cookie modal in the footer is the control surface; the Cookie settings button reopens it with current state preserved.

The operator app collects what is needed for the account, the contest, and the wallet. The categories are listed in the in-app Privacy screen: account identifiers (phone, email), device identifiers (the device token, the IP address), contest identifiers (the teams you build, the contests you enter), and wallet identifiers (the UPI handle, the bank account for withdrawals). The operator's retention and sharing rules are visible in the in-app screen.

Your rights under Indian data protection law: the right to access the data the operator holds about you, the right to correction of incorrect data, the right to erasure of data the operator is not required to retain, and the right to grievance redressal through the operator's data protection contact. The contact is in the in-app Privacy screen; the writers does not have access to operator-side records.

How to exercise a right: open the in-app Privacy screen, find the data protection contact, and send a written request that names the right you are exercising, the data category, and the account identifier. The operator responds within the time window set by Indian data protection law; the writers does not have a role in the response.

The desk's data practices are independent of the operator's. The desk publishes corrections, takedowns, and editorial inquiries through the contact on /legal/; the operator publishes account data requests through the in-app Privacy screen. The two channels do not share data; the desk cannot see operator-side records and the operator cannot see desk-side records.

What remains stable across data practices: the desk's essential cookies, the desk's optional categories off by default, the operator's in-app privacy screen as the canonical source for account data, and the right of access under Indian law. Those four are the durable markers regardless of how the operator updates their internal policies.

Editorial methodology for the privacy policy

This privacy policy is the desk's editorial policy, not a substitute for the myteam11 product brand's privacy policy. Published because this guide accepts user-submitted content and operates under the Indian Information Technology Act 2000 and the Digital Personal Data Protection Act 2023. The methodology is the same as every other page on this guide: name the data category, name the purpose, name the processor, and do not invent a data practice.

For the data categories, the source is the cookie audit and the request-log audit run on the production site. The audit is conducted once per quarter by the editorial team. If the audit is updated, the table is regenerated and the review date is updated in the footer.

For the purposes, the source is the desk's stated purpose for each data category. The desk does not collect data for a purpose that is not stated in the table. If the desk adds a new purpose, the table is updated and the consent flow is updated to match.

For the processors, the source is the named third-party service that receives the data. The desk does not transfer data to a processor that is not named in the table. If the desk adds a new processor, the table is updated and the data subject is notified via the consent flow.

For retention, the source is the desk's data-retention policy. The desk does not retain data beyond the named retention window. If the retention window changes, the table is updated and the existing data is purged.

For user rights, the source is the Digital Personal Data Protection Act 2023. The desk honours the right to access, the right to correction, the right to erasure, and the right to grievance redressal. The contact for any of these rights is the customer-care form on /customer-care/.

Update cadence: this guide is reviewed when the data audit changes, when a new processor is added, when a retention window changes, or when the DPDP Act 2023 is amended. The review date is in the footer of every page in this guide.

What this desk does not publish

The privacy policy does not publish a data practice that the production site does not follow. The desk does not publish a retention window that the data audit has not recorded. The desk does not publish a processor that the desk has not contracted.

The desk does not publish a data subject right that the DPDP Act 2023 does not provide. The desk does not publish a grievance redressal outcome that the desk has not adopted. The desk does not publish a "we never sell your data" claim that the production site cannot honour.

The desk's role is the editorial policy. The reader's role is the consent choice. The desk does not override the reader's consent; the consent flow is the canonical reference. The verified entry route is at /app/.