Reference

Privacy Policy For Your octagon 4d Account

The octagon 4d Privacy Policy explains how we handle the details you provide when opening an account, checking DANA or QRIS status, and using the lobby on mobile…

Account dataWallet recordsCookie choicesDevice security
octagon 4d Privacy Policy For Your octagon 4d Account
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact path matters when a Privacy Policy question affects your account. Start from the signed-in account help route and include the phone number connected to your profile, the subject of your request and any relevant payment reference. We can then separate a data question from a wallet-status question without asking you to publish sensitive credentials. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account matters, attach only the receipt details needed to locate the event.

Team online

Account data request

Use the account help route to ask which personal details are linked to your octagon 4d profile. We may ask for phone verification before responding, because confirming account ownership prevents another person from receiving your sign-in or wallet history.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate time rather than a password or full wallet access detail. Our support path uses those details to locate the relevant entry and explain its status.

Correction or removal

If a profile detail is wrong or you want to ask about deletion, state the specific field and the reason for your request through account support. We check identity first, then explain whether retention is still required by local law.

DATA HANDLING

Inside octagon 4d Privacy Controls

Privacy work happens across the account journey rather than in one isolated screen. We separate ordinary profile details from payment references, limit access to operational needs and use phone verification before account…

Account details

We use the details you submit for account creation, phone verification, sign-in support and requests made through your profile. Keeping your phone number current helps us confirm that a privacy request comes from you instead of releasing account material to an unknown contact.

Cookies and sessions

Cookies can keep your signed-in path available and help us understand whether a session is behaving normally. Your browser settings can control some cookie activity, but changing them may affect access to the account area or require you to sign in again.

Device signals

A mobile or desktop session may provide device and connection signals used to protect account access. These signals can help us spot an unfamiliar sign-in around the lobby, including a switch from a phone session to a computer.

Payment references

We retain references needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the correct account record. We use the reference to check status and reconciliation, not to request your wallet password.

Security actions

Phone verification, session checks and account contact confirmation help us protect personal data. If an access event looks unusual, we may pause the request and ask you to confirm ownership before discussing profile or payment records.

Retention and changes

We keep records only as long as they serve account support, security, reconciliation or a requirement that depends on local law. You can ask for a correction, access copy or deletion assessment through the account support route.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open access from Indonesia. They cover the information connected with phone verification, cookies, devices and local payment records, while keeping the next step practical. If your request concerns a specific event, include the account contact and payment reference through support. Eligibility and access depends on local law, so we may need to explain why a request or account action has a particular limit.

It covers personal details you submit, phone verification, sign-in activity, cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purpose, retention, security measures and the requests you can send.

Phone verification helps us confirm account ownership before access or a sensitive data request. It can protect your profile when a device changes or a sign-in looks unusual. We use the verification result for account security and support handling, not as a request for wallet credentials.

Yes. The Privacy Policy covers payment references and status details needed to match a DANA or QRIS event with your account. The same applies to OVO, GoPay, bank transfer and virtual account records. Send only the reference needed for support to locate the transaction.

Open the account support route, identify the profile field that needs correction and provide the phone number connected to your account. We may verify ownership before changing it. If the detail relates to a payment record, include its reference so we can separate a profile error from reconciliation data.

We retain a record for as long as it is needed for account support, security checks, payment reconciliation or a requirement that depends on local law. The period can differ by record type. You can ask support about a specific category and whether deletion assessment is available.

You can ask for an access copy through the account contact route. Describe the account and the data category you want, such as profile details, device activity or wallet references. We confirm identity first and explain the response process where local law permits that request.

Send the complaint through signed-in account support and describe the privacy event, date and affected data category. Do not include a password, wallet PIN or unnecessary identity documents. We use the account contact path to verify ownership and route the matter to the appropriate privacy handler.