Reference

sekar4d Privacy Policy for Indonesia Accounts

Our sekar4d Privacy Policy explains what we collect when you open an account, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
sekar4d sekar4d Privacy Policy for Indonesia Accounts
CONTACT YOUR WAY

Get Policy Help Beside Account Support

A clear contact route helps when you want to ask about stored data, cookie settings or a wallet record. From your account, use the support path shown near the cashier area and include the email or phone detail linked to your account. We may ask for an account step or transaction reference to confirm that the request comes from you.

Team online

Data request

Ask us to explain the account details, device records or wallet references connected with your sekar4d account. We use the contact route displayed in your account and may verify your identity first.

Cookie choice

Tell us whether you want optional cookies adjusted on your mobile browser or desktop session. Essential session cookies may remain active so sign-in and account security checks continue to work.

Wallet question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the relevant account detail through support. We compare the record with the cashier status before explaining what we hold.

HOW WE HANDLE IT

Keep Your Privacy Choices Understandable

Privacy work is tied to practical account events rather than broad promises. We separate sign-in protection from payment references, explain cookie use, and keep a request path available when you need a…

Account security

We use sign-in records, device signals and account verification steps to identify unusual access. We do not ask for your wallet password through a support request, and you should keep account credentials private.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep transaction references and status details needed to match your account history and answer cashier questions.

Cookie controls

Essential cookies help maintain a session and protect account access. Optional cookies may support preferences or page measurement, and you can ask us to adjust those choices through the account contact path.

Data retention

We keep personal and transaction records only as long as needed for account operations, security checks, support questions and applicable legal duties. After that period, records are deleted or made non-identifying.

Correction requests

If your contact detail or account record is inaccurate, send the requested correction through support. Include the account step involved so we can locate the relevant record without asking for unnecessary information.

Access requests

You can ask what personal data we hold, why it is used, or how long it is retained. We may confirm account ownership before responding, especially when the request concerns sign-in or wallet history.

Answers About the sekar4d Privacy Policy

These Privacy Policy answers cover the account questions you are most likely to ask before opening an account or checking a wallet record. We keep the wording practical: what we collect, how cookies work, how to request a change, and what access means when local rules apply.

It covers personal details, sign-in activity, device signals, cookie use, account preferences and transaction references connected with your sekar4d account, including records linked to DANA, OVO, GoPay and QRIS.

No. We use payment status and transaction references to match account activity, but we do not ask for or store your private DANA, OVO, GoPay or QRIS wallet password.

Essential cookies keep your session active and support sign-in checks. Optional cookies may remember preferences or measure page use; you can request a change through the account contact path.

Use the support route shown inside your account and ask for a data access response. Include your linked email or phone detail; we may verify account ownership before sharing records.

Yes. Send a correction request through account support and identify the affected detail, such as contact information or a device record. We will check the account step before updating it.

We retain records for account support, security checks, transaction matching and applicable legal duties. When they are no longer needed, we delete them or remove identifying details.

Yes. Account access and eligibility depends on local law. Where local law permits, you can read this Privacy Policy and contact us through the account route for questions about your records.