Reference

tag4d Privacy Policy For Indonesia

Our Privacy Policy explains how we collect, use and protect the details connected with your tag4d account, from phone verification to wallet status.

Account dataWallet referencesCookie choicesAccess requests
tag4d tag4d Privacy Policy For Indonesia
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route matters when you want to ask about your Privacy Policy rights or an account record.

Account contact Send a Privacy Policy question through the support contact shown after account access.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, share the…
Access concerns If you cannot reach your privacy settings from a mobile browser, contact us from…
DATA PRACTICE

How We Handle Account Data

We keep this Privacy Policy practical by linking each data use to an account task: access, verification, payment tracing, security or legal administration.

Phone verification

When you open an account, we use the phone detail and verification result to connect access to the correct account.

Device signals

Our pages may receive browser, device and connection details when you use a phone or desktop.

Cookie controls

Cookies can support login sessions, page settings and basic service measurement.

Wallet matching

Payment references help us match an account action with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Account protection

We may review sign-in details, verification events and device signals when an account needs protection.

Change requests

You can ask what account data we hold, request a correction or ask about deletion through the displayed support contact.

Privacy Policy Questions For tag4d

These Privacy Policy answers address the searches we hear most often from people considering a tag4d account in Indonesia. They explain the practical path for account data, cookies, payment references, mobile access and correction requests. If your question concerns a record not covered here, use the support contact shown in your account and describe the record without sending secret credentials.

The tag4d Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references and support records. It also explains how we use, retain, protect and amend those records where local law permits, including activity connected with DANA, OVO, GoPay and QRIS.

Phone verification links account access to the correct person and helps us respond safely to account requests. We may use the verification result when you ask about stored data or a payment reference. Never send the verification code itself through support or a wallet message.

Yes. The Privacy Policy includes technical details received when you use a mobile browser or desktop, such as browser type, device signals and connection details. We use them for session function, security checks and service measurement, while account access still follows the required verification path.

We may receive or store a payment reference needed to match an account action with DANA or QRIS, and similarly with OVO, GoPay, bank transfer or virtual account. We use those references for status checks and support handling, not to request your wallet password.

You can contact us through the support route displayed in your account and ask about a copy, correction or deletion of a record. We may request phone verification or another ownership check first, then assess the request against retention duties and local law.

We retain each record only while it supports account access, security, payment tracing, support handling or a legal duty. The period can differ by record type and local requirement. When a record no longer serves a permitted purpose, we assess it for removal or anonymisation.

Use the support contact shown after you access your account and state whether your question concerns cookies, phone verification, device data, wallet references or deletion. Do not include a wallet PIN or full authentication code. Account ownership checks may apply before we discuss personal records.