Reference

atm4d Privacy Policy For Your Account

Our Privacy Policy explains what atm4d collects when you open an account, sign in from a mobile device, browse rajabaccarat or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount request pathIndonesia access terms
atm4d atm4d Privacy Policy For Your Account
REQUEST HELP

Three Ways To Ask About Privacy

A privacy question should not get lost beside a cashier issue, so we keep the request path close to account support. Contact us through the available support channel shown in your account, include the email or phone linked to your account, and describe whether your request concerns access, correction, deletion or a wallet record. We may ask for an account step or receipt reference so we can locate the right record without asking you to send a full payment password.

Team online

Account request

Use the support contact connected to your atm4d account when you need a copy of stored account details or want to ask how your phone verification record is used. We may confirm ownership before releasing anything linked to your sign-in.

Wallet question

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate date through support rather than sharing your wallet PIN. We use the reference to check the account match and explain what we retained.

Correction request

If your phone number, email or account name needs correction, tell us which field is wrong and provide the updated value through the account support path. We verify the request before changing the record used for account access.

DATA HANDLING

Six Privacy Checks Behind Your Login

Privacy controls work best when they match the steps you take. We separate account details from wallet references where practical, restrict internal access to operational needs and record security events around sign-in…

Account details

We use your submitted phone number, email and account identifiers to create the correct sign-in path, confirm a request and send account-related replies. If a detail changes, contact us through support so we can verify the request before editing it.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record connected to your account. We use those fields to reconcile a receipt or investigate a wallet mismatch, not to request your wallet PIN.

Device signals

Your browser, device type, approximate network details and sign-in time may be recorded for session protection. These signals help us notice unusual access when you move from a phone lobby to another device.

Cookies

Cookies can keep a session open, remember selected settings and help us understand whether a page request completed. You can adjust cookie controls in your browser, although some account steps may then need to be repeated.

Retention

We keep account, verification and payment references for the period needed for account operations, security checks or legal duties. When a record is no longer needed, we remove it or use a form that no longer identifies you.

Your request

You can ask what eligible data we hold, request a correction, ask about deletion or raise a concern about handling. Send the request through account support; we may verify ownership before taking action or explaining limits.

Privacy Policy Questions For atm4d

These answers address the privacy searches we hear most often before an account is opened. They explain how the Privacy Policy applies to account creation, phone verification, local wallet records, cookies, device access and requests sent to support. If your situation is different, include the account step or payment reference when you contact us so we can examine the correct record.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use these records, how long we retain them and how to request action.

We use your phone number to create and protect the account path, complete the required verification step and respond to account requests. We may compare it with the account record when you ask for a correction or seek access to connected data.

Yes. The Privacy Policy covers payment references and status details received when you use DANA, OVO, GoPay or QRIS. We use those records to match a receipt with your account and investigate a wallet issue, while your wallet PIN should remain private.

Yes, you can request a correction for an eligible phone number, email address or account field through support. Tell us which value is wrong and provide the replacement. We verify account ownership first so a third party cannot alter your sign-in details.

Cookies may keep your session active, remember a selected setting and show whether an account page completed. Browser controls let you remove or restrict them. If cookies are restricted, you may need to sign in again or repeat a verification step.

We retain records only while they support account operations, security checks, dispute handling or legal duties. Retention can differ by record type, such as a sign-in event or payment reference. When the purpose ends, we remove or anonymise the record where practical.

Use the support contact available through your account and state whether you need access, correction, deletion or clarification. Include your account email or phone and a relevant receipt reference when applicable. Access eligibility depends on local law and ownership checks may apply.