Information processed during normal website use
When you visit a website, the web server may receive technical request data such as IP address, browser type, requested page, time of request, referring page and response status. These logs are commonly used for site delivery, security, troubleshooting and traffic analysis. The exact retention period depends on the hosting and server settings in use.
This site does not need an external 200SR account password, OTP, bank password or payment PIN in order to display its public information pages.
Cookies and local browser storage
Website software, analytics tools or embedded services may use cookies or similar browser storage when those features are enabled. Cookies can be used for session behaviour, preferences, security or traffic measurement. Browser settings normally allow you to remove or restrict cookies, but blocking all cookies can change how some pages function.
This site does not use a language-preference cookie because its public pages use English (Philippines).
Traffic measurement
The site may load traffic-measurement technology to understand page requests and general site usage. Such technology can receive technical information associated with a web request. The privacy terms of any analytics or statistics service in use should be reviewed, and this policy should be updated if the site's data practices change materially.
External links
Some links can take you to an external service. Once you leave this site, the external site's own privacy practices apply. This Privacy Policy does not describe how another service handles account registration, identity verification, payments, transactions or account records.
Before submitting sensitive information to an external service, verify that you intended to open that service and review its current privacy information.
Information you choose to provide
If a contact feature is added later, the page should state what information is collected, why it is needed and how it is handled. Do not include passwords, OTPs, bank passwords, card PINs or unnecessary identity data in a general website-feedback message.
No public contact form or email address is listed here. If a contact route is added later, this policy should be updated to explain what information that route collects and why.
Security and retention
Reasonable security practices can reduce risk but no public website can promise absolute security. Server logs, backups and analytics data should be limited to what is needed for the actual operation. Retention should be reviewed against the hosting setup and applicable requirements.
Changes to this policy
This page should be reviewed when the real site adds or removes material tracking, contact forms, analytics services or other data-processing features. A cosmetic CSS change by itself does not automatically mean the privacy content has changed.
Browser controls and your choices
You can use browser controls to review stored cookies, clear site data and limit certain tracking features. Blocking every script or cookie can also stop legitimate site functions, so changes should be made with an understanding of what the browser setting does. Private-browsing modes can reduce local history but do not make a request invisible to the website, network provider or external service.
When you follow a link to another domain, that destination can receive normal request information and will apply its own privacy rules. Review the destination before entering personal or account information.
Children, age eligibility and sensitive data
This information site is not designed to collect sensitive account credentials from visitors. Gaming-related services can have age restrictions, and visitors should follow the applicable age and local requirements for any external service they use. If a person is not eligible to use a service, this site should not be treated as a way around that restriction.
If personal information is accidentally submitted through a future contact feature, requests should be handled according to where the information is actually stored, how long it is retained and the applicable requirements rather than relying on a generic deletion promise.