Zizo Bet Privacy and Player Information
We use player information to operate an account experience that includes deposits, withdrawals, bets, net position, and support conversations. We keep the purpose of that information practical: account activity needs a record, a first withdrawal needs KYC verification, and a support request needs enough context for our team to understand it.
We also treat privacy as part of account care. Our service offers two-factor authentication, and we encourage players to keep passwords and authentication codes private. A player can use account history to recognise deposits, withdrawals, bets and net position, then raise a focused question through our support routes when needed.
Your choices over personal information
We want players to have a clear route for privacy requests.
- We accept a request through our support routes when a player wants to raise an account-information question.
- Account activity records help a player recognise a deposit, withdrawal, bet, or net position.
- We keep security-minded communication focused on the account matter without asking for passwords or authentication codes.
Our 24/7 live chat and email routes offer a way to describe a privacy concern or an account-information question. A concise request with the account context and date of the relevant activity helps us identify what the player means.
How we use account information
Account activity and payments
We use account activity information around deposits, withdrawals, bets and net position. Payment activity needs a record so a player can follow the account journey. A first withdrawal includes KYC verification, which connects verification information to a payout request.
Player support and communication
Support requests give us the details needed to understand the issue presented. A player may include the date, time, currency, amount, and payment category for a payment question. That context helps our team separate a withdrawal question from a bonus or account-access question.
Responsible-play settings and choices
We use the settings selected by a player for deposit, loss, wager or session limits. Cooling-off and self-exclusion choices also relate to the account controls a player has selected. These settings support a controlled approach to gambling as entertainment.
How policy changes are communicated
Clear wording for policy updates
We keep privacy information in plain language so a player can understand the account context behind it. When we update our wording, we aim to make the current version easy to identify through its visible update date.
Retention and account records
Activity history for account records
Our account activity guidance covers deposit, withdrawal, bet and net-position history. This history gives a player a practical record for reviewing a session or explaining a support question.
Information we collect for account care
We may collect account and transaction information connected to deposits, withdrawals, bets and net position. We may also receive the details that a player places in a live-chat or email request. When a player chooses a limit, cooling-off period or self-exclusion, that selected control becomes part of the account’s responsible-play setting.
Sharing information for our service
We use payment routes and game providers as part of the player experience. A payment method has its own operational role, while a game provider supplies a particular gameplay format.
Security in our account experience
We offer two-factor authentication as an added account-protection measure. We encourage players to keep passwords and authentication codes private, use a secure personal device and review activity history for unfamiliar events. Our team can use live chat and email to discuss an account matter, but a player should not include secret sign-in credentials in a message.
Last updated: 12 November 2026