Dear Matej,
Dear Casino Guru team,
Further to our previous response, we would like to provide a clear technical explanation regarding the deposit confirmation email referenced by the player.
How deposit confirmation emails are generated
BitGuruz operates on a blockchain-based deposit architecture. Deposit notification emails are generated by an automated system event, not by manual approval or active acceptance by the casino.
Specifically:
when a cryptocurrency transaction is detected on the blockchain to an address that was previously associated with a player account,
the system automatically registers the on-chain confirmation event (e.g., network confirmations),
and a system-level notification email may be triggered to inform the user that a transaction has been detected on the blockchain.
This process is purely informational and reflects:
a blockchain confirmation,
not an approval of gameplay,
not account reactivation,
and not acceptance of funds into an active player balance.
Account status vs. blockchain notifications
It is important to distinguish between:
account status (open / closed / self-excluded), which is enforced at platform level, and
blockchain events, which occur independently of account status.
Once the player’s self-exclusion was applied and the account closed:
the account could not be used to play;
deposits were not credited to an active balance;
no wagering activity was possible.
However, blockchain networks do not recognize concepts such as "self-exclusion" or "account closure". Any transfer initiated by the sender will still:
be confirmed by the network,
be visible on the blockchain,
and may trigger automated system notifications.
Why this does not constitute a breach
The presence of an automated email:
does not mean the casino allowed a deposit,
does not override self-exclusion,
and does not indicate operational acceptance of funds.
The casino did not enable deposits, did not prompt the transaction, and did not provide gameplay access after the self-exclusion was applied.
Preventive measures
We acknowledge that such automated notifications can cause confusion in self-exclusion cases. As part of ongoing system improvements, we are reviewing:
clearer wording of blockchain notification emails,
additional safeguards to suppress non-actionable emails for closed accounts.
Conclusion
The delivery of a deposit confirmation email resulted from an automatic blockchain detection mechanism, not from any manual action or policy breach by BitGuruz Casino. The account remained closed, and the casino did not facilitate or benefit from post-exclusion gameplay.
We trust this clarifies the technical aspect of the email delivery.
Should further details be required, we remain available.
Kind regards,
BitGuruz Casino
Casino Representative
Dear Matej,
Dear Casino Guru team,
Further to our previous response, we would like to provide a clear technical explanation regarding the deposit confirmation email referenced by the player.
How deposit confirmation emails are generated
BitGuruz operates on a blockchain-based deposit architecture. Deposit notification emails are generated by an automated system event, not by manual approval or active acceptance by the casino.
Specifically:
when a cryptocurrency transaction is detected on the blockchain to an address that was previously associated with a player account,
the system automatically registers the on-chain confirmation event (e.g., network confirmations),
and a system-level notification email may be triggered to inform the user that a transaction has been detected on the blockchain.
This process is purely informational and reflects:
a blockchain confirmation,
not an approval of gameplay,
not account reactivation,
and not acceptance of funds into an active player balance.
Account status vs. blockchain notifications
It is important to distinguish between:
account status (open / closed / self-excluded), which is enforced at platform level, and
blockchain events, which occur independently of account status.
Once the player’s self-exclusion was applied and the account closed:
the account could not be used to play;
deposits were not credited to an active balance;
no wagering activity was possible.
However, blockchain networks do not recognize concepts such as "self-exclusion" or "account closure". Any transfer initiated by the sender will still:
be confirmed by the network,
be visible on the blockchain,
and may trigger automated system notifications.
Why this does not constitute a breach
The presence of an automated email:
does not mean the casino allowed a deposit,
does not override self-exclusion,
and does not indicate operational acceptance of funds.
The casino did not enable deposits, did not prompt the transaction, and did not provide gameplay access after the self-exclusion was applied.
Preventive measures
We acknowledge that such automated notifications can cause confusion in self-exclusion cases. As part of ongoing system improvements, we are reviewing:
clearer wording of blockchain notification emails,
additional safeguards to suppress non-actionable emails for closed accounts.
Conclusion
The delivery of a deposit confirmation email resulted from an automatic blockchain detection mechanism, not from any manual action or policy breach by BitGuruz Casino. The account remained closed, and the casino did not facilitate or benefit from post-exclusion gameplay.
We trust this clarifies the technical aspect of the email delivery.
Should further details be required, we remain available.
Kind regards,
BitGuruz Casino
Casino Representative