Public reading does not require you to submit account credentials
The public information pages do not need your PlayNow password, OTP, bank password, card PIN or identity document. Normal web requests can still create technical records such as IP address, browser information, requested URL, time and response status through the server or security infrastructure.
Server and security logs
Web servers commonly record technical request information so pages can be delivered, errors investigated and abuse controlled. Depending on the hosting setup, this can include IP address, user agent, requested path, referrer, timestamp and HTTP status. These logs should be kept only as long as needed for operational, security or legal purposes.
Cookies and local browser storage
The website, security tools, performance tools or enabled site features may use cookies for session behaviour, preferences or administration. Public visitors should not assume every cookie is necessary for the same purpose. Browser settings can be used to inspect, block or delete cookies, but strict blocking may affect functionality on some pages.
This policy does not claim the presence of a specific advertising, CRM or customer-database system unless one is actually enabled.
Analytics and the statistics script
This website loads a statistics script that can send technical visit information to its analytics endpoint. The exact data received is determined by that script and the browser request. If analytics settings or providers change, the deployed privacy notice should be reviewed so it remains consistent with the actual site behaviour.
External links and separate privacy practices
When you follow the primary access action or another external destination, you leave this information website. The external service may have its own cookies, account data, payment processes, support systems and privacy policy. Read the privacy notice of the destination before submitting personal information there.
Data minimisation
Do not send sensitive account information merely to describe a public-page problem. A useful technical report normally needs the page name, browser, device type, approximate time and non-sensitive error wording. Passwords, OTPs, card PINs and identity documents are not needed for that purpose.
Your browser choices
- Use browser controls to inspect or clear cookies and site data.
- Use private browsing when appropriate, while remembering that strict privacy settings can affect sessions.
- Avoid saving account passwords on shared devices.
- Remove personal information from screenshots before sharing a technical problem.
- Review external privacy notices before entering account or payment data.
Children and age-restricted services
This website is intended for general information about access and use. Services involving wagering or age restrictions should only be used by people who meet the applicable age and local requirements. Do not use another person's identity or account to bypass an age rule.
Policy changes
This policy should be updated when the website's actual data practices materially change. A design or styling change by itself is not a reason to claim a new privacy practice. Visitors should read the current version available on this page.
Questions about privacy
Use Contact for questions about this website's public pages and privacy wording. For data held by an external account service, use the privacy or support route supplied by that service.
Retention and access should follow the actual hosting setup
Technical logs may be retained by the hosting provider, security layer or analytics service according to their configuration. This website should not claim a fixed retention period unless one has actually been configured and documented. Administrative access to logs should be limited to people who need it for operation, security or legal obligations.
External analytics and hosting can involve other jurisdictions
Internet infrastructure may process technical data outside the visitor's immediate location. When an external provider is used, its own terms and privacy practices can affect processing. Visitors who need detailed information about an external provider should review that provider's published privacy information.
Do not send sensitive information through ordinary page feedback
Privacy risk often comes from sending too much information, not only from website tracking. If you report a broken page, send only what is needed to reproduce the problem. Avoid attaching identity documents, payment records or account credentials unless you are using a verified service process that specifically requires them.