Reference

Legal terms for your cufflink account

cufflink Legal terms set out how account access, wallet records and policy requests work before you enter the lobby.

Account accessPolicy requestsPhone verificationLocal-law wording
cufflink Legal terms for your cufflink account
CONTACT THE POLICY TEAM

Where Legal questions get answered

A clear contact route matters when a Legal question affects your account or a payment record. Start with the account-help route near the cashier, include your registered phone number and quote the relevant status. We can then separate an access question from a wallet question and tell you which details are needed. Where local law permits, policy requests follow the same account verification step used for security checks.

Team online

Account access

If you cannot reach the account area, send the registered phone number and the exact message shown after login. We use that detail to identify an access issue before discussing Legal changes or account ownership.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the rail name, reference number and displayed status. This gives our support route a clear starting point for checking the payment record.

Policy request

When you want a copy, correction or clarification, describe the request in plain English and use the contact path linked to your account. We may ask for phone verification before releasing or changing account-related details.

DATA AND ACCOUNT CONTROL

How cufflink handles Legal matters

Legal handling starts with the account details needed to provide access, check a payment status and respond to a policy request.

Account data

We use account details to connect your login, phone verification and requested support action. Giving accurate information helps us distinguish your request from a similar wallet or payment record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help locate a cashier event. We use the visible transaction details for status checking rather than asking for unrelated account information.

Cookies

Cookies can support session continuity and device preferences when you move between account pages. You can review your browser settings if you want to change how your device stores those small files.

Account security

Phone verification may be required before we discuss ownership, change account details or provide a copy connected to your profile. Never send a password in a support message; describe the issue and use the account contact route.

Retention requests

If you ask how long a record is kept, tell us which account or payment reference you mean. We will explain the applicable retention step and any reason a record still needs to remain available.

Change requests

For correction, access or deletion questions, send a precise request from the contact path linked to your account. We may confirm your phone number before making a change or sharing account-held details.

Legal answers before account access

These Legal answers cover the questions we expect before an account is opened or a policy request is sent. They explain what to prepare, how identity checks fit into the process and where payment records belong. If your situation involves eligibility, access depends on local law. For a personal case, use the support route with your registered phone number and the relevant account or cashier reference.

cufflink Legal covers account access, policy requests, data handling, cookies, account security and payment-record context. It also explains how to contact us about a copy, correction or deletion request. Eligibility depends on local law, so check the terms that apply to your location before opening an account.

Yes. Legal sets out the account checks used when you ask about ownership, access or a change to personal details. Phone verification may be required, and where local law permits, we use the registered account route before discussing information connected with that profile.

A DANA or QRIS record may be used to locate a cashier event, together with its reference number and displayed status. Send those details through account support rather than a separate contact route. We use the record to check the payment question, not to approve an unrelated account change.

You can send a copy request through the contact path linked to your account. Include the registered phone number and describe the data you mean, such as account details or payment references. We may complete phone verification first, then explain the response and retention step.

State whether you want a correction or deletion and identify the account detail or payment reference involved. Send the request through support using your registered phone number. We will confirm the required check and explain if a record must remain available under the applicable policy.

Yes. The Legal section explains that cookies may support session continuity and device preferences across account pages. Your browser controls how those files are stored. If you have a specific cookie question, mention your device path and send it through the account support route.

Access depends on local law. Do not try to bypass a location or account restriction. Contact support with the message shown on your device and your registered phone number, where available. We can explain the account status and the policy route without promising access outside the permitted region.