Privacy Policy

A detailed explanation of how A Big Candy handles account, Inclave, payment, verification, device, support and responsible gambling information.

Visit A Big Candy
Policy scopePlayers and website visitors
RegionAustralia
Updated21 November 2026

This Privacy Policy explains how A Big Candy handles personal information when someone visits the casino website, creates or accesses an account, plays a game, claims a promotion, uses the cashier, contacts support or activates a safer-gambling control. It is intended to make the data flow understandable before a player submits information. The policy should be read together with the Terms and Conditions and any notice displayed at the point where information is requested.

Scope and responsibilities

This policy covers personal information handled through A Big Candy pages, account functions, casino games, promotional tools, cashier features and support channels. It applies to visitors, registered account holders and people who contact support even if they do not complete registration. It also applies to security and fraud-prevention records generated while the service is used.

Some functions are delivered with specialist providers. Inclave supplies the access layer used during registration and login, game studios supply casino software, and banks or payment processors complete transactions. Those organisations may process information under their own privacy notices as well as under instructions connected with A Big Candy. A player should review any notice shown by a provider before sending information directly to it.

A Big Candy does not need a player to disclose a password, full card security code or cryptocurrency recovery phrase to support. Those details should never be included in chat messages, screenshots or email attachments.

Information we process

The type of information processed depends on whether a person is browsing, opening an account, using the cashier or asking for help. Not every category is collected from every visitor.

ActivityInformation that may be involvedOperational reason
Visiting the websiteIP address, request time, browser, device, operating system, language, referring page, cookie identifiers and pages openedDeliver pages, remember settings, measure reliability and detect abusive traffic
Opening an accountName, date of birth, address, email, telephone number, country, username and Inclave-linked account referenceCreate the account, confirm eligibility and maintain a unique player record
Playing casino gamesGame selected, stakes, wins, losses, round identifiers, timestamps, balance changes and bonus contributionRun games, settle rounds, calculate wagering and investigate disputed play
Using the cashierDeposit and withdrawal amounts, currency, method, masked payment identifiers, transaction status and provider referencesComplete payments, reconcile the account and prevent financial abuse
Completing verificationIdentity document, selfie where requested, proof of address, payment ownership evidence and verification resultsConfirm identity and age, protect the account and review withdrawals
Contacting supportMessage text, account details supplied by the player, attachments, call or chat metadata and correspondence historyAnswer the enquiry, investigate an issue and preserve an accurate service record
Using safer-gambling toolsLimits, exclusion requests, risk indicators, welfare communications and actions taken on the accountApply requested controls and respond to signs of harmful play

Information supplied directly

Most account information comes from the player during registration, verification, cashier use or a support conversation. Players are responsible for keeping their contact and residential details current. Supplying inaccurate information can delay security checks and may prevent a payment from being completed.

Information created through use

Game history, balance movements, bonus progress, login events and security records are generated when the service is used. These records help reconstruct what happened if a round is interrupted, a balance is disputed or suspicious access is detected. Server and device information may also be compared across sessions to protect the one-account rule.

Information received from providers

A payment processor may return a transaction result, a verification service may report whether submitted evidence passed its checks, and Inclave may confirm an authentication event. A Big Candy aims to receive only the information reasonably needed to operate the relevant function and keep an auditable account record.

Why information is used

Personal information is processed to provide requested casino services, administer the player relationship, protect accounts and transactions, comply with applicable duties and improve the reliability of the platform. Depending on the context, processing may be necessary to perform the player agreement, respond to a request, meet a legal obligation, protect legitimate security interests or act on consent.

  • Account administration: creating the player record, maintaining account settings, confirming email details and restoring access.
  • Casino operation: recording wagers, settling game rounds, updating balances and calculating promotion requirements.
  • Payments: authorising deposits, reviewing withdrawals, reconciling transactions, handling reversals and detecting misuse.
  • Security: identifying suspicious access, duplicate accounts, payment abuse, automated activity and attempts to exploit technical errors.
  • Support: responding to questions, recording agreed actions and investigating account, game, bonus or cashier complaints.
  • Safer gambling: operating limits and exclusions, assessing risk signals and documenting player-protection decisions.
  • Service communication: sending essential notices about access, verification, transactions, policy changes and security events.

Inclave registration and login

A Big Candy uses Inclave for account access. An Inclave login can connect a verified email-based identity with the casino account without requiring support to know the player's password. Authentication events, account references and security status may be exchanged as needed to complete sign-in, prevent unauthorised access and recover an account.

Players should protect the email account connected to Inclave, use a unique password and review unexpected verification messages immediately. More practical access and recovery information is provided in the login guide. If access appears compromised, the player should contact support before continuing to deposit or play.

Payments, withdrawals and KYC checks

Cashier records connect transactions to the relevant player account. Depending on the method, a processor may receive the account name, amount, currency, payment reference, billing data and technical signals needed to approve or reject the request. A Big Candy generally stores provider references and masked identifiers rather than credentials that should remain with the payment provider.

Identity and payment ownership checks can be required before a withdrawal is released or when activity needs additional review. A request may include a government-issued identity document, recent proof of address, evidence that a payment method belongs to the account holder and clarification of unusual transactions. Submitted files should be current, legible and limited to what was requested. The withdrawal guide explains how these checks affect processing.

