Reference

tape4d Privacy Policy for Your Account Data

Your account data, wallet status and login checks have one clear home in the tape4d Privacy Policy.

Account dataWallet recordsCookie choicesAccess requests

Know How Your Account Records Are Used

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

Our Privacy Policy covers the details you provide during account creation, including contact details, verification responses and login activity. It also covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. We use these records to process account actions, check wallet

1
status, protect access and respond to support requests; we do not describe them as a public profile. Device signals may help us recognise a returning browser and investigate unusual sign-in behaviour. Cookies can keep a session open or remember a preference, and you can manage them
2
through your browser settings. We keep records for the period needed for these purposes and for applicable legal duties. Access to tape4d services and any related data request depends on local law. If you need a copy, correction or clarification, contact us through the account support
3
path and include the email or phone detail linked to your account.

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

REQUEST HELP

Get Clear Answers About Privacy Policy

A direct support route helps you handle a data question without guessing which team to contact.

Account privacy request Open the support path from your logged-in account and state whether you need access, correction or removal of personal data. We may ask for an account detail before responding.

Wallet record question For a DANA, OVO, GoPay or QRIS record, include the transaction reference and date rather than sending a full wallet password. This lets us check the right account event.

Security concern If a login or device entry looks unfamiliar, contact account support promptly, change your password and avoid sharing verification codes while we review the access concern.

HANDLING DETAILS

See What We Do With Privacy Requests

The practical side of our Privacy Policy is visible in the account steps we use every day: collection at verification, restricted access for support work, cookie controls in your browser and retention…

Data collection

We collect details needed for account creation, phone verification, login checks and support replies. If you choose DANA, OVO, GoPay or QRIS, transaction references may be attached to your account history.

Cookie controls

Our cookies can support session continuity and remember selected settings on a mobile browser. You can inspect or clear them through browser controls, although clearing them may require another account login.

Account security

Phone verification comes before account access, while login activity and device signals can help identify unusual entry. Never send a password or one-time code through a support message.

Retention approach

We keep account, support and payment-reference records only for the time needed to provide the requested service, address disputes, protect access or meet applicable legal duties.

Requesting changes

To correct a name, phone detail or other account field, use the logged-in support path and describe the requested change. We may verify control of the account before editing it.

Who to contact

Our account support route handles Privacy Policy questions, access requests and deletion queries. Include your account email or phone detail, but leave out passwords, wallet PINs and verification codes.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the questions we expect before you open an account or ask us to change a record. They cover Indonesian payment references, cookies, verification, retention and the support route, with access handled where local law permits.

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

Phone verification helps connect account access to the correct person and assists with unusual-login checks. We use the submitted contact detail for account security and support handling, subject to local law.

Yes. The policy covers transaction references and wallet status connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account activity. We do not ask for wallet PINs.

Use the support path inside your logged-in account, ask for an access copy and provide the email or phone detail linked to the account. We may verify account control first.

Yes. Send a correction request through account support and identify the field that needs changing. We may request verification before editing the record, and access depends on local law.

Cookies can preserve a login session and selected browser settings when you reach the lobby on a phone. Your browser can clear or block them, which may trigger another login.

Contact us through the logged-in account support route and request deletion or clarification. Tell us which record is involved, and we will explain what can be removed where local law permits.

tape4d Privacy Policy for Your Account Data

Get Clear Answers About Privacy Policy

See What We Do With Privacy Requests

Data collection

Cookie controls

Account security

Retention approach

Requesting changes

Who to contact

Privacy Policy Answers Before Account Access

01 What does the tape4d Privacy Policy cover?

02 Why does tape4d need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How can I request a copy of my account data?

05 Can I ask tape4d to correct my personal data?

06 How does tape4d use cookies on mobile?

07 Where do I ask about Privacy Policy or deletion?

Related Pages