Reference

aksara4d Privacy Policy for Your Account

Our Privacy Policy explains how aksara4d handles the account details, device signals and wallet records you provide when you open an account or reach the lobby.

Account clarityWallet recordsCookie choicesPolicy requests

Browse Our Lobby Read FAQ

How Your Account Data Is Used

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

This Privacy Policy describes the data we collect when you create an account, verify your phone, sign in, contact support or check a wallet status. We may handle your account name, phone number, login events, device details, browser settings, selected lobby pages and records needed to

1
match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction. We use those records to provide account access, investigate a receipt, identify unusual sign-in activity and answer a policy request. We do not ask you to send payment credentials through an open chat. Access
2
and eligibility depends on local law, and our handling can change when a legal requirement applies. The current Privacy Policy remains available through the policy link connected to your account area.

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

POLICY HELP PATHS

Where to Ask About Privacy Policy

A clear contact route helps when you need to ask about a record, cookie or account detail.

Account contact Use the support route shown after account access and identify your registered phone number. We can then connect a Privacy Policy question with the correct account record without asking you to post sensitive wallet credentials.

Wallet record check For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference and date through the account support path. We use those details to locate the relevant status without requesting your wallet password.

Policy request Ask for access, correction or removal through the privacy contact path linked from our policy area. We may ask for an account step that confirms the request belongs to you before making a change.

SIX HANDLING PROMISES

What Our Privacy Process Covers

Privacy work follows the same account path you already use: phone verification, sign-in, wallet status and support contact.

Collected data

We may record your phone number, account actions, sign-in time, browser type and device signals. These details help us connect a Privacy Policy request to the right account and distinguish a new session from a repeated login.

Cookie controls

Cookies and similar browser storage can remember session choices and help us understand which policy page you opened. You can manage browser permissions, although turning them off may require another sign-in step.

Account security

Phone verification comes before account access, while sign-in and device events can be checked when a session looks unusual. We use these signals to protect your account without asking for a DANA, OVO or bank password.

Retention period

We retain account, support and transaction-linked records only for the period needed for account operations, dispute handling, legal duties or security checks. When a record is no longer needed, our handling process removes or separates it.

Correction request

If your phone detail or account record is inaccurate, contact us through the policy route and state the correction clearly. We may compare the request with your verified account step before updating the record.

Access request

You can ask which personal records we hold and why they are used through the support path connected to this Privacy Policy. We will explain any identity check needed before releasing account-linked details.

Privacy Policy Questions You May Have

These answers address the searches we hear most often about the aksara4d Privacy Policy. They cover account creation, device activity, cookies, wallet records and requests for access or correction, so you can decide what to share before opening an account.

It covers account details, phone verification, sign-in and device activity, cookies, support messages and transaction-linked records for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number for the account step before access, session confirmation and policy-request checks. It helps us connect a correction or access request with the correct account.

Yes. We may handle browser type, device signals, session events and cookie settings when you open the lobby on mobile or desktop. These records support session security and account troubleshooting.

We may retain transaction references, dates and status details needed to match a DANA or QRIS receipt with your account. We do not ask you to send a wallet PIN or full banking credential.

You can ask through the privacy contact path linked to your account area. We may first confirm your phone or another account step, then explain which personal records can be provided.

Send the requested correction through the support route connected to this policy and describe the inaccurate field. We compare it with your verified account record before changing the stored detail.

Retention depends on the record and its purpose, such as account operation, receipt checks, security or legal duties. When the applicable need ends, we remove or separate the record.

aksara4d Privacy Policy for Your Account

Where to Ask About Privacy Policy

What Our Privacy Process Covers

Collected data

Cookie controls

Account security

Retention period

Correction request

Access request

Privacy Policy Questions You May Have

01 What does the aksara4d Privacy Policy cover?

02 Why does aksara4d need my phone number?

03 Does the Privacy Policy include mobile device data?

04 How are DANA and QRIS records handled?

05 Can I request a copy of my account data?

06 How do I correct details under the Privacy Policy?

07 How long does aksara4d keep personal data?

Related Pages