Delete account, written as a rights question

The delete-account route is a rights question. It restates the right to delete the account, the right to remove the wallet balance and the right to remove the KYC documents. The route does not run a deletion service; the in-app deletion entry is the authoritative surface.

The route exists because the account-deletion rights question is one of the most important readings on the editorial reference. Visitors who land on myteam11app.com before deciding to enter through the verified first-party path need to know what happens if they decide to delete the account later. The editorial reference answers the question in measured language: the deletion path is in-app, the confirmation is by email or OTP, the timeline is 7 to 30 days, and the data-deletion acknowledgement is the final step.

The route also covers the relationship between deletion and self-exclusion. Self-exclusion closes the account for a standing window; the visitor can return after the window expires. Account deletion is permanent; the visitor's data is removed within the standing window of the deletion request.

The deletion path is exposed inside the operator product. The four steps below restate the path; the in-app deletion entry is the authoritative reading.

1. Request in-app. Open the operator product, tap the profile or hamburger entry, tap Account settings, and pick Delete account. The in-app entry exposes the deletion request form.
2. Confirm email or OTP. The deletion request is confirmed by an email link or an OTP sent to the registered mobile number. The confirmation step is required to prevent accidental deletion.
3. Wait 7 to 30 days. After confirmation, the deletion typically completes within 7 to 30 days. The exact timeline is operator-controlled; the in-app entry exposes the current reading.
4. Receive data-deletion acknowledgement. The visitor receives an acknowledgement once the data-deletion envelope completes. The envelope removes the account, the wallet balance and the KYC documents within the standing window.

Each step is exposed inside the operator product. The visitor can track the status of a pending deletion inside the in-app account settings; the editorial reference does not expose the status because the status is operator-controlled.

Account deletion triggers the data-deletion envelope. The envelope removes the account, the wallet balance, the KYC documents, the contest history and the responsible-play settings within the standing window of the deletion request.

The wallet balance is removed at the end of the standing window. The visitor who wants to withdraw the wallet balance before deletion should open the wallet, request a withdrawal, wait for the withdrawal to settle, and then submit the deletion request.

The KYC documents are removed at the end of the standing window. The visitor who needs the KYC documents for another operator should not submit the deletion request until the new operator's KYC envelope is complete. The standing reading of the data-handling envelope lives on /privacy/.

Self-exclusion and account deletion are two different closure shapes. Self-exclusion closes the account for a standing window; the visitor can return after the window expires. Account deletion is permanent; the visitor's data is removed within the standing window of the deletion request.

The visitor who needs a temporary break should consider self-exclusion first. The standing reading of self-exclusion lives on /responsible-play/. The visitor who needs a permanent closure should consider account deletion.

The two shapes are independent. A visitor who self-excludes and then decides to delete can submit a deletion request inside the in-app account settings after the self-exclusion window expires. A visitor who deletes cannot undo the deletion; the account and the data are removed within the standing window.

This route does not run a deletion request. It does not collect identity documents. It does not run the confirmation step. It does not run the data-deletion envelope. It does not expose the status of a pending deletion.

If a visitor lands on this route expecting any of those surfaces, the route forwards them to the correct entry: deletion requests to the in-app account settings, confirmation to the email or OTP sent by the operator, data-deletion envelope to the standing reading on /privacy/, and status of a pending deletion to the in-app account settings.

The boundaries exist because the editorial reference is not the operator. myteam11app.com is an editorial product reference; the route restates the deletion path, in measured language, without inventing facts.

The editorial reference carries three routes that overlap with the account-deletion reading. The first is /responsible-play/, which restates the self-exclusion tool list and the standing reading of state help-line references. The second is /privacy/, which restates the data-handling envelope and the data-deletion acknowledgement. The third is /login/, which restates the account-access path that the visitor may need before submitting the deletion request.

The visitor who needs to update a KYC document before deletion should open the in-app KYC envelope and use the standing update path. The visitor who needs to withdraw the wallet balance before deletion should open the in-app wallet and request a withdrawal.

The visitor who needs a specific deletion timeline should rely on the in-app deletion entry, not on the editorial reference. The in-app entry is the current reading; the editorial reference is a dated snapshot.