Cookie Policy
Understand which cookies or similar technologies may appear on the independent website, why providers use them, how external destinations differ and which browser controls are available.
What cookies and similar technologies do
A cookie is a small piece of data that a website or service can ask a browser to store and return on later requests. Similar technologies include local storage, session storage, pixels and identifiers attached to network requests. They can support authentication, security, preferences, measurement and service performance. A cookie name alone does not explain its full purpose; the setting domain, duration and data use also matter.
This policy applies to storage and measurement associated with the independent pages on this domain. It does not govern cookies placed after a visitor follows an external link to a 77Bet-related service, payment provider or another website. Those destinations choose their own technologies and purposes. Visitors should read the policy and settings shown by the destination before entering account or financial information.
- Cookies store or return small values
- Similar technologies can measure requests
- Purpose depends on domain and use
- External destinations have separate policies
A browser can visit several data controllers in one journey; each domain’s storage should be evaluated separately.
Cookies used by the public theme and WordPress
The public theme does not intentionally create a language-preference cookie; English and Hindi are represented by their page addresses. It also does not operate a visitor account, gaming login, shopping basket or contact-form session. A normal anonymous page view therefore does not need a theme-specific authentication cookie. This description concerns the supplied theme and may change when a host or site owner adds plugins or features.
WordPress core sets authentication and settings cookies for administrators and other logged-in site users. If comments are enabled, WordPress may offer cookies that remember commenter details. Security, caching, accessibility or consent plugins can introduce additional storage. The deployed cookie list should be checked after every plugin or hosting change, because a policy written from theme files cannot see behaviour added later by the running environment.
- No theme language cookie is intended
- Anonymous views need no theme account session
- WordPress administrators receive core cookies
- Plugins and host features can add storage
The actual running site—not only the theme—determines the final cookie inventory.
Third-party analytics technology
The theme includes an analytics request to node90.aizhantj.com. The provider can receive the browser request, IP address, referring information and viewed page, and may set or read cookies or other identifiers according to its current implementation. This site does not control that provider’s infrastructure. The provider’s current terms, storage duration, transfer locations and opt-out mechanism should be assessed before public use.
Where applicable law requires consent before non-essential measurement, analytics should not run until valid consent has been obtained. A consent choice should be as easy to refuse as to accept and should remain available for later change. If the provider cannot be documented or configured consistently with the published notice, the site owner should disable it. Analytics should never request a 77Bet password, OTP, bank PIN or payment credential.
- A separate analytics domain receives a request
- Cookies or identifiers may be used
- Consent requirements depend on applicable law
- Undocumented measurement should be disabled
Measurement is not automatically essential merely because the script is bundled with a theme.
External-service cookies are separate
An external 77Bet-related destination may use cookies for account sessions, security, personalisation, product operation, promotion attribution and measurement. A payment provider may use additional authentication and fraud-prevention technology. This independent website cannot list, change or delete storage controlled solely by those services. A visitor who signs in externally should use the privacy and cookie controls published by that operator.
Referral information can be passed in an ordinary browser request when moving between sites, subject to browser and site policy. The independent website uses a restrictive referral policy on its local transition, but visitors should still review the final destination and avoid placing sensitive information in a page address. An external prompt to enable every cookie does not remove the visitor’s ability to examine the available choices.
- External accounts use their own session storage
- Payment providers have separate security technology
- This site cannot remove external cookies
- Review choices at each destination
Leaving this domain changes both the service and the party responsible for its cookies.
Browser controls and their effects
Most browsers allow a visitor to view stored site data, delete it, block third-party cookies, restrict tracking or clear data when the browser closes. Private-browsing modes can reduce persistence on the local device but do not make a visitor invisible to the network, host or destination. Content blockers may prevent some measurement requests. Instructions and available controls differ by browser version and device.
Blocking essential authentication storage on an external account can sign the visitor out or prevent a feature from working. That technical effect does not mean all non-essential cookies must be accepted. Visitors can make a more precise choice by reviewing storage per site and clearing data after using a shared device. Browser synchronisation should also be considered, because stored history or settings may be copied to another signed-in device.
- View and delete data per site
- Block third-party tracking where desired
- Understand private browsing limits
- Clear shared-device data and review sync
Privacy controls can change functionality, but functionality and consent remain distinct questions.
Retention, updates and contact limits
Cookie duration can be limited to a browser session or continue for a stated period. The party setting a cookie determines that duration and should keep it no longer than needed for the declared purpose. Analytics and WordPress settings should be reviewed against the actual browser storage panel and vendor documentation. Expired or unused identifiers should not be retained merely because they were once configured.
This policy should be updated when analytics, plugins, consent tools or interactive features change. The current release does not publish a public email or contact form, so visitors should not send browser exports or account screenshots to an address found elsewhere. A future privacy channel should be visibly published on this domain and explain how requests are verified. External-service cookie questions belong to the controller identified in that service’s policy.
- Duration should match purpose
- Review real browser storage
- Update policy after technical changes
- Send requests to the actual controller
A useful cookie notice is a current inventory of deployed behaviour, not a permanent generic statement.
Cookie and storage overview
| Source | Likely purpose | Visitor control |
|---|---|---|
| Public theme | No intentional language or account cookie | Navigate or clear site data |
| WordPress core | Administrator authentication and settings | Sign out and clear browser storage |
| Installed plugins or host | Security, cache, consent or added features | Use notice and browser controls |
| Analytics provider | Traffic and performance measurement | Consent choice, blocking or opt-out |
| External services | Account, product, payment and measurement | External policy and settings |