Reference

cufflink Privacy Policy for Your Account

Your account details, device signals and wallet records receive a clear explanation in the cufflink Privacy Policy, so you can decide what to share before opening an account.

Account dataWallet recordsCookie choicesPolicy requests
Explore Our Lobby Read FAQ
cufflink cufflink Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when you need to ask about the Privacy Policy, an account record or a wallet reference. We keep policy questions separate from game choices, so your request can focus on the data involved. Use the support route shown after login, include the account phone number or relevant receipt reference, and avoid sending a password or full wallet credentials. We will use the details you provide to identify the request and respond through the available account support channel.

Team online

Policy request

Ask which account, device or transaction details we hold through the logged-in support path. Include a short description of your request, but never send your password or one-time phone code.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the receipt reference rather than private wallet credentials. This lets us locate the relevant record without receiving unnecessary payment details.

Login concern

If a phone verification step or account sign-in looks unfamiliar, use the account support route beside the login screen. We may ask for identifying details to confirm ownership before discussing private records.

HANDLING DETAILS

What We Do With Your Data

We keep this policy practical by tying each data type to an account action. Login records help us check access, device signals help us spot unusual sessions, and wallet references help us…

Account records

We use details such as your account identifier and verified phone status to connect requests to the correct account. Before sharing private account data, we may confirm ownership through the existing sign-in or phone verification step.

Device signals

Browser, device and connection signals can support sign-in security and help us identify unusual activity. They are considered alongside account events, not treated as a public profile, and are handled for security and service administration.

Cookie choices

Cookies or similar browser storage may keep a session active, remember a setting or support security checks. Your browser controls can remove stored data, although clearing required session storage may interrupt the account path.

Wallet details

Payment records may show a method such as DANA, OVO, GoPay or QRIS, plus a reference needed to check status. We do not need your wallet password for a receipt or cashier-status request.

Retention requests

We retain records only as needed for account operation, security checks, dispute handling and legal duties. You can ask what applies to a particular record, and we will explain any limit on deletion or correction where local law permits.

Policy changes

If the Privacy Policy changes in a way that affects account data handling, we will present the revised wording on this policy page. Check the page before using a new account or cashier step so the current terms are clear.

Privacy Policy Questions About cufflink

These answers address the practical searches you may make before opening an account or contacting us about personal data. We focus on the cufflink Privacy Policy, including phone verification, mobile browsing, cookies, wallet references and requests for account records. If your situation is not covered, use the logged-in support path and describe the specific record or policy point you want us to check.

It covers account details, phone verification, device and connection signals, cookie storage, support messages, security events and payment references. It also explains why we use these records for account access, wallet-status checks, security, support and legal duties.

Yes. The Privacy Policy covers records showing a DANA or QRIS payment reference and related cashier status. It can also apply to OVO, GoPay, bank transfer and virtual account references, while your wallet password remains yours.

Phone verification helps connect an account request to the person signing in and supports account security. We may use the verification status when discussing private records, login concerns or a request to change account details.

It can cover browser, device and connection signals linked to an account session. We use these signals for security and service administration, such as spotting an unfamiliar login, rather than presenting them as a public personal profile.

Use the support route available after account login and state whether you want a record copy, correction or clarification. Include your account phone number and the relevant reference when useful, but do not send a password or one-time code.

Retention depends on the record and its purpose, including account operation, security checks, dispute handling and legal duties. Ask us about a specific account or payment reference, and we will explain the applicable retention position.

Contact us through the logged-in account support path and mention the section or wording that concerns you. We will direct the request to the relevant policy process and explain how the current page applies where local law permits.

Related Pages

cufflink Indonesia About Us Account information cufflink Casino Dice Duel Fast Game