Kiwi Casino TillView 22BETPrivacy policy: how Kiwi Casino Till handles information
TOP 1
22BETCasino and sports
★★★★★4,889 reviews
18+ · Offer terms ›
Availability, eligibility, qualifying deposits, wagering, games, maximum bet, expiry and withdrawal rules are controlled by the operator's current terms.
This privacy policy describes the mechanisms implemented in the current Kiwi Casino Till website, rather than the practices of an external casino. The pages are static, assets are served locally and there is no registration, document-upload or payment form operated by this site. A small browser script manages promotions, and the server-side referral handler records a limited click event on the website server.
- Implemented browser and referral fields are described explicitly
- Click-event fields and ordinary hosting logs are described separately
- Operator records are separated from editorial-site records
- Understand which organisation this policy covers
- Know what the browser script stores
- Read the referral event fields accurately
- Separate site code from hosting and provider records
- Manage privacy requests using relevant information
- Review changes and keep credentials out of this site
- Questions and answers
- Related guides
Understand which organisation this policy covers
Kiwi Casino Till is an informational website, not an operator account system. This policy covers the page scripts and referral handler supplied with this release.
It does not describe a casino's identity checks, game records, banking information or customer-service database. Following an external link creates a separate relationship with the destination.
Read that organisation's policy before submitting information there. A referral does not give this editorial website access to the resulting account or make it a processor of the operator's verification documents.
Know what the browser script stores
The script uses browser sessionStorage to remember the selected compact promotional format and whether an offer has been shown or dismissed. The formats share this frequency control.
This supports the behaviour that a dismissed promotional format does not repeatedly reappear during the same storage session. Browser session storage has its own lifecycle and controls.
Clearing it can reset the promotional state, but it does not remove server-side records created by a separate request. Shared-device users should also consider the browser's ordinary history and session behaviour.
| Mechanism | Data in this release | Location or role |
|---|---|---|
| Promotion state | ktpromo value selecting a format or closed status | Browser sessionStorage |
| Referral event | Time, offer label, placement label and page label | Private server-side JSON-line journal when the handler runs |
| Address-derived value | Unsalted SHA-256 of the handler's remote-IP value | Referral journal; not guaranteed anonymous |
| Ordinary hosting logs | Depend on the chosen host and configuration | Not defined by the static page script |
Read the referral event fields accurately
The deployed referral handler accepts a known offer ID, a placement label and the source-page path. It writes an event with a UTC time and those labels to the server error log when an ordinary referral click occurs.
The referral service records the event time, offer ID, placement and source-page label. It does not add an IP-derived identifier to that click-event record. Ordinary access and security logs at the hosting layer are separate.
These labels describe the referral placement. They do not contain an operator password, an identity document or a payment-card number. Hosting access logs remain a separate source of technical request information.
Separate site code from hosting and provider records
Serving a page necessarily involves requests to a host, which may retain ordinary access or security logs according to its configuration.
The supplied static-page code does not establish the hosting provider's retention period, location or access practices. The current source loads fonts, photographs and scripts from the same site rather than third-party content delivery or analytics domains.
A host, proxy or later integration can change the deployed behaviour, so this policy needs review when the implementation changes.
| Action or question | What it affects | What it does not establish |
|---|---|---|
| Clear browser session storage | Local promotional state | Deletion of separate server records |
| Follow a configured referral | A request to the handler and then the destination | Shared access to the destination's private account database |
| Ask about a site record | Information held by the publisher | Operator authority over independent publisher logs |
| Read this source release | Implemented local mechanisms | A verified description of future hosting or integrations |
Manage privacy requests using relevant information
New Zealand privacy guidance explains rights to request access to personal information and seek correction. The appropriate first recipient is the organisation holding the records.
An operator account team cannot necessarily identify or amend an independent publisher's referral journal. For a site-record query, describe the relevant page or referral event and approximate time without initially sending identity documents.
Any identity check should be proportionate to finding and protecting the requested information. A general request does not justify collecting an unrelated bundle of private files.
Review changes and keep credentials out of this site
This policy should change when data fields, integrations, storage purposes or hosting arrangements change. A revised date alone does not make an outdated technical description accurate.
The implemented behaviour and the published explanation should remain consistent. This policy was checked against the supplied code on 21 October 2026.
It describes the limits of that release without inventing a corporate address, retention duration or external provider practice that has not been configured or verified.
Practical strengths and limits
- Implemented browser and referral fields are described explicitly
- Click-event fields and ordinary hosting logs are described separately
- Operator records are separated from editorial-site records
- Publisher privacy contact details are not configured in the local release
- No automatic server-journal deletion period is implemented
- Hosting and external-destination practices require their own disclosures
Questions about privacy policy
Does this website create a casino account for me?
No. The supplied site is informational and has no operator registration system. Account details entered at an external destination belong to that separate relationship. This policy does not describe or administer the destination's private account records.
What does promotion session storage contain?
It contains the selected promotional-format label or the closed state used by the local script. It is stored in browser sessionStorage. It is not a casino credential, document record or copy of an operator balance.
Does clearing browser storage erase referral logs?
No. Browser state and a server-side journal are different storage mechanisms. Clearing the local promotion value can reset display behaviour without deleting an event previously written by a configured referral handler.
Are external analytics or advertising pixels included in the supplied pages?
The current source does not include them and serves its assets locally. A later host integration or code change can alter deployed behaviour. The policy must be updated if another collection mechanism is introduced.
How long are referral records automatically retained?
The current code does not implement a scheduled deletion period. A fixed number of days would therefore be an invented promise. The public publisher must configure and disclose the actual retention and deletion arrangements for its deployment.
Can I send verification files to this site for privacy or account help?
Do not send operator identity or banking documents here. The site has no verification-upload service. A privacy query should begin with a description of the relevant site record and use the publisher's properly configured contact process.
Where can I read independent information about New Zealand privacy rights?
The Office of the Privacy Commissioner publishes guidance on access and correction. That resource explains general rights; it does not administer this site's records or replace the need for an identified publisher contact route.