KYC material is used for verification, fraud prevention, payment review and dispute handling. It is not used as promotional artwork or published in player-facing areas. Access should be limited to authorised personnel and providers who need the material for the review.

Cookies and similar storage

Essential cookies or local storage may keep a session active, remember a security choice, route traffic correctly and preserve language or display settings. Without these technologies, login and cashier features may not work reliably. Performance information may also be used to understand errors, loading times and navigation patterns.

Where a non-essential cookie requires a choice, the available control should be shown before that cookie is activated. Deleting browser storage can sign a player out and remove saved preferences, but it does not erase account, transaction or game records held separately.

When information may be shared

Personal information is not made public simply because someone holds an account. It may be disclosed to carefully selected recipients where disclosure is necessary for a defined operational, security or legal purpose.

  • Inclave and other identity or authentication providers supporting account access;
  • game studios and platform suppliers recording and settling casino rounds;
  • banks, e-wallets, voucher services and payment processors completing cashier requests;
  • identity, age, address, fraud and payment-ownership verification services;
  • hosting, security, analytics, communications and customer-support providers;
  • professional advisers, auditors, insurers and dispute-resolution specialists;
  • regulators, courts, law-enforcement bodies or other authorities where disclosure is required or lawfully requested;
  • a successor organisation if the service is reorganised, provided appropriate safeguards continue to apply.

Providers should receive only the information required for their role and be subject to confidentiality, security and use restrictions. When processing crosses national borders, contractual or other appropriate measures should be used where required to protect the information during transfer.

How long records are kept

There is no single retention period for every record. Session and diagnostic data may be needed briefly, while account, transaction, KYC, exclusion and dispute records may need to remain available for a longer period. The period is assessed according to the purpose of collection, the sensitivity of the information, fraud and chargeback risk, limitation periods and applicable record-keeping duties.

Closing an account does not necessarily delete every record immediately. Information needed to enforce an exclusion, complete a pending withdrawal, answer a complaint, defend a legal claim or meet a record-keeping duty may be restricted and retained until that purpose expires. When a record is no longer required, it should be deleted, anonymised or otherwise placed beyond ordinary operational use.

Security and incident response

Administrative, technical and organisational controls are used to reduce the risk of unauthorised access, alteration, disclosure or loss. Measures can include access restrictions, authentication controls, encrypted transmission, logging, provider assessment, monitoring, staff procedures and tested recovery processes. No website or transmission method can promise absolute security, so players also have an important role.

  • Use a password not shared with another service and protect the connected email account.
  • Sign out on shared devices and do not save credentials in a public browser.
  • Check the address bar before entering account or payment information.
  • Do not send one-time codes, card security codes or recovery phrases to anyone claiming to be support.
  • Report unexpected login messages, account changes or transactions promptly.

If a personal-information incident occurs, it will be investigated, contained and documented. Affected people and relevant authorities will be notified where the nature of the incident and applicable requirements call for notification.

Responsible gambling and sensitive circumstances

Requests for deposit limits, cooling-off periods or exclusion are treated as account-protection instructions. Related information can include the requested control, its duration, communications with the player and risk signals observed through account activity. It may be used to apply restrictions, prevent a new account from bypassing an exclusion and train authorised teams to respond consistently.

Players should avoid including unrelated medical, financial or family details when a concise request is sufficient. If sensitive information is voluntarily provided because it is relevant to a welfare concern, access should be restricted and the information used only for player protection, compliance and appropriate follow-up.

Service messages and marketing choices

Essential account messages can be sent even when a player does not want promotional communication. These include security alerts, verification requests, transaction updates, changes affecting the account and responses from support. Promotional email or other marketing should provide a practical way to opt out. An opt-out may take a short period to apply and does not prevent essential service messages.

Protection of minors

A Big Candy is intended only for adults who are legally permitted to gamble. The service is not designed to collect personal information from minors. If an underage person has created an account or submitted information, support should be notified so access can be blocked, the circumstances reviewed and the information handled in line with legal and security requirements.

Access, correction and other privacy requests

Depending on the law that applies, a person may ask for access to personal information, correction of inaccurate details, deletion of eligible records, restriction of certain processing, an explanation of processing, withdrawal of consent or review of a decision. A request can be limited where disclosure would expose another person's information, undermine security or fraud controls, or conflict with a legal retention duty.

Before acting on a request, support may need to verify the requester's identity. This protects the account from someone attempting to obtain or alter another player's information. A request should identify the account, explain the action sought and provide a safe contact method. Passwords and full payment credentials should not be included.

Questions, complaints and policy updates

Privacy questions or complaints can be submitted through the authenticated support channel. The message should state that it concerns privacy and describe the relevant account activity, date and requested resolution. Privacy enquiries can also be sent to [email protected].

A complaint will be reviewed using available account, transaction, support and security records. If the response does not resolve the concern, the player may ask what further review or external complaint option is available in the circumstances.

This policy may be updated when the website, providers, legal requirements or operational practices change. The date at the top identifies the current version. Material changes should be communicated through an appropriate website or account notice before they take effect where required.