Reference

taxsi4d Privacy Policy for Your Account

The taxsi4d Privacy Policy tells you what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet records explainedMobile cookie choicesAccount request path
taxsi4d taxsi4d Privacy Policy for Your Account
REQUEST HELP

Get Privacy Help Through Your Account

A clear support route helps when a privacy question is separate from a wallet status issue. Sign in first when you can, then use the account support path to identify the relevant profile or payment reference. If login is unavailable, share only the minimum details needed for us to locate the request. We do not ask for your full wallet password in a privacy conversation.

Team online

Account data request

Use the support path shown after sign-in and state whether you need a copy, correction or explanation of account records. We may ask for phone verification before releasing personal details.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the date and displayed reference only. We use those details to check the correct record without requesting your wallet password.

Privacy access issue

If the mobile account path stalls, return to the sign-in screen and use the available account help route. Tell us which step failed, such as phone verification or the request form.

HANDLING YOUR DATA

How We Apply This Privacy Policy

We keep the Privacy Policy practical by linking each data use to an account action or a security need.

Account details

We use the name, phone number and verification details you submit to create and protect your account. Phone verification helps us distinguish an account request from an unapproved attempt to enter your profile.

Device behaviour

A mobile browser may send device, browser and session signals when you sign in or move between the lobby and account pages. These signals help identify repeated or unusual access patterns.

Cookies

Session cookies help keep your sign-in state while you move through account pages. Preference cookies remember choices where available; you can clear browser cookies, although this may require another sign-in.

Wallet references

Payment records may contain a rail name, amount reference, status and time linked to your account. We use this information to match DANA, QRIS, bank transfer or virtual account activity.

Security controls

We use phone verification, account checks and restricted internal access to reduce unauthorised handling. Never send a password or one-time code through a support conversation, even when asking about your data.

Retention and changes

We retain records only for the period needed for account service, security checks, dispute handling and legal duties. Ask through the account support path to request correction, access or deletion where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account steps we see most often, including phone verification, mobile browsing and local wallet references. We explain the request path in plain English so you know what to send and what may be checked before we respond. Any right or restriction depends on local law.

It explains how we collect and use account details, phone verification records, device signals, cookies, support messages and payment references to provide access, protect the account and answer lawful requests.

Phone verification helps confirm that the person requesting account access or a data change controls the registered number. We may use that step before sharing, correcting or removing personal records.

Yes. It covers transaction references and status details linked to those rails. We use them to match wallet activity with the correct account, while your wallet password remains outside our support request.

Session cookies help maintain sign-in while you move through account pages. Preference cookies may remember selected settings. Clearing cookies can remove the session and require phone verification or another sign-in.

Use the account support path and ask for a data copy. Include your registered phone number only through the protected request flow. We may verify account control before releasing personal records.

You can ask through the support path for correction or deletion. We assess the request against account security, transaction records and duties that depend on local law, then explain any retained items.

We keep records for the period needed for account service, security checks, payment disputes and legal duties. The exact period can differ by record type and depends on local law.