Reference

How We Handle Your Data

This policy explains what we record when you open an account, sign in from Android, iPhone, or desktop, and use DANA, OVO, GoPay, or QRIS.

Account DataDevice LogsCookiesWallet Links

Browse The Lobby Read FAQ

What This Policy Covers Here

bajad4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect only the details needed to open, verify, and keep your account in order. That can include your name, contact number, login timestamps, device type, browser version, and the payment reference shown by DANA, OVO, GoPay, or QRIS. If a session starts from mobile and

1
finishes on desktop, we may link those events so the record stays accurate. We also keep cookie data and security checks so we can spot duplicate requests, mismatched logins, and failed access attempts. Access or eligibility depends on local law and is available only where local
2
law permits. If you ask us to correct or remove a field, we compare the request with the account history before we make any change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST CHANNELS

Where to Send Privacy Requests

The quickest route is live chat, where we can point you to the right request path for access, correction, or deletion of account details. If you prefer email, send the address linked to the account and the exact field you want changed, so we can match it against the same record. You can also open Settings > Privacy inside the dashboard and start the request without leaving the page.

Team online

Live Chat

Open live chat from the help button and tell us which data you want checked. We use it for identity questions, correction requests, and wallet matching tied to DANA, OVO, GoPay, or QRIS.

Email Desk

Send the email linked to your account, include the field you want changed, and attach any proof we ask for. Replies stay in one thread, so the record does not split across multiple cases.

Settings > Privacy

Inside Settings > Privacy, you can send a request without leaving the dashboard. That path keeps the request attached to the right session, device, and login history, which helps us answer it faster.

RECORD CARE

How We Protect Your Records

We keep the policy practical: use the minimum data needed, limit who can open the record, and remove stale entries on a schedule.

Data Use

We use your name, contact details, login history, and request history only to run the account, resolve disputes, and answer the changes you ask us to make. We avoid extra fields unless there is a clear reason.

Cookies

Cookies keep you signed in, remember language choices, and reduce repeat checks when you return on the same device. If you clear them, some session details reset and we may ask for another login.

Account Security

We record device type, browser, and last access time to spot a login that does not fit your usual pattern. That extra check can slow the session for a moment, but it protects the account record.

Retention

We keep contact and transaction records only as long as needed for support, dispute handling, or the legal period that applies. After that, we remove them or separate them from your profile on schedule.

Change Requests

If your name, phone number, or wallet reference changes, send the new detail through chat or email and we will compare it with the record already on file. Matching details keep the account history clean.

Who Sees It

Only the team that needs the record for support, verification, or security can open it. We do not pass it around inside the company without a reason, and we track each access against the request.

Questions About Your Data

If you want to know what we store, how long we keep it, or how to ask for a correction, this section points you to the same account record. We keep the process tied to the details you provide, the device you used, and the payment reference if DANA, OVO, GoPay, or QRIS appears in the history. That lets you see what we can verify before you send a request.

We keep only the details needed to open and protect the account, such as your name, contact number, login record, device type, and the wallet reference tied to the request. We do not ask for extra fields without a clear reason.

Cookies let us remember your session, language setting, and the last page you opened so you do not repeat every step. If you clear them, the login may ask for verification again.

Send the updated detail through chat or the account form, and we will compare it with the record already on file. If the new data matches the request history, we update the profile faster.

We keep records only for as long as they are needed for support, dispute handling, security, or the legal period that applies. After that, we remove them or separate them from your profile.

Yes. When DANA, OVO, GoPay, or QRIS appears in the account history, we store the reference and time stamp so the request can be matched to the right profile. We do not use that record for anything unrelated.

Access depends on local law and is available only where local law permits. If the rules in your area do not allow access, we will not invite you to continue the request or create a record.

Open live chat, send email, or use Settings > Privacy inside the dashboard. Each channel reaches the same privacy queue, so the team can trace your request without making you repeat the details.

How We Handle Your Data

Where to Send Privacy Requests

Live Chat

Email Desk

Settings > Privacy

How We Protect Your Records

Data Use

Cookies

Account Security

Retention

Change Requests

Who Sees It

Questions About Your Data

01 What data do you collect when I open an account?

02 Why do you use cookies on my device?

03 How do I correct my account details?

04 How long do you keep my records?

05 Do DANA, OVO, GoPay, and QRIS details stay in the file?

06 Can I use the service where local law does not allow it?

07 How do I contact you about a privacy request?

Related Pages