Reference

Privacy Policy for simba4d Account Data

Our Privacy Policy explains how simba4d handles the details connected with your account, device and wallet activity.

Account clarityCookie choicesData request pathIndonesia context

How DANA and QRIS Data Is Used

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

Our Privacy Policy separates payment references from the private credentials held by your wallet provider. When you choose DANA, OVO, GoPay or QRIS, we may receive transaction references, status details, timestamps and account identifiers needed to match a request to your simba4d account. Bank transfer and

1
virtual account activity can add a bank name, reference number and reconciliation status; BCA, BRI, Mandiri and BNI may appear in those records when you select them. We use these details to confirm account actions, investigate a missing status and answer a receipt question. We do
2
not ask you to send a wallet PIN or banking password through support. Where local law permits, we retain records for the period needed for security, disputes and legal duties, then remove or anonymise them under our retention process. The policy applies to access from Indonesia
3
and may change when local requirements differ.

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

CONTACT WHEN NEEDED

Privacy Help Along Your Account Path

A clear contact path helps when a Privacy Policy question affects your login or wallet status.

Account access If you cannot complete phone verification, contact us through the account support route and describe the step that stopped. We use the submitted account detail to check identity safely.

Wallet status For a DANA, OVO, GoPay or QRIS status question, send the transaction reference and date rather than a PIN. This lets us trace the record while limiting sensitive wallet data.

Privacy request To ask about access, correction or removal, use the same support path and state the request clearly. We may ask for account verification before changing or releasing personal data.

CONTROL YOUR DETAILS

Cookies, Devices and Account Security

Privacy controls work best when they match the way you actually sign in. Our handling covers browser storage, phone verification, wallet references and account activity across mobile and desktop paths.

Account records

We use your account details to create access, confirm requested changes and connect account activity with the correct wallet reference. Phone verification helps prevent an unauthorised person from changing those details.

Device signals

Browser type, device information and sign-in events can help us detect unusual access and diagnose a mobile login issue. We use these signals for account protection, not to request your private device password.

Cookie choices

Cookies and similar storage can keep a session active, remember a language or preserve a security setting. You can adjust browser controls, although some account steps may then need repeating.

Payment references

For QRIS, DANA, OVO, GoPay, bank transfer or virtual account activity, we keep the references needed to match status and receipts. Wallet PINs and banking passwords should never be sent to us.

Retention process

We keep personal data only while it supports account security, transaction questions, dispute handling or a legal requirement. When the retention period ends, records are deleted or changed so they no longer identify you.

Change requests

You can ask us to access, correct or remove eligible personal data through the support route attached to your account. We verify the request first, then explain any legal reason a record must remain.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep the wording practical: what we collect, how we use it, what happens on a mobile device and how you can reach us when a personal-data request needs attention.

It covers account details, phone verification, device signals, cookies, wallet and payment references, retention and requests to access or change personal data connected with your simba4d account.

No. Our Privacy Policy says you should not send a DANA or GoPay PIN, OVO credential or banking password to support. We use transaction references and status details for account matching.

Phone verification helps connect an account request to the person authorised to use it. We may use the verification result when you request account access, correction or a change to personal details.

Cookies can retain a session, language choice or security setting while you browse on mobile. You can change browser permissions, but disabling some storage may require you to repeat login steps.

Yes. Send a correction request through the support route shown with your account, identify the field that needs changing and complete any identity check required before we edit the record.

We retain wallet and bank references for the period needed for security checks, receipt questions, disputes or legal duties. After that period, we delete or anonymise the applicable record.

Yes, the same Privacy Policy applies to your account and device activity from Medan and other Indonesian locations, while access or eligibility depends on local law and applicable requirements.

Privacy Policy for simba4d Account Data

Privacy Help Along Your Account Path

Cookies, Devices and Account Security

Account records

Device signals

Cookie choices

Payment references

Retention process

Change requests

Privacy Policy Questions for Indonesia

01 What does the simba4d Privacy Policy cover?

02 Does simba4d store my DANA or GoPay PIN?

03 Why does simba4d need phone verification?

04 How are cookies used on my phone?

05 Can I ask simba4d to correct my personal data?

06 How long does simba4d keep wallet references?

07 Does the Privacy Policy apply to access from Medan?

Related Pages