Reference

akar555 Privacy Policy for Your Account

Clear account control starts before you enter the lobby. Our akar555 Privacy Policy explains what we collect during phone verification, how DANA and QRIS status data is used…

Account dataWallet statusCookie choicesAccess requests
akar555 akar555 Privacy Policy for Your Account
PRIVACY SUPPORT

Reach Us About Account Privacy

Privacy questions should have a clear route, especially when a wallet reference or phone check does not match your account. We connect privacy requests with the account-help path beside the cashier area, so you can provide the relevant transaction status without sending unnecessary credentials. Use the details below to ask about access, correction, deletion eligibility or a confusing cookie setting. We may ask for account verification before changing personal data, because the request must come from the account holder.

Team online

Account privacy path

Open the account help route and choose the privacy subject when you need to ask about stored phone details, login records or a correction. We use the account step to connect your request with the right record without asking you to share a wallet password.

Wallet status check

For DANA, OVO, GoPay or QRIS questions, include the visible transaction reference and its status from the cashier path. We can investigate a mismatch while keeping the request focused on payment metadata rather than collecting unrelated account content.

Privacy request follow-up

If you ask for access, correction or an eligible removal, we may confirm your phone-verified account first. That step protects your details from an unauthorised request and lets us explain which records must remain for account or legal reasons.

DATA CONTROLS

See How We Protect Your Details

We handle privacy as part of the account path, not as a separate promise hidden from your wallet and login screens.

Account data handling

We use your phone number and account details to complete the account step, support phone verification and connect activity to the correct profile. We do not ask for a wallet password through our privacy route, and we keep requests limited to the issue you raise.

Cookies and device signals

Cookies can remember a session choice, while device and browser signals help us detect repeated login attempts or unusual access. You can clear browser storage through your device settings, although doing so may require another account login or verification step.

Login protection

Phone verification is checked before account access, and security records may include login time, browser details and device signals. If a login or wallet status stalls, share the visible account reference through support instead of sending passwords or private wallet credentials.

Record retention

We retain account, security and payment references for the period needed to operate the account, settle disputes and meet applicable legal duties. When that period ends, records are removed or separated from direct account identification where the applicable process allows.

Who handles a request

Our account privacy route receives questions about personal data, cookies and transaction references. We may involve the internal team responsible for account security or payment reconciliation, but the request remains tied to your verified account and its stated purpose.

Changing your details

Ask us to correct an inaccurate phone detail, account identifier or contact record through account help. We check the request against your verified account, explain any records that cannot be changed, and confirm the outcome through the same privacy route.

Ask About akar555 Privacy Policy

These Privacy Policy answers focus on the searches we hear most often before an account is opened. They cover payment references, phone verification, cookies, account access and requests to see or correct personal data. If your situation involves a specific DANA, QRIS or bank transfer reference, use the account privacy path so we can check the exact record.

It covers account details, phone verification, login and device records, cookies, wallet status and transaction references. It also explains retention, security controls and how to request access or correction. Eligibility and access depend on local law, so the policy is read together with applicable local requirements.

No. For DANA and QRIS, we use the transaction reference and visible status needed to match a wallet action with your account. We do not need your wallet password for that check. The same approach applies to OVO, GoPay, bank transfer and virtual account references.

Phone verification connects the account request to the correct account holder and helps protect access from an unauthorised attempt. We may retain the verification result and related security record. If your number is inaccurate, request a correction through account help after signing in.

Cookies and similar browser storage can remember a session choice and help us understand page performance. You can clear them through your browser or device settings. Clearing storage may sign you out or require phone verification again, but it does not automatically delete account records.

Yes, you can request access or correction through the account privacy path. We first confirm the phone-verified account, then identify the relevant record and explain the result. Some security or payment records may need to remain for dispute handling or applicable legal duties.

Payment references are kept for the operational period needed to reconcile wallet or bank activity, address disputes and meet applicable legal duties. The period can differ by record type. Afterward, we remove or separate direct identifiers where the applicable process allows.

Use the account help route and select the privacy subject, including when access is unavailable or depends on local law. Share only the account reference and visible status needed for identification. We may request verification before discussing personal data or changing account details.