Reference

maestro 4d Privacy Policy

The maestro 4d Privacy Policy shows what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the lobby and your…

Clear data purposesWallet activity explainedPhone verification records
maestro 4d maestro 4d Privacy Policy
HELP WITH YOUR DATA

Get Policy Help Beside Account Support

A clear contact route matters when your account record, wallet reference, or phone verification detail looks wrong. Our support channel can help you identify the account connected to a request, explain which data we hold, and direct a correction or access request to the right team. Include your account contact, the relevant date, and a short description so we can check the request without asking for your DANA, OVO, GoPay, or bank password. We use the same careful process whether you contact us from mobile or desktop.

Team online

Account data request

Ask our account support channel what personal data is linked to your maestro 4d account. We may request a phone confirmation before discussing records, so another person cannot obtain your login history or wallet references through a simple message.

Wallet reference check

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference appears incorrectly, send the date and receipt reference through support. We can check the payment record while keeping wallet credentials and bank login details outside the request.

Correction route

Tell us which account field, device record, or support message needs correction. We compare the request with your verified account details and explain the next step, including where local law limits deletion or changes to a required record.

HOW WE HANDLE RECORDS

Keep Control Of Account Details

We keep this Privacy Policy practical by tying each data use to a visible account action: phone verification before access, a wallet status check after a payment, or a device signal during…

Account security signals

We may use phone verification, sign-in time, browser type, and device signals to identify an account session. These details help us investigate an access problem or unusual sign-in without requesting your wallet password or storing your bank login.

Cookies and sessions

Browser cookies or similar storage can keep a session active, remember a selected setting, or show whether a policy page loaded correctly. Your browser can block or clear them, although changing those controls may require another sign-in.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account entry may contain a reference, amount status, and time. We use that record to match account activity and payment support, not to collect your wallet password or bank credentials.

Device access

When you open the lobby on a phone or desktop, we can receive browser and device details linked to the session. This supports account continuity and issue checking; it does not mean we can read unrelated files, contacts, or messages on your device.

Retention choices

We retain account, verification, payment, and support records only while they serve access, security, dispute handling, or legal duties. When a record is no longer needed, we remove it or separate it from direct account identification where appropriate.

Requesting policy changes

You can ask us to access, correct, or delete eligible personal data through account support. Include your verified contact and the precise record involved. We may confirm identity first and explain if local law requires us to keep part of the record.

Find Answers About Your Privacy

These Privacy Policy answers cover the account steps Indonesian customers ask about most: phone verification, mobile access, wallet references, cookies, retention, and requests for changes. We keep each answer tied to maestro 4d data handling rather than general lobby content. If your situation is not listed, contact account support with the account contact and date involved.

The Privacy Policy covers data collected when you open or access an account, verify your phone, use a mobile browser, contact support, or make a wallet payment. It explains purposes, cookies, security signals, retention, payment references, and how to request access or correction.

Phone verification helps connect an account request to the person seeking access and helps protect account records during support contact. We may use the verification result for access and security checks, but the Privacy Policy does not give us your DANA, OVO, GoPay, or bank password.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account routes. We use those details to match an account payment or investigate a receipt question, while wallet credentials remain with the payment provider.

When you sign in from a phone or desktop, we may receive browser type, device signals, session timing, and basic technical details. The Privacy Policy uses this data for session continuity, access checks, and fault finding; it does not provide access to unrelated files or messages.

Contact our account support channel with your verified account contact, the field or record you believe is wrong, and the relevant date. We may confirm your identity before changing anything, then explain the result or why a legal retention duty prevents removal.

We keep account, phone verification, payment, device, and support records for the time needed for access, security, payment questions, disputes, or legal duties. The Privacy Policy allows removal or separation from direct identification when a record no longer serves those purposes.

Yes, the Privacy Policy describes data handling for Indonesian account access, including sessions opened in Makassar or elsewhere in the country. Eligibility and access still depend on local law. If your location or account status creates a question, contact support before sending extra personal details.