What each cookie category does on myteam11play.com

The four categories

Essential

Required for the menu, drawer, and consent state. Always on. The category uses local storage for the consent record (lifetime: 12 months) and a single session cookie for the no-scroll class on the body when the drawer is open.

Analytics

Anonymous page-view counts that help us improve the editorial. Off by default. The category uses a first-party analytics endpoint with a 13-month retention. The IP address is truncated before storage. No cross-site tracking.

Marketing

Off by default. Used only if a partner campaign needs it. The category uses no third-party tags on this domain; the toggle is wired to a data attribute on the document element and can be turned on by the consent record only.

Preferences

Remembers the menu and language choices. Off by default. The category uses local storage with a 12-month lifetime. Clearing the consent record resets the preferences.

How to manage the categories

• The footer "Cookie settings" button opens the modal with the current state preserved.
• The banner "Manage" button opens the same modal.
• Withdrawal is as easy as acceptance: turn the toggles off and click "Save my choices".

Retention

The consent record is kept for 12 months, per the GDPR-aligned guidance for non-essential cookies. After 12 months the consent banner re-appears and the reader is asked to confirm the choices.

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 /privacy/ notice is the broader data-collection reference.

How the categories work, and what changes when you turn them off

myteam11play.com uses four cookie categories: essential, analytics, marketing, and preferences. Essential cookies are required for the menu, the drawer, and the consent state, and they are always on. Analytics, marketing, and preferences are off by default until you accept them.

Essential cookies do one job: they keep the drawer, the menu state, and the consent record working between page loads. They do not track you across sites, do not collect identifiers beyond a session token, and do not share data with third parties. Disabling essential cookies would break the menu; that is why they are always on.

Analytics cookies, when you accept them, count anonymous page views to help us improve the coverage. They do not collect identifiers beyond a hashed session token, do not share data with third parties for advertising, and can be turned off at any time without affecting site behaviour.

Marketing cookies are off by default and are used only if a partner campaign needs them. They are not enabled on this domain at the time of writing; the field exists for the case where a future operator campaign needs to attribute a referral. The default is off and stays off until you opt in.

Preferences cookies remember your choices on myteam11play.com: the cookie banner state, the drawer open-on-mobile preference, and any future preferences we adds. They do not share data with third parties. Disabling them returns you to the default behaviour on each visit.

Withdrawal is as easy as acceptance. The Cookie settings button in the footer reopens the modal with your current state preserved; you can change any toggle and save, or you can use Essential only at any time. The decision is yours, and the path is one click from the footer.

Editorial methodology for the cookies policy

This cookies record is a reading of the myteam11play.com cookies, not legal advice. The categories, the providers, and the retention windows are described as observed on the myteam11play.com production site. The methodology for the cookies table is the same as the rest of myteam11play.com: name the cookie, name its purpose, name its lifetime, and do not invent a category that myteam11play.com does not use.

For the cookie table, the source is the cookie audit run on myteam11play.com. The audit is conducted once per quarter by our cookies audit and the result is the canonical reference. If the audit is updated, the table is regenerated and the review date is updated in the footer.

For essential storage, the source is the cookie that maintains the menu state, the consent state, and the cookie-modal state. These are first-party cookies and are required for myteam11play.com to function. myteam11play.com does not operate without essential storage; consent for essential storage is assumed.

For optional storage (analytics, marketing, preferences), the source is the third-party tag that the cookies modal would load when the user opts in. The tags are not loaded by default. If the user opts in, the tag is loaded and the cookie persists for the named lifetime. If the user does not opt in, the tag is not loaded and the cookie is not set.

For withdrawal, the source is the cookie settings button in the footer of every page. The button re-opens the cookie modal with the current state preserved; the user can change the toggle and submit a new consent. The new consent replaces the previous consent in local storage and the cookies page reloads with the new state.

For third-party cookies, the source is the named provider's published policy. myteam11play.com does not host a third-party cookie without a category assignment and a retention window. We do not load a third-party cookie inside a category that does not match the provider's purpose.

Update cadence: cookies-table entries get a fresh review whenever the cookie audit changes, a new optional category is added, a third-party provider changes their policy, or the user requests a category review. The review date is in the footer of every page on myteam11play.com.

What we does not publish

The cookies policy does not publish a cookie that myteam11play.com does not set. The cookies audit does not publish a third-party tag that myteam11play.com does not load. The cookies audit does not publish a retention window that the audit has not recorded.

The cookies audit does not publish a passing-grade behaviour for a tag that the cookie audit has not classified. The cookies audit does not publish a "do not track" signal that myteam11play.com does not respect. The cookies audit does not publish a global privacy control signal that myteam11play.com does not honour.

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

How to verify the cookie audit yourself

Open the browser's developer tools and navigate to the application storage tab. The cookies set by myteam11play.com should match the cookie table on this cookies record. The cookie categories, the providers, and the retention windows should match our reading.

For the essential storage, the cookies that maintain the menu state, the consent state, and the cookie-modal state should be present. The essential storage is the canonical reference; this cookies record links to the developer tools tab rather than restating the storage.

For the optional storage, the cookies that the third-party tags would set when the user opts in should be present in the audit table. The optional storage is the canonical reference; this cookies record links to the developer tools tab rather than restating the storage.

For the withdrawal, the cookie settings button in the footer of every page should re-open the cookie modal with the current state preserved. The withdrawal is the canonical reference; this cookies record links to the cookie settings button rather than restating the withdrawal flow.

For the third-party cookies, the named provider's published policy should describe the cookie's purpose and retention window. The third-party cookies are the canonical reference; this cookies record links to the provider's policy rather than restating the policy.

For what to do if the developer tools tab contradicts the record's table, the answer is the developer tools tab is the canonical reference. The cookies record is updated next time our cookies desk reviews the audit; the reader can verify the audit via the developer tools tab at any time.