Reference

serubet Privacy Policy for Indonesia

Our Privacy Policy explains how we handle your account, device, wallet and support records when you use serubet, including payments through DANA, OVO, GoPay and QRIS.

Account data clarityWallet record detailsPolicy access on mobileSupport request path
serubet serubet Privacy Policy for Indonesia
HELP WITH PRIVACY

Three Ways to Ask About Your Data

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account support path Open support from your signed-in account and select the privacy question route. Add your verified phone number and the account step where the question appeared so we can locate the relevant record.
Payment record request For DANA, OVO, GoPay or QRIS questions, include the payment date and reference shown in your account. We can then separate a wallet status record from your wider account details.
Access correction request If your name, phone detail or account record needs correction, ask through support while signed in. We may request phone verification before changing information connected with account access.
OUR DATA PRACTICE

Six Privacy Details We Keep Clear

We explain the practical side of privacy rather than hiding it behind broad wording. The policy covers what enters our records during login, phone verification, mobile browsing, wallet activity and support contact.

Account details

We handle the contact and verification details needed to create and protect your account. Your phone verification step helps us distinguish an account request from an unverified change attempt.

Device signals

When you move from login to the lobby on a phone, our records may include browser, device and session signals. These help keep account activity connected to the correct signed-in session.

Cookie choices

Cookies can remember session settings and help the account area load correctly. Your browser controls can remove or block them, although some sign-in functions may then need to be repeated.

Account security

We use phone verification and session checks around account access. Never send us your password or wallet PIN in a support message, even when asking about a Privacy Policy request.

Record retention

We keep account, payment and support records only for the period needed for account operation, payment matching, security checks or legal duties that apply where local law permits.

Change requests

You can ask us to correct account data or explain its use through signed-in support. Include the affected field and your phone verification detail so we can handle the request safely.

Answers About serubet Privacy Policy

These Privacy Policy answers cover the searches we expect before you open an account. They focus on data access, mobile browsing, payment references, cookies, correction requests and the identity checks that protect your account. If your situation is not listed, use the signed-in support path and describe the exact record you want us to locate.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Open the support path while signed in and ask for the account data connected with your phone number. We may use phone verification to confirm that the request belongs to you.

Yes. The policy covers browser, device and session data created when you use a mobile path from login to the lobby. Cookies may also retain session settings in your browser.

Payment references help us match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with the correct account, investigate a stalled status and answer a payment record request.

Yes. Send a correction request through signed-in support and name the field that is wrong. We may ask for phone verification before changing details tied to account access.

Cookies can support session settings and account functions. You can manage them in your browser, but blocking certain cookies may require you to repeat login or other account steps.

Use the account support path and mention retention, access or deletion in your message. We will connect the request to the relevant record and apply the rules that depend on local law.