What cookies are
Cookies are small browser files used for different website functions
Cookies are small text files or similar browser storage mechanisms that can be created when a website loads. They can last only for a browser session or remain for a longer period. Different cookies serve very different purposes, so it is not accurate to treat every cookie as advertising or every cookie as harmless.
Some cookies are purely functional
Session or security cookies can help a website remember a technical state, protect a form or keep navigation working. Depending on what they contain, they may not identify an individual.
Some cookies can involve personal data
The Personal Data Protection Commission notes that the PDPA can apply when cookies collect, use or disclose personal data. The more information linked to a persistent identifier, the more important transparency and consent choices can become.
Cookies can be first-party or third-party
A first-party cookie is set in connection with this website's domain. A third-party service embedded or linked through the site can set or read its own identifier subject to browser rules, consent settings and that third party's practices.
Similar technologies
Local storage, pixels, referral parameters and server-side identifiers can serve functions similar to cookies. This policy uses “cookies” broadly where appropriate for readability.
Consent choices
How users can manage cookies
Site consent controls
Where the site deploys a consent-management interface, use it to accept, reject or change optional cookie categories. Essential technical cookies may remain necessary for core functionality.
Browser settings
Most browsers let users block, delete or limit cookies. Blocking all cookies can affect website functions, saved preferences or attribution. Browser instructions vary by device and software version.
Private browsing and storage clearing
Private-browsing modes can limit how long some local data remains, while manually clearing cookies removes stored identifiers from that browser. These controls do not necessarily prevent server logs or all forms of third-party tracking.
Do Not Track and similar signals
Browser privacy signals are not implemented uniformly across every service. Where applicable, the site and its providers should follow legal and platform requirements relevant to the signal.
Affiliate cookies
What can happen when you click a casino link
Some outbound casino links can contain an affiliate identifier. The destination or an affiliate network may use a cookie or another identifier to record that the referral originated from PayNow Casinos Singapore.
Affiliate attribution is commercial, not editorial evidence
A tracking relationship does not mean the casino is approved, safe or guaranteed to pay. Our affiliate disclosure explains the commercial model.
Tracking duration varies
Different partners can use different attribution windows. Because relationships can change, this policy does not invent one universal duration for every casino link.
Casino cookies are governed by the destination
Once you leave this site and visit a casino, that casino's cookie and privacy practices apply. Review its policy before creating an account or submitting KYC.
Cookies do not require banking credentials
Cookie or affiliate attribution never requires you to send this site a PayNow OTP, banking password or casino password.
Analytics & measurement
Why a site may measure usage
Analytics can help identify whether important pages load, whether users find internal links, which device types experience layout issues and which content receives little engagement. The goal should be site improvement rather than collecting unnecessary personal information.
Data minimisation
Where practical, measurement should be configured to collect only information reasonably needed for the purpose. Persistent identifiers and detailed behavioural profiles can create greater privacy implications than basic aggregated metrics.
Vendor changes
WordPress plugins, analytics vendors and security services can change over time. The site's actual cookie inventory should be reviewed when material services are added or removed.
Why this policy does not list invented cookie names
A static list copied from another website would be misleading. Cookie names and durations should reflect the services actually deployed. This policy therefore explains categories, while the site's active consent tool or cookie scan should provide the current technical inventory where required.
Relationship with the Privacy Policy
For broader information about contact data, technical logs, third-party services, retention and privacy requests, read the privacy policy.
Implementation examples
How cookie categories can appear on a WordPress comparison site
Essential WordPress or security state
A security, consent or session mechanism can need a temporary identifier to protect forms, remember a consent choice or distinguish legitimate traffic from automated abuse.
Analytics measurement
An analytics service can record that a page was viewed, what device category was used or how navigation moved between pages. Whether that information is personal data depends on the identifiers and other information involved.
Affiliate attribution
A referral parameter can be passed to a casino link, and the partner can set its own identifier after the click. That process should be considered separately from site analytics because it has a commercial attribution purpose.
Why a periodic cookie scan is useful
Plugins can add or remove cookies without obvious visual changes to the site. A periodic technical review helps keep the public policy and consent interface aligned with the actual deployment rather than an outdated template.
