Reference

sastra4d Privacy Policy for Indonesia

sastra4d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
sastra4d sastra4d Privacy Policy for Indonesia
CONTACT ROUTES

Where to Ask About Your Data

A clear contact route helps you ask what we hold, why we use it, or how to correct an account detail. Start from the support path linked to your sastra4d account and include the email or phone detail used during verification. For wallet questions, add the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so we can locate the record without asking for unrelated details.

Team online

Account request

Use the support path attached to your account to ask for a copy, correction or clarification of personal data. We may ask you to confirm the verified contact detail before discussing records.

Wallet record

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate date. We use those details to separate your payment record from another account.

Access concern

If a login or device prompt blocks a policy request, mention the phone or desktop path you used and the visible account message. That gives our support team a practical starting point.

SECURITY PRACTICE

Six Checks Behind Our Data Handling

We apply the Privacy Policy to the ordinary moments that matter: creating an account, checking a wallet reference, returning on a phone and asking for a data change.

Account creation

When you open an account, we collect the details needed to identify the account and complete phone verification before access. We do not ask you to repeat unrelated profile details for each lobby visit.

Device signals

A phone or desktop session may create login, browser and security records. These signals help us recognise unusual access when you move from the mobile lobby to a desktop session.

Cookie choices

Cookies can remember session settings and help the account path load correctly. You can manage cookie controls in your browser, though restricting them may interrupt login or policy-request forms.

Account protection

We use verification details, login events and device checks to protect account access. Never send a password or full wallet credential through a support message or a policy request.

Retention timing

We retain account, payment-reference and security records only for the period needed for account operation, dispute handling, fraud checks or legal duties. The period can differ by record type.

Change requests

You can ask us to correct, access or clarify personal data through the account support route. Include your verified contact detail and the specific record so we can assess the request.

Privacy Policy Questions for Your Account

These answers address the searches we hear most often about the sastra4d Privacy Policy. They cover wallet references, device sessions, cookies, account access and requests to change personal data. If your case involves a specific record, use the support path connected to your account and describe the event clearly.

It covers account details, phone verification, device and login events, cookies, wallet references, security records, retention and requests to access or correct your personal data.

Our policy concerns the payment reference and status needed to match a transaction. We do not need a general view of your DANA or QRIS wallet activity to handle an account request.

Device and login details help us identify unusual access, protect your account and understand a blocked session. A phone and desktop visit can therefore create separate security events.

Use the support path linked to your account and ask for data access. Include the verified email or phone detail used at account creation so we can confirm the request.

Yes. Send a correction request through account support and name the field that needs changing. We may verify your account before updating contact, profile or payment-reference details.

Cookies can support session settings and account access across your browser. You can adjust them in browser controls, but blocking required cookies may affect login or policy-request pages.

Yes, access and eligibility depend on local law. We assess each request against the applicable rules and explain the next step through the support route linked to your account.