Reference

Legal terms before account access

Our legal page explains how your galisata account, wallet records and lobby access are governed before you open an account.

Local law appliesAccount termsWallet recordsPrivacy requests
galisata Legal terms before account access
CONTACT ROUTES

Three legal contact paths

Legal questions should reach the right team with enough detail to act. Send the account email, date of the event, payment reference if relevant, and the exact term you want us to…

Account terms desk Use this route when you want a clause explained, an account status checked or a restriction reason clarified. Include your registered email and avoid sending full card or bank details in the message.
Wallet record request Choose this path for UPI, Paytm, PhonePe or Google Pay references connected to a legal query. We compare the payment reference with wallet logs before sharing what we can release.
Privacy and correction Send correction requests here when your name, contact detail or saved document appears wrong. We may ask for proof before amending records, because legal accuracy affects withdrawals and account access.
RECORD CARE

Six ways we handle legal records

Legal handling is practical: we collect only what is needed for account operation, payment checks, fraud prevention, support history and local law duties.

Data use

We use account data to confirm identity, process wallet activity, answer support requests and apply the terms you accepted. We do not ask for documents unless account checks or local law require them.

Cookie records

Cookies record session status, device signals and preference choices so the account page works consistently. You can change browser settings, but some account security checks may need session cookies to function.

Account security

Login alerts, device checks and password controls help us protect the account from access that does not match your usual pattern. If we detect risk, we may ask you to verify details.

Retention period

We keep legal, wallet and support records for as long as needed to meet account duties, dispute handling and local law requirements. After that, records are deleted or made non-identifying where possible.

Change requests

You can ask us to correct inaccurate account details or update contact records. We check the request against existing proof so that a correction does not create a new legal mismatch.

Escalation path

If a legal response does not answer the issue, reply with the same ticket reference and explain what remains unresolved. A separate handler can re-check the account record and response history.

Seven legal answers for your account

These answers explain the legal points you are most likely to check before opening or using an account. They cover eligibility, data access, wallet records, cookies, correction rights, account restrictions and how to contact us. Each answer is written for practical action, not legal jargon, so you know what to send and what we may ask for.

You may open an account only where your local law permits access and you meet the eligibility checks shown during account setup. We may ask for details if location, identity or payment records need confirmation.

We keep UPI, Paytm, PhonePe and Google Pay references to match account wallet activity, handle disputes and meet legal duties. These records help us explain credits, reversals and withdrawal checks accurately.

Yes. Contact us from your registered email and state the account data you want to check. We may verify your identity before sharing records, because account data can include payment and security details.

Send the correction request with your registered email, the wrong detail and a clear proof document if needed. We compare the request with existing records before changing anything tied to legal access.

Access may be restricted when local law, identity checks, payment mismatch, security risk or a breach of the terms requires review. We will explain the broad reason where we are allowed to do so.

Cookies help record session status, security signals and preference choices. Some are needed for account access and fraud checks, while others support site settings. Browser changes may affect how your account page works.

Use your registered email and include the account ID, ticket reference, payment reference if relevant and the clause or record involved. Clear details help us route the issue to the correct legal handler.