Reference

Privacy Policy for brio4d Accounts

The brio4d Privacy Policy explains how we collect, use, secure and retain details connected with your account, device and wallet activity.

Account clarityWallet data careIndonesia access
brio4d Privacy Policy for brio4d Accounts
CONTACT THE TEAM

Privacy Help When Account Details Stall

A clear contact route helps you ask about the Privacy Policy without searching through unrelated account screens. Use the support path connected to your brio4d account when a phone check, wallet reference or device login needs clarification. Include the email or phone detail linked to the account, the relevant transaction reference and a short description of your request. We use those details to locate the right record, while you should avoid sending a password, one-time code or full payment credential.

Team online

Account support route

Ask about a Privacy Policy clause through the signed-in support path when you can access your account. We can connect your question to the relevant phone verification, login event or wallet reference without asking you to post sensitive credentials in an open message.

Payment receipt check

If a DANA, OVO, GoPay or QRIS receipt does not match your account history, send the reference shown by the wallet and the approximate transaction time. We use that narrow context to investigate status while keeping unrelated account activity outside the request.

Access assistance

When a device path or phone verification blocks access, contact us from the account route available to you and describe the screen you reached. We may ask for account identifiers, but we will not ask for your password or one-time security code.

DATA CONTROL ROOM

Inside brio4d Privacy Handling

We separate the information needed for account access from the records used to investigate a wallet or security event.

Data collection

We collect account details, phone verification results, device information, login events and support messages when those records are needed to provide account access or investigate an issue. Payment references from DANA, OVO, GoPay, QRIS and bank rails are used for matching rather than unrelated profiling.

Cookie choices

Cookies can keep a session working, remember a selected setting and help us understand whether an account page loaded correctly. You can adjust cookie controls in your browser, although blocking required cookies may affect login, wallet status display or the path back to the lobby.

Account security

Phone verification, login records and device signals help us check whether an access request fits your account history. Keep your password and one-time code private, sign out on shared devices, and contact support if a login alert or wallet action was not yours.

Record retention

We keep account, support and transaction references for the period needed to operate the service, resolve disputes, protect accounts or meet an applicable legal duty. When a record no longer serves one of those purposes, our handling follows the retention process described in this policy.

Correction requests

If your phone number, account name or contact detail is inaccurate, ask us to correct it through the account support route. Include the field that needs changing and enough account context to identify you; do not send passwords, one-time codes or complete wallet credentials.

Privacy contact

Questions about collection, cookies, retention or a data request can be sent through the support path linked to your account. Tell us which Privacy Policy section concerns you and whether you are asking for access, correction, deletion or an explanation of a record.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account decisions you are most likely to make before using brio4d from Indonesia. We explain what we collect, why wallet references appear in account records, how to request a change, and where to ask for help. If your situation involves access or eligibility, that outcome depends on local law, so check the policy and contact route that apply to your location.

It covers account details, phone verification, device signals, login events, cookies, support messages and payment references connected with your use of brio4d. It also explains retention, security measures and how to request access, correction or deletion where that request is available under applicable law.

DANA and QRIS references can appear when we match a deposit or account status request to your account. The reference helps us investigate a receipt or stalled status. We use it for the transaction purpose described in the policy, not as permission to collect unrelated wallet content.

Our Privacy Policy does not require you to send a wallet password or one-time code through support. When a DANA, OVO, GoPay or QRIS issue needs checking, provide the transaction reference and timing shown in your wallet. Keep authentication credentials private at all times.

Use the support path connected to your account and state that you are making a Privacy Policy data access request. Include your account contact detail and the records you want us to locate, such as login events, support messages or payment references. We may verify ownership first.

Yes, you can ask for an inaccurate account name, phone number or contact detail to be corrected through the account support route. Explain which field is wrong and provide identifying context. We may request phone verification before changing access-related details or wallet status records.

Send a request through the support route and identify the account records concerned. We will assess deletion against operational, security and legal needs described in the Privacy Policy. Some transaction or access records may need to remain for a relevant period before they can be removed.

Start with the support path available from your account and mention the exact Privacy Policy topic, such as cookies, device data, retention or wallet references. If you cannot reach the account because of phone verification, describe that access issue without including a password or one-time code.