Reference

tag4d Terms & Conditions for Your Account

Your account path, wallet status and access to titles such as Blackjack and Asgardian Rising are covered in the tag4d Terms & Conditions.

Account stepsWallet rulesLocal-law accessPolicy contacts
tag4d tag4d Terms & Conditions for Your Account
POLICY HELP

Where To Raise A Terms Question

A clear contact route matters when a clause affects your account or wallet status. We direct policy questions through the support path shown inside your account, close to the cashier area, so…

Account access Tell us which Terms & Conditions clause relates to your phone verification or login step. We can check the account record without asking you to send a password.
Wallet status For DANA, OVO, GoPay or QRIS questions, include the receipt reference and displayed status. We use those details to match the payment record with the account clause.
Policy request Ask for clarification, a copy of the applicable wording or a correction route through the account support contact. We will point you to the relevant Terms & Conditions section.
DATA PRACTICES

How tag4d Handles Account Policy

Our Terms & Conditions work alongside practical account controls rather than replacing them. We use the details needed to verify access, match payment records and protect the account, while cookies help the…

Account data

We handle the account details needed for registration, phone verification and account access. The Terms & Conditions explain why those details are used and how you can ask about them.

Payment records

A DANA, OVO, GoPay or QRIS receipt may be matched with your account status. This helps us address a missing update without requesting your wallet password or PIN.

Cookies

Cookies can support the session and device behaviour needed to keep you signed in during an account visit. Our policy sets out their role and the choices available in your browser.

Account security

Keep your password and phone access private, and contact us through the displayed support route if you see an unfamiliar account action. We do not ask you to share a password.

Data retention

The Terms & Conditions describe how long relevant account and payment records may be kept for account handling, checks and legal duties, subject to where local law permits.

Change requests

If your account details need correction, use the policy contact path and identify the field that needs attention. We will explain the next account step and any required verification.

Terms & Conditions Questions Before Opening

These answers cover the clauses you are most likely to check before creating an account. We keep the wording practical, with direct references to phone verification, local wallets, device access and requests about stored account data.

They are the agreement governing your tag4d account, access steps, payment records, policy contacts, cookies, security checks and account data handling. Read them before accepting the account terms.

Yes. Account access and eligibility depends on local law. Where local law permits, you must still complete the stated account step, including phone verification before access is enabled.

They cover account records connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account steps. A receipt or status check may be needed before the record is updated.

Yes. You can read the Terms & Conditions before choosing the account path. Check the phone verification clause, wallet wording and local-law access statement before you accept.

We may pause access while checking account ownership, phone verification or a payment record. Use the displayed support route, provide the relevant receipt or account detail, and follow the requested step.

Use the policy contact path shown in your account and identify the data field that needs correction. We may ask for an account check before applying or explaining the requested change.

Send the question through the account support contact and name the cookie, retention or account-data clause. We will direct you to the applicable Terms & Conditions wording and request route.