Reference

Privacy Policy For Your bitung4d Account

Our Privacy Policy explains how we collect, use and protect details connected with your bitung4d account, wallet activity and device access.

Account clarityWallet recordsDevice controlsPolicy contact
bitung4d Privacy Policy For Your bitung4d Account
CONTACT OPTIONS

Reach Us About Privacy Policy

A clear contact path helps you control your account data without guessing which team to reach.

Account privacy request Ask us to access, correct or remove eligible account details through the account support channel. Include your registered contact detail and the specific request so we can route it to the privacy team after an account check.
Payment record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, send the reference number and date. We use those details to find the payment event while avoiding requests for your wallet password or PIN.
Device access concern If a sign-in alert or session looks unfamiliar, contact support from the account area and describe the device and approximate time. We can review account access records and guide the next verification step where local law permits.
DATA CARE DETAILS

What We Do With Your Account Data

Privacy Policy choices should be practical, so we describe the handling steps behind everyday account activity.

Account details

We use your registered phone or email to send account notices, complete a clear verification step and help recover access. Keep those details current, because an outdated contact route can delay a privacy request or account change.

Wallet references

A payment record can include the rail used, reference code, amount, status and timestamp. DANA, OVO, GoPay and QRIS details help us reconcile a cashier event; we do not need your wallet PIN to check that record.

Cookies and sessions

Our site may store session cookies and device settings so your account remains consistent while you move from login to the lobby. Browser controls can limit cookies, although some account and privacy functions may then require another sign-in.

Account protection

We use login events, device signals and verification steps to reduce unauthorised access. If your account opens on a new phone, a check may be required before profile or payment records are shown, including when you use a mobile browser.

Retention choices

We retain account and transaction records for the period needed to provide service, resolve a payment dispute, investigate suspicious activity and meet legal duties. When a record is no longer needed for those purposes, our process removes or de-identifies it where permitted.

Changing your data

You can ask us to correct inaccurate contact details or clarify the records linked to your account. Send the request through support with enough detail to locate the profile; we may verify ownership before making a change or confirming what can be removed.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with bitung4d login activity, local wallet records, cookies, device checks and requests for access or correction. If your case involves a specific payment reference or an unusual sign-in, use the support route rather than sending sensitive wallet credentials. Any access or eligibility decision depends on local law.

The bitung4d Privacy Policy covers account contact details, verification records, login events, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask about access or correction where local law permits.

These rails create account-linked payment records such as a reference code, amount, status and timestamp. Our Privacy Policy explains how we use that data to match a cashier event, investigate a missing status or handle a dispute without requesting your wallet PIN or password.

Yes. Send an access request through the support channel in your account area and identify the phone or email attached to your profile. We may complete an ownership check before sharing eligible records, and the response can be limited by legal, fraud-prevention or dispute requirements.

Tell us which account detail is inaccurate, such as an outdated phone or email address, through account support. We verify the request before changing the profile. If the detail appears in a payment or dispute record, we may preserve the original event while adding the corrected context.

It does. Cookies and similar storage can keep a signed-in session, remember selected settings and help us identify loading problems on a mobile browser. You can adjust browser controls, but limiting storage may require repeated login or affect account functions that depend on a current session.

We keep records for the time needed to provide account service, resolve payment questions, examine suspicious activity and meet legal duties. The period varies by record type. When a record no longer serves those purposes, our process removes or de-identifies it where local law permits.

Use the support channel linked from your bitung4d account and describe the privacy concern plainly. Include a relevant account detail or payment reference, but never send a wallet PIN or password. We may ask for identity confirmation before discussing records or changing account data.