Reference

soya4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a soya4d account, sign in on mobile, or use DANA and QRIS for account funding.

Account dataWallet recordsDevice choicesPrivacy requests
soya4d soya4d Privacy Policy for Your Account
HELP PATHS

Where To Ask About Privacy Changes

You can raise a privacy question without guessing which account team to contact. Start from the support route connected to your account, include the email or phone detail used at registration, and describe the requested change clearly. For a wallet matter, attach the payment reference rather than sharing a password. We use the same route to clarify access in Yogyakarta when local eligibility wording affects your account.

Team online

Account privacy

Ask us to check the personal details attached to your account, including your registered phone contact. We may request an account step before changing data so another person cannot act for you.

Wallet records

For DANA, OVO, GoPay, QRIS, or bank transfer records, send the reference and date shown in your cashier history. We can clarify matching or status without requesting your wallet password.

Data requests

Request access, correction, or eligible deletion through the account support path. Tell us which record you mean and keep your sign-in details private while we confirm the request.

SIX PRIVACY CHECKS

Six Checks Behind Your Account Privacy

Privacy is handled through practical account steps rather than a vague promise. We separate sign-in checks from payment references, explain why device records may appear, and keep a route for correction requests.

Data we collect

We may record your registration contact, verification result, sign-in events, device signals, and payment references. These details help connect your account activity with the correct wallet record and protect access.

Cookie choices

Cookies and similar browser storage can keep your session connected and remember selected settings. You can manage browser permissions, although turning them off may interrupt sign-in or policy access.

Account security

Phone verification before account access helps us distinguish you from an unfamiliar sign-in. Never send a password or wallet PIN to support; we use account checks instead.

Retention period

We retain account, security, and payment references only as long as needed for service, dispute handling, system protection, or a lawful record-keeping reason that applies.

Correction route

If your contact detail or account record is inaccurate, use the support route and identify the specific field. We may verify ownership before applying a correction to your profile.

Third-party requests

When a payment provider or lawful authority requires a transaction response, we share only the records needed for that request. We do not disclose your wallet password or private sign-in credentials.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording practical: what we collect, how you can ask for a change, and what happens when a payment reference or device record needs checking. For location-based eligibility, the applicable wording is where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, payment references, support requests, retention, and privacy changes connected with your soya4d account.

Yes. The Privacy Policy covers status and reference details for DANA and QRIS, as well as OVO, GoPay, bank transfer, and virtual account activity used to match your account.

Device and sign-in signals help us identify unusual access and protect your account. They may also keep a mobile session working correctly, but they do not reveal your wallet password.

Use the account support route, name the field that needs correction, and provide the contact detail used during registration. We may complete an ownership check before changing the record.

You can request deletion of eligible data through support. We assess the request under applicable rules, and some account, security, or payment records may remain when a lawful retention reason applies.

We keep payment references for the time needed to match activity, handle disputes, protect systems, or meet an applicable record-keeping duty. The period can differ by record type and local rule.

Yes. Access and eligibility depends on local law. If you request data or account action from Indonesia, we apply the location rules and account checks relevant to your request.