Privacy Policy
This policy explains the limited data context of the independent website, server and analytics information, external destinations, retention, security and visitor choices.
Scope and the data boundary
This policy applies to the independent website pages and technical delivery under this domain. It does not govern a 77Bet account, external registration, app, payment, game or support conversation. Those services have separate controllers and privacy terms. Following an external link changes the data context, so visitors should read the destination’s current policy before providing an identifier, document or financial information.
The website itself does not provide a visitor account form, gaming login, deposit, withdrawal or identity-verification process. It should never receive a 77Bet password, OTP, bank PIN, card security code or account-recovery code. Visitors should not send such information through any future editorial correspondence. If a person asks for it while claiming to represent this website, the request should be treated as suspicious.
- Applies to this domain’s independent pages
- Does not govern external accounts
- No gaming credential belongs here
- External destinations have separate controllers
Privacy responsibility follows the service that actually collects and controls the data.
Technical data used to deliver and protect pages
When a browser requests a page, the hosting environment may process an IP address, request time, requested path, response status, browser or device information and referring address. These technical records can be necessary to deliver content, diagnose errors, maintain security, prevent abuse and understand aggregate performance. The exact hosting configuration and retention are controlled by the deployed environment rather than by the visual theme alone.
Technical logs should be limited to what is reasonably necessary, protected from unauthorised access and retained only as long as required for the stated operational or legal purpose. They should not be combined with external gaming-account credentials because this website does not need those credentials. The site owner should review host settings, access permissions, backups and deletion schedules after deployment and whenever the hosting provider changes.
- Requests can create server logs
- Logs support delivery and security
- Access and retention should be limited
- No need to add gaming credentials
A web server needs enough information to answer a request, but that does not justify collecting unrelated account secrets.
Analytics and measurement
The published theme includes a third-party analytics script loaded from node90.aizhantj.com. When it loads, that provider may receive technical information such as the visitor’s IP address, browser, referring page and the address being viewed, and it may use cookies or similar storage depending on its current implementation. This independent site does not control the provider’s infrastructure or policy.
Visitors who do not want third-party measurement can use browser privacy controls, content blocking or leave the site before continuing, subject to local law and browser capability. The site owner should verify the analytics provider’s identity, terms, retention, transfer locations and consent requirements before public deployment and should disable the script where it cannot be operated lawfully. Analytics should be used for aggregate site understanding, not to request gaming credentials.
- A third-party measurement request is present
- The provider may receive browser and network data
- Browser controls may restrict measurement
- Deployment requires a current compliance review
Analytics is a separate data recipient and should be assessed as such, even when no contact form is present.
Cookies, local storage and external pages
The public theme does not intentionally set a language-preference cookie. WordPress core, installed plugins, hosting security or the analytics provider may set cookies or similar identifiers depending on configuration and visitor action. Logged-in administrators can receive WordPress authentication cookies. If comments or other interactive features are enabled later, additional data and cookies may apply and the relevant notice should be updated before collection.
External links lead to separately operated pages that can set their own cookies, measure referrals and collect account or payment information under their own policies. This website cannot view or delete data stored solely by an external service. Visitors can review and clear browser cookies, block third-party storage or use private browsing, although some site or external-service functions may then work differently.
- No theme language cookie is intentionally set
- WordPress and providers may set technical cookies
- External pages have separate storage
- Browser controls can remove or block data
The cookie policy describes storage in more detail; external-service cookies remain outside this site’s control.
Data sharing, security and retention
Technical data can be processed by the hosting provider, security services and the identified analytics provider as needed to deliver their functions. It may also be disclosed when required by valid law or to protect the website and users from abuse, subject to applicable safeguards. The site does not sell a visitor’s 77Bet password or payment credential because it has no legitimate reason to collect either.
No internet transmission or storage method is completely secure. Reasonable measures include updates, limited administrative access, strong credentials, encrypted connections, backups and incident review. Retention should be tied to a documented purpose and removed or anonymised when no longer needed. A public policy cannot substitute for checking the real server, plugin and vendor configuration; the deployed behaviour must match the notice.
- Service providers process limited technical data
- Valid legal requests may require disclosure
- Reasonable safeguards reduce but do not remove risk
- Actual configuration must match this notice
Privacy promises should describe deployed behaviour, not only the intention of a theme file.
Visitor rights, children and policy updates
Depending on location, a visitor may have rights to ask about personal data, request access, correction, deletion, restriction or objection, or complain to a relevant authority. The responsible recipient is the organisation controlling the specific data. For external 77Bet account data, use the controller identified in the external service’s current policy. This website cannot fulfil a request for data it never receives or controls.
The site is not intended to encourage underage gaming. Minors should not submit personal information or attempt to access age-restricted external services. This policy may change when vendors, technical features or law change; the published version should include a current review date. Because this release has no public contact form or email, the site owner should add a verified privacy-contact route before relying on direct visitor submissions.
- Rights depend on applicable law
- Send requests to the actual controller
- Minors should not access age-restricted services
- Update notice when collection changes
A privacy request succeeds only when it reaches the organisation that controls the relevant data.
Data-context summary
| Context | Possible data | Controller or recipient |
|---|---|---|
| Public page request | IP, time, path and browser details | Hosting and security providers |
| Analytics request | Network, browser, referral and page details | Identified analytics provider |
| WordPress administration | Login and authentication cookies | Independent site owner and host |
| External 77Bet service | Account, identity and transaction data | External service under its policy |
| Payment provider | Financial and transaction data | Selected provider under its policy |