Reference

gocap123 Privacy Policy for Your Account Data

gocap123 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or select DANA and QRIS for account activity.

Account data explainedWallet activity coveredCookie choices includedContact path available

Explore Our Lobby Read FAQ

What DANA and QRIS Context Means Here

gocap123 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy connects account records with the actions needed to process your chosen payment route, without treating a wallet label as a separate identity. When you select DANA, OVO, GoPay or QRIS, we may record the method, transaction reference, status and time so we can

1
match an account request and answer a payment question. Bank transfer and virtual account references are handled for the same reason. We use sign-in details, device signals and account messages to protect access and resolve requests. Where local law permits, you can ask what data we
2
hold, request a correction, or ask about deletion limits. Access or eligibility depends on local law, and our policy is read together with any required account checks.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH DATA REQUESTS

Reach Us When Account Data Needs Attention

A clear contact route matters when a name, phone number, wallet reference or device record needs checking. Use the support path shown inside your account and include the email or phone detail linked to your login, plus the subject of your Privacy Policy request. We use those details to locate the right record without asking you to send a full payment credential.

Team online

Account access request

If you cannot sign in, tell us the account step where access stopped and the device path you used. We can explain which identity detail is needed before discussing stored data.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, share the payment method and reference shown in your account. Do not send a wallet PIN, password or full card credential.

Privacy Policy request

Ask about access, correction, deletion or retention through our account support route. We may request a matching account detail so a private record is not disclosed to the wrong person.

HOW WE HANDLE RECORDS

How Account Data Stays Tied To Your Access

We keep this policy practical by linking each data practice to an account action you recognise.

Data we collect

We may handle your account name, contact detail, verification status, sign-in records, device signals and selected payment reference. We collect these details when they support access, security or a direct request.

Cookie controls

Cookies and similar storage can remember a session or help us understand page use. Your browser settings provide a way to remove or restrict them, though sign-in functions may then need another step.

Account security

Phone verification comes before account access where required. We also use session and device details to review a sign-in concern, and we will not ask for your password through a support message.

Payment references

A DANA, OVO, GoPay or QRIS reference can remain with the related account record so we can match status questions. We do not need your wallet PIN to investigate that reference.

Retention approach

We retain records for the period needed for account operation, security, dispute handling and legal duties. The period can differ by record type and by requirements that depend on local law.

Change or deletion

You can ask us to correct account data or explain whether deletion is available. Send the request through account support, and we will confirm the identity detail needed to process it.

Privacy Policy Answers For DANA And QRIS

These questions cover the account situations that most often lead you to look for a Privacy Policy before opening an account. We keep the answers focused on your data, your access request and the payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

It covers account details, phone verification, sign-in and device records, cookies, payment references, retention and requests to access or correct data connected with your account.

We use a DANA or QRIS reference to match an account action with its payment status and answer a support question. A wallet PIN is not needed for that check.

You can ask for access to the account data we hold through the account support path. We may first confirm your phone or email detail to protect the record.

Send a correction request through account support and identify the record that appears wrong. We will explain the verification step and any limits that depend on local law.

Retention depends on the record, its security or dispute purpose, and applicable legal duties. Our Privacy Policy explains why a DANA, GoPay or bank reference may remain after an account action.

Your browser settings can remove or restrict cookies on a mobile phone. Some account functions may then require another sign-in step, while necessary session records follow the policy.

Yes. Requests and account eligibility depend on local law. Where local law permits, you can ask about access, correction or deletion through the support route linked to your account.

gocap123 Privacy Policy for Your Account Data

Reach Us When Account Data Needs Attention

Account access request

Wallet record question

Privacy Policy request

How Account Data Stays Tied To Your Access

Data we collect

Cookie controls

Account security

Payment references

Retention approach

Change or deletion

Privacy Policy Answers For DANA And QRIS

01 What does the gocap123 Privacy Policy cover?

02 Why does gocap123 record my DANA or QRIS reference?

03 Can I request a copy of my account data?

04 How do I correct a phone number or account name?

05 How long does gocap123 keep payment data?

06 Can I delete cookies used during mobile access?

07 Does access to my data depend on local law?

Related Pages