Privacy Policy
Last reviewed: 13 July 2026
Last substantively updated: 13 July 2026. This policy describes the services detected on the current 22bet.xin installation. It does not describe data held by 22Bet because this publication has no access to that data.
Website delivery and security
The domain uses Cloudflare nameservers and Cloudflare appears in live response headers. Cloudflare may process IP address, request, device and security information to deliver and protect the website under its own published terms. The origin server keeps access and error logs that can include IP address, time, URL, status, referrer and User-Agent.
Log retention
The active server configuration writes site-specific logs, but no administrator-approved fixed retention schedule was found during this review. The policy therefore does not invent a number of days. Logs may be used for security, reliability and incident investigation and may be disclosed where required by applicable law or needed to protect the service.
WordPress and cookies
The public site now runs as a single-language en-IN publication; TranslatePress is inactive and no language-choice cookie is described. Anonymous curl and browser checks found no application cookie set by ordinary page viewing. WordPress can set administrator or login cookies for authorised users, while Cloudflare may set a security cookie when its protective controls are triggered.
Analytics and session recording
No Google Analytics, Microsoft Clarity, Meta Pixel, Hotjar or comparable public-facing analytics or session-replay script was detected in the active rendered pages on 13 July 2026. If one is introduced, this policy and any required consent control must be updated before collection begins.
Contact and message data
No public contact form, upload field or verified domain mailbox is active. The site therefore does not intentionally collect names, email addresses, topics, messages, complaint attachments, identity scans, account credentials or payment records through a contact route. No contact-message retention period applies while that route is absent.
If a form is introduced after mail verification, it must state its fields, purpose, processors, access controls and retention period before publication. The form must not accept attachments or credentials and must not use a visitor’s address as the SMTP From address.
Data not requested
Do not send a gambling-account password, OTP, CVV, UPI PIN, login cookie, wallet key, recovery phrase, full payment-card number or unrestricted identity document. 22bet.xin does not need these items to correct its own editorial content.
Service providers
Cloudflare and the hosting environment may process technical request data. WordPress and active plugins process page and administrative data on the origin server. No external SMTP provider is configured and no tested domain-mail route is advertised. The actual provider list should be rechecked whenever hosting, security, mail or analytics configuration changes.
Privacy requests
The contact page records that no public address has passed delivery verification. A privacy address is not invented. Until a route is verified, the most useful public records are this policy, the source policy and the corrections method; none should be used to transmit sensitive account or payment information.