Reference

Privacy Policy For Your manual4d Account

manual4d Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby on your phone or desktop.

Clear data purposesWallet activity contextAccount access controlsCookie choices
manual4d Privacy Policy For Your manual4d Account
CONTACT ROUTES

Reach Us About Privacy Requests

A clear contact path helps when you want to ask about your Privacy Policy rights or account records.

Account privacy Send a request through our account support channel when you want to ask what personal details we hold, why they are used or which account step created the record. Include your registered phone number and a short description so we can route the Privacy Policy request correctly.
Wallet records For a Privacy Policy question involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, attach the relevant date and receipt number without sharing your wallet password or one-time code. We use those details to find the right payment record while limiting exposure.
Access concerns If your account behaves differently after a phone change, browser reset or sign-in check, contact us through the same support route before opening another account. We can compare the device session with your account record and explain the data step connected to access.
DATA PRACTICE

How We Handle Your Account Data

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Account details

When you open an account, we collect the details needed to create and protect that account, such as your phone number and verification status. We use them for sign-in checks and requested account service, not as a reason to ask for your DANA, OVO or GoPay password.

Payment references

A wallet or bank record can show a reference, amount status and time connected with your request. We use that limited payment context to match DANA, QRIS, virtual account and bank transfer enquiries, while your external wallet credentials remain outside our requested account details.

Device sessions

Your phone or desktop may send browser, operating system and session signals when you sign in. These signals help us identify an unexpected session or repeated OTP request, and they also help explain why access looks different after clearing cookies or changing devices.

Cookies

Cookies can keep a session active, remember basic page settings and support the path from login to the lobby. You can manage cookies through your browser controls, although removing them may require another sign-in or make account pages behave differently on that device.

Retention choices

We retain account and transaction records only for the operational, security and legal purposes connected with the service. When you ask how long a particular record remains, tell us whether it concerns login, a wallet reference or a support exchange so we can answer precisely.

Change requests

You can ask us to correct inaccurate account details, explain a data use or provide a copy where the request is available under applicable rules. We may verify the phone linked to your account before making a change, so another person cannot alter your record.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the account situations you are most likely to meet on manual4d, from a first phone verification to a QRIS receipt or a new-device sign-in. We keep the wording direct so you can decide which support route fits your request. Access remains where local law permits, and account checks may be needed before we discuss personal records.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those details and how you can contact us about them.

We may collect your phone number, verification status and details needed to maintain the account path. Sign-in can also create device, browser and session records. Payment enquiries may include a reference and status, but we do not ask for your external wallet password.

DANA and QRIS references help us match a payment question with the correct account activity. The same applies to OVO, GoPay, bank transfer and virtual account records. We use the reference, timing and status needed for the request, not your wallet login credentials.

Use the account support route beside the cashier area and state whether you want access, correction or an explanation of use. Include your account phone number and the relevant record type. We may complete a phone verification step before releasing or changing personal data.

Cookies may keep your session, remember basic settings and support the move from login to the lobby. You can remove or restrict them in your browser. After that change, you may need to sign in again, and some account pages may not retain their previous state.

Retention depends on the purpose of the record, including account security, payment tracing, support handling and legal duties. Ask us about a specific login, QRIS receipt, bank transfer reference or support exchange. We can then explain the applicable retention position for that record.

You can send a deletion request through account support, and we will assess it under the rules that apply to your account and the record concerned. Some data may need to remain for security, transaction tracing or legal duties. Access depends on local law.