Privacy: short notice on cookies, collection and rights

By default, nothing

myteam11app.com does not require an account, a login or a contact detail to read any route. Every route renders without server-side personalisation. Strictly necessary cookies carry the cookie preferences and the session state required to keep the editorial routes running; that data lives in your browser, not on the editorial surface.

Optional categories (analytics, marketing) are off until the visitor accepts. The cookie banner offers three choices: Accept all, Reject optional or Customise. The choice is stored under the mt11_cookie_pref_v1 key and can be re-opened through the Cookie settings button at the foot of every route. Resetting the choice clears the stored value on the next render.

The /privacy-policy/ route lists the full data inventory the editorial surface handles, the retention window per category and the processor list behind any analytics or marketing cookie. The short notice is intentionally short: the long notice carries the field-level reading.

What each cookie category does

Three categories, three choices. The cookie banner explains the choice; the cookie panel lets a visitor switch any optional category on or off.

What happens when you click Play Now

The Play Now CTA on every route is a link to the verified first-party path /Login/playnow. Clicking the link is an external navigation: the visitor leaves myteam11app.com and lands on the operator's domain. The handoff is not a data transfer from the editorial surface; the operator's own data-protection notice applies on the operator's domain.

The operator domain handles the login, the KYC verification and the wallet. The editorial surface never sees the credential, the KYC document or the balance. Once the visitor is back on myteam11app.com, the same cookie preferences apply; the editorial surface does not re-read operator state.

If you have a privacy concern that spans both surfaces (for example, a marketing email that references the editorial visit), contact the operator through the in-app help centre. The editorial surface cannot resolve cross-surface concerns; only the operator holds the data needed to do that.

Access, deletion, complaint

Three rights a visitor always has on the editorial surface. Each is a dedicated route with a verified contact mechanism.

Right of access. The visitor can request a copy of the data the editorial surface stores by emailing the address listed on /customer-care/. The reply lists the cookie preference value, the analytics page-view record (if analytics are on) and any explicit complaint trail.

Right of deletion. The visitor can clear the strictly necessary cookie at any time by resetting the browser. The optional analytics and marketing records expire on the cookie-consent refresh. For the verified account-deletion request against the operator, use /delete-account/.

Right to complain. The visitor can escalate any privacy concern through /customer-care/. Where the concern is about the operator, the editorial surface forwards the visitor to the in-app help centre. Where the concern is about the editorial surface, the route itself is the resolution path; the response is published as a dated note on /news/.

How long the editorial surface holds data

The retention windows for the editorial surface are short. The cookie preferences key expires on the visitor's next manual reset; the analytics record rolls forward only when the visitor has opted in; the per-session sticky CTA dismiss is session-scoped.

Server-side logs are kept for thirty days for the purpose of debugging and security review. Server-side logs do not include the cookie preference value, the analytics page-view record or any marketing attribution; logs record only the request line, the response status and a coarse country code.

The /privacy-policy/ route carries the field-level retention table. The short notice on this route carries the headline windows only; the long notice is the authoritative document.

Where the full privacy disclosure lives

The /privacy-policy/ route is the long-form disclosure. It carries the data inventory, the retention windows per category, the processor list behind the optional cookies, the cross-border data-flow statement, the rights route per category and the complaint escalation path. Read the long-form disclosure if you need a field-level reading.

Five other routes worth reading next

The privacy cluster on myteam11app.com carries five sibling routes. Each carries its own archetype and conclusion.

Six questions readers keep asking on the privacy notice

Read the long-form disclosure before you click Play Now

The /privacy/ route is the short companion. The /privacy-policy/ route is the long-form disclosure. The cookie panel at the foot of every route lets you switch optional categories on or off.