Cookies on myteam11app.com: two keys, two purposes, two retentions

Two cookies are stored on myteam11app.com, both required to remember the visitor's preference state across pages. The first is a menu-state cookie (key: mt11_nav_pref_v1) which remembers whether the mobile drawer is collapsed or expanded, so the visitor does not have to tap the hamburger on every page.

The second is a cookie-consent cookie (key: mt11_cookie_pref_v1) which records whether the visitor has accepted or dismissed the cookie banner. Without that cookie the banner would reappear on every page; the consent cookie is what persists the choice across the session.

Both cookies are first-party. No third-party trackers, no analytics cookies, no advertising cookies are stored by myteam11app.com or by the embedded font style sheet. The Google Fonts style sheet is loaded with display=swap and does not set cookies on its own.

Removing the menu-state cookie would force every visitor to re-tap the hamburger on every navigation. Removing the consent cookie would force the cookie banner to reappear on every page until dismissed. Both effects are small individually but together they degrade myteam11app.com's usability into a re-confirm pattern.

There is no third-party cookie on myteam11app.com. myteam11app.com does not run analytics, advertising, or social-pixel tracking. The single operator-side cookie surface that exists is the operator's own in-app analytics and login state, which sit inside the operator's flow rather than on this editorial product.

The cookie banner on myteam11app.com is the disclosure surface that satisfies the consent rule. Visitors who decline or dismiss the banner keep the session anyway because both cookies are necessary; the banner records the dismissal state but does not block the editorial reading.

The menu-state cookie expires at the end of the browser session (the user closing the browser). The cookie-consent cookie expires after thirty days from the consent moment. After expiry the consent banner reappears once and records the next consent decision in the same key.

No data is transferred off the visitor's device. The cookies set by myteam11app.com contain only preference state and do not carry identifiers beyond the cookie key itself. Cross-device continuity is not supported and is not part of the editorial product scope.

Visitors who want to clear myteam11app.com cookies can do so through the browser's own privacy controls. The path is consistent across major browsers: open myteam11app.com settings, locate the cookies panel, search for myteam11app.com, and delete the two keys. The cookie banner will reappear on the next visit.

Private or incognito browsing does not store cookies across sessions in the same way that standard browsing does. Visitors who want maximum discipline on cookie state can use private browsing for the editorial read and standard browsing for any follow-up actions inside the operator's surface.

This disclosure covers cookies set by myteam11app.com directly. It does not cover cookies set by the operator's in-app surface after a visitor passes through /Login/playnow. Those cookies are governed by the operator's own privacy and cookie policy; visitors should read that policy inside the operator's app after passing the verified first-party path.

The editorial product scope of myteam11app.com is the public reading surface only. Cookies set on myteam11app.com are preference-state only; the operator's surface is a separate cookie surface with its own disclosure.

The reading order is short: /privacy-policy/, /terms/, /responsible-play/, /about/ and the deletion path on /delete-account/. Once these five routes are read the visitor knows the policy posture, the jurisdictional standing and the deletion surface for any preference state.

Visitors who want a single-contact point for any data-related question can use the customer care route on /customer-care/.