Privacy policy on myteam11app.com
myteam11app.com is an editorial reading surface that stores two first-party cookies and nothing else. There is no analytics, advertising or social-pixel tracking on this product. The operator's in-app surface after the verified first-party path is a separate data surface. Captured 17 August 2026.
/Login/playnow) which records the click and continues to the operator. Editorial links inside the body remain independent. Read the responsible play notice before participating.
What myteam11app.com does and does not collect
This disclosure covers myteam11app.com as an editorial product. myteam11app.com stores two cookies: a menu-state cookie and a cookie-consent cookie. Both are first-party. myteam11app.com does not run analytics, advertising, or social-pixel tracking on this editorial reading surface.
The Google Fonts style sheet is loaded with display=swap and does not set cookies on its own. myteam11app.com's CSS and JS are served from the same origin as the route itself; no third-party script is loaded on this reading surface.
The operator's in-app surface after /Login/playnow is a separate data surface governed by the operator's own privacy policy. Visitors who reach the operator's surface should read that policy inside the app after the verified first-party path.
What myteam11app.com receives automatically
myteam11app.com receives only the requests the visitor makes. Standard web-server logs record the request path, the user-agent string, the referrer (if any), the IP address (truncated by the upstream), and the request timestamp. Logs are retained for thirty days for operational debugging and discarded after that.
The cookie banner records the visitor's choice (accepted or dismissed) and the moment of the choice. The cookie that holds this state is mt11_cookie_pref_v1, set with a thirty-day expiry. The cookie carries no identifier beyond its own key.
The cookies that hold menu state are mt11_nav_pref_v1 for the mobile drawer and an auxiliary key for the desktop navigation highlights. Both expire at the end of the browser session.
Who sees the visitor's data
No third party sees the visitor's data through myteam11app.com. myteam11app.com does not transmit the editorially-stored data to analytics services, advertising services, social platforms or any external endpoint. The cookie state stays on the visitor's device.
The server logs are operator-internal and are not shared with any third party. Where a third-party service is required (for example, the Google Fonts CDN for the embedded style sheet), the visitor's IP address is sent to that service as a normal HTTPS request. The visitor can mitigate this by setting their browser to block third-party style sheets; myteam11app.com degrades gracefully to system fonts.
Why myteam11app.com does not address visitors under 18
myteam11app.com is an editorial product for adults 18+. myteam11app.com does not collect information from visitors who identify as under 18, does not direct any content at visitors who identify as under 18, and does not knowingly accept any submission from a visitor under 18.
The real-money gaming service on the operator's surface is also for adults 18+. The operator's KYC chain enforces this gate; minors who attempt to pass through /Login/playnow will fail KYC and the related bonus eligibility.
When the data is deleted
The cookies set by myteam11app.com expire on the timelines above. Server logs are retained for thirty days and then discarded. There is no long-term retention surface on this editorial product.
The operator-side retention is governed by the operator's privacy policy. Visitors who have data on the operator's surface and want it cleared should follow the deletion path on /delete-account/ and contact customer care through /customer-care/.
How a visitor can resolve any privacy concern
Visitors with any privacy concern about myteam11app.com can reach the editorial product team through the contact surface on /contact/. The team replies within the operational window for editorial inquiry, which is captured on that route.
Visitors with privacy concerns about the operator's in-app surface should contact the operator's privacy officer through the in-app help after passing /Login/playnow. The Editorial product is not party to the operator's data handling beyond the click that passes through the verified first-party path.
The deletion path for any state on myteam11app.com is captured on /delete-account/. The DMCA procedure for copyright concerns is on /dmca/.
Seven routes worth opening
Five questions visitors ask first
What information does myteam11app.com collect?
Does myteam11app.com share data with third parties?
Are children directed at myteam11app.com?
How long is data retained?
Where is the deletion path?
Read the privacy policy with the related routes
Read the cookies disclosure, the deletion path and the contact surface alongside this policy. Then continue reading or reach customer care through the operator's flow.