Reference

sukro4d Privacy Policy for Your Indonesia Account

Our Privacy Policy explains how we collect, use and protect the details connected with your sukro4d account, including phone verification, device access and wallet records.

Clear data purposesWallet record handlingPolicy contact path
sukro4d sukro4d Privacy Policy for Your Indonesia Account
PRIVACY HELP

Where to Ask About Your Account Data

A direct support route helps when you want to ask about a phone record, device sign-in or payment reference. Open the account support path and identify the email or phone number attached to your profile; we use that account step to reduce mistaken disclosures. If your question concerns a QRIS receipt or bank transfer, include its reference without sending a wallet password.

Team online

Policy request

Send a Privacy Policy question through the support path linked to your account. We use your registered phone or email to confirm that the request concerns your own records.

Wallet reference

For DANA, OVO or GoPay records, share the transaction reference and date only. We can check the account match without asking for your wallet PIN or private wallet credentials.

Access concern

If a new device or phone verification blocks account access, tell us the device type and registered contact. We use those details to investigate the sign-in event safely.

DATA PRACTICE

What We Do With Privacy Requests

We treat this policy as an operating process rather than a page kept out of sight. Account records support phone verification, wallet reconciliation and security checks, while cookies help remember session choices…

Account details

We collect the contact details you submit during account opening and phone verification. These details help us connect your sign-in, support request and account records without asking you to repeat the full account path.

Device signals

Browser type, device details, IP address and sign-in time can help us identify unusual access. A mobile session opening the lobby is treated as an account security event, not as permission to read unrelated device content.

Cookies

Cookies can retain session choices and help the account path work between login and the lobby. You can manage browser cookie settings, although changing them may require another sign-in or affect saved session preferences.

Payment references

For QRIS, DANA, OVO, GoPay, virtual account or bank transfer checks, we retain the reference needed to match status and receipts. We do not request your wallet PIN through our account support route.

Retention process

We retain account and transaction records for the operational or legal period that applies, then delete, restrict or anonymise them where appropriate. A retention question can be sent through the same policy contact path.

Change requests

You may ask us to correct account details, explain a data use or address a deletion request where local law permits. Include your registered contact so we can verify ownership before making a change.

Privacy Policy Answers for sukro4d

These Privacy Policy answers cover the account, device, cookie and payment questions we expect you to ask before opening or using your profile. Each answer points back to a practical account step, so you know what to send and what we can check.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with your sukro4d account. It also explains purposes, retention and request routes.

We use your phone number for account creation, verification and ownership checks when you contact support. It helps us protect account records and distinguish your request from another person’s request.

Yes. The policy covers the DANA, OVO, GoPay and QRIS references needed to match a receipt or transaction status. We do not ask for your wallet PIN or unrelated wallet activity.

You can ask us to correct inaccurate account details through the policy support path. Include your registered phone or email, and we will verify ownership before changing the relevant record.

Cookies may retain a browser session and account-path choices between login and the lobby. You can adjust browser settings, but removing cookies may sign you out or require another verification step.

We keep records for the operational or legal period needed for account security, support and transaction reconciliation. After that period, we delete, restrict or anonymise records where appropriate.

You may send a deletion request through our policy contact route, where local law permits. We first confirm account ownership and explain any records that must remain for legal or transaction reasons.