Reference

Privacy Policy for Your Account Path

Our angkasa 338 Privacy Policy explains what we collect when you create an account, sign in on a phone, or connect DANA, OVO, GoPay or QRIS.

Account recordsWallet referencesCookie choicesPolicy requests

Browse Our Lobby Read FAQ

How Privacy Rules Follow Wallet Activity

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

This Privacy Policy covers details linked to your account path, including contact information, verification events, sign-in records, device signals and support messages. When you select DANA, OVO, GoPay or QRIS, we may retain a payment reference or status needed to match your request; we do not

1
use that context to describe your private wallet balance beyond the relevant transaction record. Bank transfer and virtual account references can also appear in an account history. We limit internal access to people who need it for account checks, payment reconciliation, fraud screening or policy requests.
2
Storage and access depends on local law, and we apply the rules that govern your location where local law permits.

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

REQUEST ROUTE

Three Ways to Ask About Personal Data

A clear request helps us locate the right record without exposing another account. Use the account support route when your sign-in or verification detail needs correction, and include the email or phone…

Account correction Ask us to amend a name, phone detail or email connected with your account. We may request a sign-in confirmation before making the change, so a correction cannot be applied to the wrong account.

Wallet record query Send the payment rail and receipt reference when a DANA, OVO, GoPay or QRIS record looks unfamiliar. We use the matching account and transaction date to investigate the privacy request.

Access request Request the personal data associated with your account through our support path. Include your account contact detail and device sign-in context; we verify ownership before sharing a response.

HANDLING DETAILS

Six Practical Controls Behind This Policy

We handle privacy as an operating task rather than a footer statement. A new account starts with the contact detail you submit, then sign-in and phone verification events help us separate your…

Account collection

We collect the contact and verification details you provide during the account step. A phone check can be recorded as an access event, helping us confirm that a later sign-in belongs to the same account.

Device signals

When you move from phone login to the lobby, we may record device and session signals such as access time. These details help us investigate unusual sign-ins without treating every new device as a policy breach.

Cookie controls

Cookies can keep the account path working between sign-in and the next page. You can adjust cookie settings in your browser; limiting them may affect saved session details and require another login.

Payment matching

A DANA, OVO, GoPay or QRIS reference may be retained to match a receipt with the correct account. The record supports status checks and does not replace the wallet provider's own privacy rules.

Retention choices

We retain account, access and transaction references only while they serve account operations, dispute handling, security checks or applicable legal duties. When a record is no longer needed, our handling follows the rules that apply to it.

Change requests

Contact us when your personal detail is wrong, your data request needs clarification or you want to ask about removal. We first confirm account ownership, then explain what can be changed under local requirements.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account records, wallet references, cookies, device access and requests for changes. If your question concerns a specific DANA, OVO, GoPay or QRIS receipt, include its reference when contacting support so we can follow the correct account path.

It covers personal details linked to your account, sign-in and phone verification events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can request access or correction under the rules applying to your location.

Yes. The Privacy Policy explains how we handle a payment reference or receipt status connected with DANA, OVO, GoPay or QRIS. We use that record to match an account request or payment check, while the wallet provider remains responsible for its own data practices.

Contact our account support path with the email or phone detail attached to your account and ask for a data access request. We verify ownership before responding, which helps prevent another person from receiving your account records or device-linked details.

You can ask us to correct an account name, phone detail or email when it is inaccurate. Include the affected detail and your account contact path. We may ask for phone verification or another ownership check before applying the change.

Cookies can maintain a session between phone sign-in and the lobby, remember selected access settings and help us understand a failed page path. Browser controls let you limit them, although you may need to sign in again or lose saved session details.

We keep account, access, support and payment-reference records while they are needed for account operations, security checks, disputes or applicable legal duties. The period can differ by record type and location; where local law permits, you may ask why a record remains.

Use the support route and explain whether the issue concerns login, phone verification, a DANA or QRIS receipt, or another record. We check ownership first and can explain the next step. Account access and eligibility depends on local law.

Privacy Policy for Your Account Path

Three Ways to Ask About Personal Data

Six Practical Controls Behind This Policy

Account collection

Device signals

Cookie controls

Payment matching

Retention choices

Change requests

Privacy Policy Answers for Indonesian Accounts

01 What does the angkasa 338 Privacy Policy cover?

02 Does the Privacy Policy cover DANA, OVO, GoPay and QRIS?

03 How can I request my angkasa 338 account data?

04 Can I correct personal details in this Privacy Policy record?

05 How do cookies affect my Privacy Policy choices?

06 How long does angkasa 338 keep my personal data?

07 What if I cannot access an account data request?

Related Pages