Reference

How we protect your account and payment details

When you open an account with amavi login, your personal information and transaction history are encrypted and stored on secure servers.

Data encrypted at rest and in transitIdentity verified before first withdrawalPayment details handled by PCI-compliant processors
amavi login How we protect your account and payment details
REACH US ANYTIME

Contact us about your privacy rights

Email support Send privacy questions, data-access requests or concerns to our compliance team at [email protected]. Responses sent within three business days.
Live chat during lobby hours Open the help icon in your account dashboard between 09:00 and 23:00 Jakarta time, seven days a week, to speak with an agent about data handling or account security.
Account settings > Privacy View and manage your data preferences, download your account information, or request deletion by navigating to Settings > Privacy & Security in your dashboard.
SECURITY IN DEPTH

How we keep your privacy secure across every transaction

Account access control

Your password is hashed and never logged in plain text. Two-factor authentication is available in Settings; we recommend enabling it. Logins from new devices require email confirmation.

Cookie and tracking practices

We use session cookies to keep you logged in and analytics cookies to see how you navigate the lobby. Third-party cookies from payment processors help prevent fraud. You can manage cookie preferences in your browser settings.

Payment processor partners

DANA, OVO, GoPay and QRIS transactions are processed by certified payment handlers who encrypt data and comply with PCI-DSS standards. We do not see your full card or wallet credentials.

Data retention policy

Account data is retained as long as your account is active. After closure or inactivity beyond 24 months, personal data is deleted within 90 days unless law requires longer retention for audit or dispute resolution.

Your right to access and correction

You can download a copy of your account information, including betting history and deposit records, from your dashboard. Contact us to correct inaccuracies or dispute a transaction.

Breach notification

If unauthorized access to your data occurs, we notify affected users by email within 48 hours and provide guidance on securing your account. We maintain cyber-liability insurance.

Privacy and data questions answered

Yes. Navigate to Settings > Account > Close Account and request permanent deletion. We will anonymize your name, email and contact details within 30 days; betting history is retained for tax and dispute purposes only, as required by local regulations.

Payment details — DANA, OVO, GoPay or QRIS IDs — are not stored on our servers; they're processed by external partners and deleted after each transaction. Your transaction history appears in your account for 36 months for dispute resolution and audit.

We share data only with payment processors, compliance partners and law enforcement when required by court order. We do not sell or rent your personal information. Depends on local law for disclosure of betting history to regulators.

Contact our support team with your registered phone number and date of birth. We'll verify your identity and help you reset your password. Withdrawals require additional verification via government ID before funds are released.

We collect and verify your national ID during registration and match it against our database. We monitor login locations and device fingerprints; unusual activity triggers a security check or temporary account lock pending verification.

No. Your betting history, balance and transaction records are private and visible only to you and our compliance team for dispute resolution. Leaderboards show only your username and rank, never your real name or account balance.

We use essential cookies for login and session management, plus analytics cookies to improve the lobby experience. Payment processors set fraud-detection cookies. You can disable non-essential cookies in your browser; this may limit some features.