Owner of myteam11, written as an identity disclosure card

The owner route is an identity disclosure card. It does not run a corporate registry, does not pull filings from the relevant registrar, and does not publish ownership structure. The route tells a first-time visitor that the owner, the parent company and the corporate filings are operator-controlled fields, and that the verified in-app disclosure is the authoritative reading.

The route exists because the owner question is one of the most common first-time visitor questions. Visitors who land on the editorial reference often want to know who runs the product before they decide to enter through the verified first-party path. The editorial reference answers the question in measured language: the standing reading lives inside the operator product, and the editorial reference does not republish the standing reading.

The route also covers the sister-brand question, the parent-company question and the App Store publisher question. Each answer points back to the verified in-app disclosure rather than republishing the disclosure on a third-party surface.

The verified in-app disclosure is the authoritative reading of the operator's identity. The disclosure sits inside the operator product, typically in the profile or hamburger entry, and exposes the operator's registered name, the parent company (where applicable), the regulatory framework the operator references, and the standing contact channels.

The disclosure is the authoritative reading because the operator updates it as corporate structure changes. The editorial reference cannot match the disclosure's freshness because the editorial reference is a dated snapshot; the in-app disclosure is a current reading.

Visitors who need a specific corporate filing should consult the relevant registrar. The visitor who needs the standing identity reading should open the in-app disclosure. myteam11app.com does not republish the disclosure because the disclosure is operator-controlled and can change between releases.

The publisher name on the App Store and the verified in-app disclosure should reconcile. The publisher name is the developer field on the App Store listing; the disclosure is the operator's registered name inside the product. A visitor who sees a publisher name that does not match the disclosure should not download from that listing.

App Store regional availability is a separate friction. If the App Store listing does not appear, the regional Apple ID may not be enabled for the operator's distribution. Switch to an India Apple ID or contact /support/ for the standing reading.

The editorial reference does not publish the publisher name. The publisher name is operator-controlled and the App Store listing is the authoritative surface. The in-app disclosure is the standing reading of the operator's registered name; both names should match.

The regulatory framework the operator references is the Public Gambling Act 1867 at the central level, the state-level Public Gambling Acts, the Online Gaming Rules under the IT Act 2008 and the MeitY 2023 rules, and the SRVA verification requirement under the IT Rules 2023 amendment. The framework names an operator category (real-money online game) and a verification envelope (SRVA).

The framework does not name an owner. The framework names a category and an envelope. The operator's standing under the framework is exposed in the verified in-app disclosure; the editorial reference does not republish the standing.

Visitors who need a specific regulatory interpretation should consult a qualified lawyer in their jurisdiction. The editorial reference restates the framework the operator references; it does not interpret the framework for a specific visitor.

This route does not run a corporate registry. It does not pull filings from the relevant registrar. It does not publish ownership structure. It does not expose the operator's parent company. It does not provide a corporate filing.

If a visitor lands on this route expecting any of those surfaces, the route forwards them to the correct entry: corporate filings to the relevant registrar, ownership structure to the verified in-app disclosure, and regulatory interpretation to a qualified lawyer in the visitor's jurisdiction.

The boundaries exist because the editorial reference is not the operator and is not a corporate registry. myteam11app.com is an editorial product reference; the route restates the framework the operator references, in measured language, without inventing ownership facts.

myteam11app.com is an independent editorial product reference. myteam11app.com carries an affiliate disclosure on every transactional link; the disclosure appears in the route hero and in the footer. The affiliate relationship does not influence the editorial body copy, which is independent of any sponsor relationship.

The affiliate disclosure is required by the standing reading of the consumer protection framework in India. The disclosure explains that the verified first-party path at /Login/playnow records the click and continues to the operator; editorial body links do not generate any operator-side attribution.

If the visitor prefers to reach the operator surface without going through the editorial reference, the operator's verified in-app download entry and the operator's verified customer-care channel are both reachable directly. The editorial reference does not gate any of those surfaces.