Reference

sinartogel Privacy Policy for Your Account

sinartogel Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Account dataWallet recordsCookie choicesAccess requests
sinartogel sinartogel Privacy Policy for Your Account
CONTACT ROUTES

Reach Us About Personal Data

A clear contact route helps when you need an answer about your Privacy Policy rights or an account record.

Account data request Tell us whether you need a copy, correction or deletion request, and include the…
Wallet record question For DANA, OVO, GoPay, QRIS or bank-transfer records, send the transaction reference through the…
Access page contact When your login stalls, use the contact option shown before account entry and provide…
ACCOUNT SAFEGUARDS

Cookies, Security And Retention Controls

We handle this policy area through defined account and device steps rather than broad collection. Browser cookies can remember session choices, while security records help us identify unusual sign-in activity.

Data collected

We may receive your name, phone detail, verification result, support messages, device signals and transaction references when you create an account, sign in or ask about DANA and QRIS status.

Cookie controls

Cookies can keep a session active and remember selected settings on your browser. You can clear them through browser controls, although this may require another sign-in before account pages load.

Account security

Phone verification and sign-in checks help connect account activity to the right profile. Never send a password or wallet PIN through support; we do not need either to process a policy request.

Payment matching

A DANA, OVO, GoPay or QRIS reference can help us match a cashier status with your account. We use that reference for the stated payment query, not for unrelated contact.

Retention period

We keep account, support and transaction records only while they serve account operation, dispute handling or legal duties. When the relevant period ends, records are removed or separated from direct identity where practical.

Change request

Ask us to correct an inaccurate detail through the signed-in support route. Include the field concerned and your account phone detail; we may request verification before changing information tied to access.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account, device and payment questions we hear most often from Indonesian customers. Each answer points you toward the relevant account step, contact route or local-law condition without treating a wallet reference as permission for wider data use.

It covers account creation, phone verification, sign-in records, browser cookies, support messages, device signals and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the phone detail to create or locate your account, complete the stated verification step and respond to account requests. It also helps us avoid discussing a wallet record with the wrong person.

QRIS, DANA, OVO and GoPay records may contain a reference, amount status and timing connected with your account. We use those details to match a payment query and do not treat them as broad marketing permission.

Yes. Use the signed-in support route, name the specific record or field, and provide your account phone detail. We may complete an identity check before sending a copy or changing access-related data.

We retain data for account operation, support, dispute handling and applicable legal duties. The period depends on the record and purpose; when it is no longer needed, we remove or de-identify it where appropriate.

Cookies are controlled through your browser settings rather than a wallet screen. Clearing or blocking them may end a saved session and require you to sign in again before viewing account pages.

Yes. Account access and eligibility depends on local law. If you ask about a regional restriction, contact us from the available account or access-page route so we can address the policy condition directly.