Reference

Privacy Policy for your biolabet account

Your account, wallet and lobby activity are covered by this Privacy Policy before you open an account, including DANA, OVO, GoPay and QRIS payment records.

Account data useDANA and QRIS recordsCookie choicesSupport privacy
biolabet Privacy Policy for your biolabet account
CONTACT ROUTES

Three privacy contact paths

Privacy questions should reach the team that can actually check your account record. Use live chat for quick identity checks, email when you need a written reply, or the account form when you want to change saved details. We ask for the same login name and registered contact so we do not expose your data to the wrong person.

Team online

Live chat

Chat is open daily from 09:00 to 23:00 WIB for privacy questions tied to login access, device sessions or wallet records. We may ask you to confirm your registered phone or email before discussing account data.

Email request

Send policy requests to our support mailbox when you need a written record about data access, correction or deletion. Include your login name, last payment rail used and the change you want us to check.

Account form

Inside your profile, use Account > Help > Privacy Request to start a data change from the signed-in session. This path helps us match the request to the correct account without exposing wallet details.

DATA HANDLING

Six controls behind your account data

A privacy promise only matters if the account flow supports it. We separate wallet records from support chat, log security events, limit internal access and keep payment references…

Account creation

When you join, we collect the details needed to create and protect your profile: login name, password record, contact channel…

Payment records

DANA, OVO, GoPay, QRIS and bank transfer references are stored as transaction records, not as open wallet credentials.

Cookie choices

Cookies help keep you signed in, remember language settings and detect repeated failed logins.

Device sessions

Open Account > Security > Sessions to see recent device access and sign out of a browser you no longer…

Retention period

We keep account and payment data for the period needed to run the service, answer disputes, meet tax or legal…

Change requests

You can ask us to correct contact details, close an account or explain stored data through chat, email or the…

Answers about your privacy rights

These answers focus on the privacy steps you are most likely to need before or after opening an account. They explain what data we collect, how payment records are handled, how to ask for changes and what happens when local access rules affect a request.

We collect the details needed to create and secure your profile, such as login name, password record, contact channel, device signal and session time. Wallet actions may add DANA, OVO, GoPay, QRIS or bank transfer references.

No. We store transaction references, status records and matching details for account service, not your wallet login credentials. Those records help us confirm deposits, verify withdrawal requests and answer payment disputes linked to your account.

Contact us through live chat, email or Account > Help > Privacy Request. We will ask you to verify your login name and registered contact before sharing data or making corrections, so the request stays tied to you.

You can request deletion through the same privacy contact paths. We review the account for open balances, payment disputes, security flags and legal retention duties before confirming what can be removed or kept.

Device sessions and cookies help keep your account signed in, remember basic settings and detect unusual login patterns. You can clear browser cookies, but we may repeat security checks when your device looks new.

Only staff assigned to support, account safety or payment checks can access the relevant chat record. We limit internal access, keep request history for follow-up and avoid sharing privacy details outside the service team.

Yes. Access to features and some account actions depends on local law. If a request affects wallet records, identity checks or account closure, we may need extra verification before completing the privacy step.