Reference

Privacy Policy For Your between Account

The between Privacy Policy explains what account details we collect, why we use them and how you can ask about them before opening an account.

Clear data purposesPhone verificationDANA and QRIS context
between Privacy Policy For Your between Account
ASK ABOUT DATA

Get Help With Privacy Policy Requests

A clear contact path helps when you want to ask about the Privacy Policy, check an account detail or request a correction. We keep privacy questions close to the same account and payment context used for phone verification, so your request can be matched without guesswork. Include the account email or verified phone reference, the page involved and the change you want us to check. For Jakarta account access, wallet status and privacy questions, use the support route shown in your account area.

Team online

Account privacy

Ask which account details are held, why they are used and how the Privacy Policy applies to your sign-in, phone verification and device access. Include a reachable account reference so we can check the correct record before replying.

Payment records

If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer, send the payment reference and date through the account support path. We can then distinguish a wallet status question from a request about personal data.

Correction request

Tell us which detail needs changing and provide the account reference connected to it. We may ask for a verification step before making an update, helping keep another person from changing your contact or payment record.

CONTROL YOUR DETAILS

What We Do With Account Data

Privacy Policy choices matter most when they match the way an account works. We describe the practical controls available to you: asking what we hold, requesting a correction, raising a concern about…

Data collection

We may collect details you enter during account creation, along with sign-in, device and payment-reference data created while you use the service. The Privacy Policy links each category to an operating purpose rather than treating every detail alike.

Purpose of use

Account data helps us provide access, complete phone verification, show wallet status and respond to support messages. Payment references can help trace a DANA, QRIS or bank-transfer question without requiring you to repeat the entire account history.

Cookies

Cookies and similar device signals may help keep pages working, remember session choices and identify unusual sign-in behaviour. Your browser settings can affect these functions, so the Privacy Policy explains their role alongside ordinary account controls.

Account security

We use account checks such as phone verification and sign-in review to reduce unauthorised access. Never send a password in a privacy request. If a device or contact detail looks wrong, raise it through the account support path.

Retention

Records are kept for the period needed for the purpose described in the Privacy Policy, including account operation, payment tracing and security checks. Retention can vary by record type, so ask us about the category connected to your request.

Your request

You can ask about access, correction, use or retention of your personal details. Provide enough account context for us to locate the record, and we may verify your identity before discussing or changing it.

Privacy Policy Answers For between

These Privacy Policy answers cover the account questions most often raised before access: what we collect, how payment references are used, how to request a change and what local eligibility means. Read them with the full policy and contact support when your situation involves a specific account record.

The between Privacy Policy covers details connected with your account and use of the service, including contact data, phone verification, sign-in activity, device signals, payment references and support messages. It also explains purposes, sharing, cookies, retention and ways to request access or correction.

We can collect details you enter for an account, verified contact details, device and sign-in activity, payment references and messages you send through support. The Privacy Policy explains why each category may be needed for access, security, payment tracing or account assistance.

DANA, OVO, GoPay and QRIS references can help us identify a wallet status or payment question. We use the reference for the stated account and payment purpose, not as a replacement for your account identity. Contact support with the date and reference when checking a record.

Yes. You can request a correction when a contact, account or related record is inaccurate. Tell us which field needs attention and provide a reachable account reference. We may complete phone or identity verification before changing it, so another person cannot alter your record.

Use the account support path and state that your request concerns the between Privacy Policy. Include your account email or verified phone reference, the data category you want checked and a clear way to reply. We may verify identity before sharing account-linked details.

Retention depends on the record type and the purpose described in the Privacy Policy. Account operation, payment tracing and security checks may require different periods. Ask support about the category involved, and we will explain the applicable handling without asking you to resend unrelated data.

Yes. Account access and eligibility depends on local law, including the rules relevant to your location. The Privacy Policy explains data handling for supported access, but it does not change local requirements. Check your position before opening or continuing an account.