Reference

sepuhtoto Terms & Conditions, Clearly Set Out

Clear account rules help you understand access, wallet activity and policy changes before you enter the lobby.

Account access rulesWallet handlingPolicy change noticesSupport contact path
sepuhtoto sepuhtoto Terms & Conditions, Clearly Set Out
HELP WITH POLICY

Get Help With Terms And Access

A clear contact route matters when a policy clause affects your account or wallet status.

Policy questions Send the clause or account step you want explained through our support route.
Login access If you cannot reach your account after a device change, tell us the registered…
Wallet records For DANA, OVO, GoPay or QRIS questions, keep the payment receipt and reference visible.
ACCOUNT SAFEGUARDS

Your Data And Account Safeguards

We treat the Terms & Conditions as a working policy, not a hidden link. The account flow, cookie settings, phone verification and support record each have a defined purpose, while requests to…

Account details

We use the details you submit to create and maintain your account, check phone verification and match payment records. Keeping your phone number current helps us apply the Terms & Conditions to the correct account.

Cookie settings

Cookies can keep your session active and remember selected preferences. Your browser controls can clear them, although removing session cookies may require you to complete the account access step again.

Login security

Your password, phone verification and device session work together during access. Do not share login details; contact support if a device change leaves your account locked or the policy screen cannot load.

Payment records

We retain payment references needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. A receipt or reference number helps us answer a Terms & Conditions question accurately.

Policy retention

We keep account and support records for the period needed to operate the account, address disputes and meet applicable legal duties. We do not describe a fixed period where the period can vary by case.

Change requests

To request a correction, deletion or policy clarification, contact us through the account support route and identify the affected account detail. We may ask for verification before changing personal or wallet-linked records.

Terms & Conditions Questions Answered

These answers focus on the clauses you are most likely to check before opening an account or asking for a change. If your situation involves a specific DANA, QRIS, device or verification record, include that detail when contacting our support route.

You can open the Terms & Conditions from the policy page before completing account access. Read the current version for account duties, payment records, privacy requests and the wording that applies where local law permits.

Yes. The policy explains how we associate DANA and QRIS references with your account, what receipt details may be requested and why a payment check can be needed before an account change.

Phone verification is part of the account access path. Your registered number must match the account record, and we may ask for additional confirmation when a new device or unusual account detail needs review.

Yes. Contact our support route with the account detail you want corrected, removed or clarified. We may verify your identity first, then apply the request according to the Terms & Conditions and applicable law.

A device change can end a session or trigger another phone check. That step protects the account record and does not by itself change your agreement; contact us if access remains blocked after verification.

We may restrict access when account details cannot be verified, payment records conflict or activity appears to breach the stated terms. Eligibility depends on local law, and support can explain the relevant policy section.

Keep the OVO or GoPay receipt, reference and registered phone number ready, then use our support route. We can compare the record with the account terms and explain whether more verification is required.