Reference

Terms & Conditions For Your Account

Our Terms & Conditions set the ground rules for using bosku33, from opening an account to checking a DANA, OVO, GoPay or QRIS transaction.

Account accessWallet checksDevice rulesPolicy requests
bosku33 Terms & Conditions For Your Account
HELP WITH TERMS

Get Clear Answers Before You Join

Questions about the Terms & Conditions should be resolved before you confirm an account action or send a payment.

Account access When a login or phone verification step stalls, contact our support desk from the account path. We use your registered phone number and the affected device details to locate the relevant Terms & Conditions step without asking you to send a password.
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment receipt and reference shown in your cashier path. We compare the status with the account record, then explain whether the Terms & Conditions allow the requested correction or next step.
Policy requests To ask about a wording change, account closure or access decision, contact us with the section you mean and your registered contact detail. We keep the conversation tied to your account so the response applies to your actual Terms & Conditions request.
ACCOUNT SAFEGUARDS

What We Keep And How We Use It

Our handling of the Terms & Conditions starts with the details needed to operate an account: your phone number, verification result, payment reference and basic device signals.

Phone verification

Phone verification connects your account to a contact route before account access is completed. If your number changes, tell us through the support path first. The Terms & Conditions allow us to request another check when the registered number and account request do not match.

Payment records

A DANA, OVO, GoPay or QRIS reference helps us trace a cashier event. We retain the reference and status needed to resolve a payment question, while the Terms & Conditions restrict account actions that cannot be matched to your registered details.

Cookies

Cookies can preserve a login session and device preference, but your browser controls whether they remain. Clearing them may require a fresh phone verification step. Our Terms & Conditions still apply when you return through a new browser or another supported device.

Account security

Keep your phone, password and verification codes private, and sign out on a shared device. We may ask for account details already held in our records when access looks unusual. We will not ask you to disclose a password to settle a Terms & Conditions question.

Record retention

We keep account, verification and payment records for the period needed to operate the account, answer a dispute and meet applicable local requirements. A retention request should name the record or section concerned, so we can assess it against the Terms & Conditions.

Change requests

You can ask us to correct contact details, explain an access decision or clarify a policy section through the support desk. Include your registered phone number and the requested change. We review the request against the account record and reply with the available next action.

Terms & Conditions Questions Answered

These Terms & Conditions questions cover the account steps that matter before you use the lobby. We address eligibility, phone checks, wallet records, device changes, cookies and policy requests in plain language. If your situation does not fit one of these answers, send the section name and account reference through our support path. We can then connect the written rule to your account record, including a DANA, OVO, GoPay or QRIS status that needs checking.

They cover account creation, phone verification, login security, supported payment records, device access, cookies, account changes and policy requests. They also explain when we may pause an action for a record check. Access depends on local law and applies where local law permits.

Yes. We use the phone number you submit to confirm account access and connect support requests to the correct record. If your number changes or a code does not arrive, contact us before creating another account so we can check the existing verification path.

Those payment names are available as local cashier routes where shown for your account and location. Your payment reference must match the account details we hold. We may ask for a receipt or status check before reflecting, correcting or discussing a wallet transaction.

A new phone, browser or cleared cookie session may trigger another login or phone verification step. This is part of our account security terms, not a new account requirement. Keep your registered number available and contact support if the device check does not complete.

We use phone, verification, device and payment-reference data to operate access, trace account activity and answer disputes. Cookies may support a session or preference. Our Terms & Conditions limit these records to account operations, policy handling and applicable local requirements.

Yes. Send the registered phone number, the detail that needs correction and the relevant Terms & Conditions section through our support path. We compare the request with the account record and explain the available correction. Do not send your password or verification code.

Yes. We may pause access or a transaction while checking unusual login activity, duplicate details, mismatched wallet records or an eligibility question. The Terms & Conditions do not remove local requirements. Contact us with your account reference so we can explain the status.