LZLAZER
ZHLoginRegister
System status Online●Mode Demo simulation●Fairness Ready to verify
Support desk

Bring the
round ID.

For account, verification or responsible-play questions, send us the round ID and timestamp when possible.

Support triage
Mon—Fri / 09:00—18:00 UTC
01
Before you writeBring the smallest useful set of facts.
02
Account helpSecurity questions come first.
03
Fairness reviewA round ID gives the team a place to start.
04
Responsible playYou can ask for a pause without explaining everything.
Current guidance

Bring the smallest useful set of facts.

A clear request gets routed faster. Start with the topic, the affected page or round, the time it happened and what you expected to see.

support@lacaze-trading.exampleMon—Fri / 09:00—18:00 UTC
01Create a request

Send the issue to the right queue. Never include a password, one-time code or full payment details.

Security note
02Resolution playbook
02 / Account help

Security questions come first.

For login or registration issues, support may ask you to confirm the account contact method. We will never need your password in a support message.

  • Use the email or phone linked to the account.
  • Mention whether you can still receive messages.
  • Do not send one-time codes in plain text.
03 / Fairness review

A round ID gives the team a place to start.

If a result looks wrong or cannot be verified, preserve the context. The review path should compare the record, the published rule and the account event without asking you to recreate the round.

  • Keep the original time zone if possible.
  • Include the displayed result.
  • Wait for a case reference before following up.
04 / Responsible play

You can ask for a pause without explaining everything.

If you need a cool-off, self-exclusion or help finding local resources, say so directly. Support should treat the request as a safety control, not a sales conversation.

  • Ask for a temporary or ongoing restriction.
  • Tell us if someone else may be using the account.
  • Use local specialist support for urgent personal risk.
Escalation path

No context, no reliable review.

01 Submit facts02 Receive case ID03 Await review
Support questions
How quickly will I receive a reply?

The preview lists service hours but does not promise a live response time. The production service should publish a clear support target.

What should never be sent?

Never send passwords, one-time codes, full card numbers or private keys. A round ID and timestamp are enough to begin a review.

Can support close my account?

A live service should provide account closure and self-exclusion routes. Use the request form to start the process.

Where do I report a responsible-play concern?

Use the support form and write “responsible play” as the topic. For immediate harm or crisis, contact local emergency or specialist services.

Responsible play

Good support is part of the game design.

Use the form above for a specific request, or read the responsibility guide when you are deciding whether to pause.

Open responsible play