Reference

Open with bri4d Privacy Policy

Our Privacy Policy shows how bri4d handles the details connected with your account, including phone verification, wallet references, device access and support messages.

Account detailsWallet referencesDevice recordsSupport requests
Explore Our Lobby Read FAQ
bri4d Open with bri4d Privacy Policy
CONTACT PATHS

Reach Support About Privacy Policy

A clear support route helps you ask what we hold about your account or report a suspected mistake. Start from the account help path when you are signed in; if login or wallet status stalls, include the relevant date, payment reference and device used. We use those details to locate the correct record without asking for a banking password. Requests about the Privacy Policy stay focused on access, correction, deletion, security or processing concerns.

Team online

Account help path

Use the signed-in account help path for a Privacy Policy request. Tell us whether you need account access, a data correction or clarification about phone verification, and we can connect the request with the correct account record.

Payment record check

For a DANA, OVO, GoPay or QRIS question, share the payment reference and approximate time rather than a wallet password. We can compare the reference with the account record and explain what payment data is retained.

Security concern

If you notice an unfamiliar login, device session or account change, contact support through the account path promptly. Include the device type and last known access so we can check security events while limiting unnecessary personal details.

HANDLING DETAILS

Explore How bri4d Handles Your Data

We keep the Privacy Policy practical by linking each data type to an account task you can recognise.

Account collection

When you open an account, we collect the details needed for the account path, including your phone number and verification result. We use these records to connect your sign-in with the correct account and to respond when access fails.

Wallet matching

A payment reference can show that a DANA, OVO, GoPay or QRIS transaction belongs to your account. We use that reference for matching and status checks; wallet credentials and banking passwords are not required for this purpose.

Device signals

Your browser, device type, login time and security events can be recorded when you move from login to the lobby. These signals help us spot unusual access and investigate whether a session came from your usual device.

Cookie controls

Cookies or similar browser storage may keep a session active, remember a setting or help us diagnose a page fault. You can manage browser storage through your device settings, although changing it may require another account login.

Retention approach

We retain account, payment and security records only for the period needed for the stated account task, dispute handling, security checks or a legal requirement. When a record is no longer needed, our handling follows the applicable deletion process.

Change requests

Ask through the account help path if a name, phone detail or other account record needs correction, or if you want to ask about deletion. We may request account verification first so another person cannot change your data.

Browse Privacy Policy Questions

These Privacy Policy answers cover the points you are most likely to check before opening a bri4d account from Indonesia. We explain the account step, payment references, device records, browser storage, retention and contact route in plain terms. Where a request depends on a local requirement, access depends on local law and we will apply the rule that governs your request.

The Privacy Policy covers data linked to your account, phone verification, wallet and payment references, device access, cookies, security events and support messages. It explains why we use each category, how we protect account access and how you can ask about correction or deletion.

Phone verification connects the account path with the correct person and helps us respond to access problems. We record the verification status rather than asking for a banking password. If eligibility or access is discussed, it depends on local law and the applicable requirement.

Yes. We may retain a DANA, OVO, GoPay or QRIS reference, plus related status details, so a payment can be matched to your account. Bank transfer and virtual account references may be handled in the same way, without collecting your banking password.

We may record device type, browser details, login time and security events connected with your session. These signals help us identify unusual access and diagnose a failed account path. They are handled for account security and technical support, not as a replacement for your account details.

Cookies or similar browser storage may keep your session connected, remember a setting or help us locate a technical fault. You can manage them in your browser or device settings. If you remove them, the account path may ask you to sign in again.

You can use the signed-in account help path to ask about a correction or deletion. We may verify your account before changing records. The result depends on local law, security needs, dispute handling and any retention period that still applies to the requested data.

Start through the account help path and state that your request concerns the Privacy Policy. Include the account phone detail, relevant payment reference or device context only when needed. For an unfamiliar login, report it promptly so we can check the related security events.

Related Pages

bri4d Indonesia Register bri4d Login Lucky Fortune Cat FAQ