Reference

Legal at hakata136: access and privacy

Legal clarity starts with knowing how account access, payment records and personal data are handled.

Account termsPrivacy requestsCookie choicesLocal-law access
hakata136 Legal at hakata136: access and privacy
CONTACT ROUTES

Where Legal questions should go

A clear contact path helps you resolve a policy question without repeating account details. We separate access concerns, wallet records and personal-data requests so the right context reaches our support team.

Account access Use the account help path when phone verification, age eligibility or local-law access is unclear. Include your registered phone number and the exact message shown on your device; do not send a password or one-time code.
Wallet records For DANA, OVO, GoPay or QRIS questions, open the payment-status path and attach the receipt reference. We use that reference to match the account record, check its status and explain which Legal term applies.
Data requests For access, correction or deletion requests, choose the personal-data contact route in your account. Tell us which detail you want changed and how we can verify ownership before any record is amended.
DATA PRACTICE

How we handle policy duties

Legal promises matter only when they match daily account work. We apply the same data and security steps across desktop browsers and mobile browsers, including the phone check before access.

Data collection

We collect account details needed to create, secure and maintain your access, plus payment references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Our Legal terms describe the purpose for each record.

Cookie controls

Cookies help keep account sessions working and remember selected settings on your browser. You can manage available cookie choices through your browser controls; changing them may affect sign-in continuity or saved preferences.

Account security

Phone verification is required before account access, and we ask you to protect the registered number and password. We do not need your one-time code in a support message, even when a payment status needs checking.

Record retention

We retain account, verification and payment records only for the period explained in our Legal terms or required for a valid operational or legal duty. When retention is no longer needed, the applicable record is removed or securely restricted.

Policy contact

Questions about Legal wording should go through the account support path, with the clause or account step named clearly. This lets us distinguish an access question from a DANA receipt issue or a personal-data request.

Request changes

You can ask us to correct account details or explain how a record is used. We first verify account ownership, then confirm the requested action and any reason a record must remain under the stated policy.

Legal answers before opening an account

These Legal questions cover the points you may want settled before creating an account on hakata136. They address local access, verification, payment records, cookies and personal-data requests without replacing the full policy text. Read the relevant clause and contact us through the account path when your circumstances need a direct answer.

The Legal policy covers account eligibility, phone verification, personal-data use, cookies, payment records, account closure and contact requests. It applies to the listed lobby and account services, including records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Access depends on local law. You must decide whether you are permitted to use the service in your location and complete the required account step, including phone verification before access. If eligibility is uncertain, contact support before creating or funding an account.

Phone verification links the account to a contact detail you control and helps us protect access when a session or payment record needs checking. We may use the verified number to confirm ownership, but you should never share a one-time code.

A DANA or QRIS transaction creates a payment reference that helps match the receipt with your account status. Our Legal terms explain the purpose and retention of that record. Keep your receipt reference, and use the wallet-status path if the account display is unclear.

Yes. Send a correction request through the account data path and identify the detail that is wrong. We verify account ownership first, then confirm whether the change can be made immediately or whether a record must remain unchanged for a stated policy reason.

Essential cookies help maintain a secure browser session, while preference cookies can remember selected settings. Your browser controls let you change available choices. Blocking required cookies may interrupt sign-in or phone verification, but it does not remove the underlying Legal terms.

Use the account support path to request closure or ask about data removal, and include the registered phone number without sharing your password. We verify ownership, explain which records can be removed, and identify any records that must remain for a valid policy duty.