Reference

Privacy Policy for inbox4d Accounts

Our Privacy Policy explains how inbox4d handles the details connected with your account, including phone verification, wallet activity and access from your device.

Account dataWallet recordsCookie choicesContact path
inbox4d Privacy Policy for inbox4d Accounts
CONTACT YOUR WAY

Where To Ask About Privacy Policy

A clear contact route makes a Privacy Policy useful when you need an answer about your account record. We ask you to begin from the inbox4d account area and include the phone number linked to your profile, the topic of your request and any relevant payment reference. Do not send a password, one-time code or full wallet credentials. For a request about DANA, QRIS or a bank transfer, the payment status and date help us locate the right record without unnecessary personal details.

Team online

Account privacy request

Use the account contact path to ask which personal details are associated with your profile, why a detail is needed or how to request a correction. Include your verified phone number and keep passwords and one-time codes out of the message.

Wallet record question

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the payment date and visible reference only. We use those details to locate the relevant record while avoiding unnecessary wallet credentials.

Access and cookie help

For a cookie choice or device-session question, tell us whether you are using mobile or desktop and describe the account step where the issue appears. We can then separate a privacy request from a normal sign-in status question.

OUR HANDLING PRACTICE

What This Privacy Policy Covers

We use this policy to connect everyday account actions with clear data-handling choices. Phone verification supports account access; payment references support wallet-status checks; and device-session details help us…

Account details

We may handle the phone number and account details you provide during account access.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that a wallet event relates to your account.

Device sessions

When you switch between a mobile browser and desktop, technical session details can help us identify access events and protect…

Cookies

Cookies can support sign-in continuity, remember a selected setting or help us understand whether a page session is working.

Retention

We retain personal and payment-related records only for the purposes and periods set out in this Privacy Policy or required…

Policy changes

If the Privacy Policy changes, we will place the revised wording on this page and identify the updated policy date…

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening or using an inbox4d account. They cover access, wallet records, cookies, corrections and contact steps without asking you to disclose private credentials. For a case-specific answer, use the account contact path and provide only the details needed to locate your record.

It explains how we handle account details, phone verification records, device sessions, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also describes contact routes, retention purposes and requests to correct or update personal details.

We use your phone number for the account step that confirms access belongs to you. It can also help us locate the correct profile when you ask about a Privacy Policy matter. Do not include your password or one-time code in a contact request.

Yes. The policy covers payment references connected with QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account records. We use a visible reference, date or status detail to check the relevant event without asking for full wallet credentials.

Cookies may help maintain a sign-in session, remember a setting or show whether an account page is working correctly. Your browser provides cookie controls. If you change those settings, some account or policy-page functions may not behave in the same way.

Where local law permits, you can ask us to correct or update personal details linked to your account. Start from the account contact path, identify the detail that needs attention and include your verified phone number. We may need to confirm account ownership first.

Retention depends on the purpose of the record and the periods described in this Privacy Policy, including any period required where local law permits. We do not ask you to guess the retention period; contact us with the record type and we can address the request.

Yes. Ask us to identify the account details, device-session data, cookie context or payment references associated with your profile. For a DANA, QRIS or bank transfer question, provide the date and visible reference only, not your password or wallet credentials.