Reference

tag4d Privacy Policy for Your Account

Our Privacy Policy explains how we handle your tag4d account, phone verification, device access and wallet records when you use DANA or QRIS.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How We Handle Wallet And Account Data

tag4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the account details you submit, including contact data used for phone verification, together with sign-in records, device signals and pages you open on the mobile browser or desktop site. When you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we use

1
the transaction reference and status needed to match your account and resolve a payment question. We do not treat a wallet name as permission to collect unrelated content from your device. Cookies may keep your session active and help us understand security events, while browser settings
2
can restrict some cookie functions. We retain records for the period needed for account support, security checks, dispute handling and legal duties. Access to the service depends on local law, and our handling may change when a rule requires it. You can contact us through the
3
account support path to ask what data is held about you.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where To Ask About Privacy Policy

A clear contact route helps when you need a copy, correction or explanation of personal data.

Account support Use the signed-in support path for a Privacy Policy question, correction request or account-access concern. Include your registered phone number so we can match the request safely.

Wallet status If a DANA, OVO, GoPay or QRIS record looks incorrect, send the transaction reference through account support. We use that reference to locate the related status without requesting your wallet password.

Access request Ask for a copy of eligible account data or request a permitted change through the same channel. We may confirm phone ownership before discussing private records or applying an update.

SECURITY PRACTICE

Six Practical Rules Behind Our Policy

Our Privacy Policy is applied through everyday account steps rather than broad promises. Phone verification helps us separate your account from an unknown sign-in, while device and session records help us investigate…

Phone verification

Before account access is completed, we use the submitted phone details to confirm the account path. This reduces confusion when you return from a new mobile browser or another device.

Session signals

We record practical sign-in signals such as session activity and device type to investigate account access. These records help us identify an unusual session without reading unrelated device content.

Cookie controls

Cookies can keep a session available and support security checks. You can adjust cookie settings in your browser, although restricting them may affect sign-in continuity or certain account pages.

Payment matching

For QRIS, DANA, OVO, GoPay and bank transfers, we use transaction references to connect a payment status with your account. We do not need your wallet PIN for that matching step.

Retention checks

We keep account, support and transaction records only while needed for security, dispute handling, account service or legal duties. When a record is no longer needed, our retention process can remove it.

Policy contact

You can ask about access, correction or eligible removal through account support. We may request phone verification first, then explain the available action and any limit required by local law.

Privacy Policy Questions About tag4d

These answers address the searches we hear most often about the tag4d Privacy Policy. They cover account records, wallet references, browser cookies, access requests and the steps needed to contact us from Indonesia when the service is available where local law permits.

The tag4d Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number for account identification and verification before access. It helps us match a support request to the correct account and confirm ownership before discussing private records.

No. Our payment matching process uses a transaction reference and status for the selected rail. You should not send a DANA, OVO, GoPay or banking PIN through account support.

Open the signed-in support path near the cashier area and ask for an eligible data copy. Include your registered phone number, then complete any ownership check needed before we discuss the record.

Yes, you can request a correction through account support. Tell us which field is wrong and provide the updated detail; we may verify your phone ownership before changing the account record.

Cookies can preserve your session and help us identify security events. Your mobile or desktop browser can restrict them, but sign-in continuity and some account functions may change after those settings.

We retain records for the time needed for account support, security checks, payment questions, disputes and legal duties. You can ask support about a record, while removal depends on local law and required retention.

tag4d Privacy Policy for Your Account

Where To Ask About Privacy Policy

Six Practical Rules Behind Our Policy

Phone verification

Session signals

Cookie controls

Payment matching

Retention checks

Policy contact

Privacy Policy Questions About tag4d

01 What does the tag4d Privacy Policy cover?

02 Why does tag4d need my phone number?

03 Does the Privacy Policy collect my wallet PIN?

04 How can I request my tag4d account data?

05 Can I ask tag4d to correct my personal data?

06 How do cookies affect my Privacy Policy choices?

07 How long does tag4d keep account and payment data?

Related Pages