Reference

Open bening4d Privacy Policy Before Account Access

bening4d Privacy Policy tells you how we collect account details, wallet records, cookies and device signals before you open the full lobby.

DANA and QRIS recordsCookie choice pathPhone verification stepAccount update request
bening4d Open bening4d Privacy Policy Before Account Access
CONTACT ROUTES

Check Privacy Help From Your Account

Privacy help starts from your account area because we need to confirm that the request comes from you. Use the same login path you use for the lobby, then open the account help area near the cashier screen. If wallet status, cookie choices or phone verification create confusion, send the exact receipt code, device type and time shown on the page.

Team online

Privacy Request Form

Use Account > Profile > Privacy Request after phone verification. We use that logged-in path so your request is tied to the same account that holds wallet records and lobby activity.

Cashier Receipt Check

When a DANA, OVO, GoPay or QRIS status stalls, send the receipt code from the cashier page. We check only the payment fields needed to confirm your account record.

Access And Cookie Help

If the mobile browser keeps a cookie choice or login session you did not expect, message us from the account help area and include your device model and time.

DATA PRACTICE

Browse How We Keep Records

Clear privacy handling helps you decide whether to open an account with us. We separate profile data, wallet records, cookie choices and device checks so a cashier question does not expose more…

Account Data

We collect your registration details, phone verification result and login record to identify the account. We use those fields for access checks, privacy requests and account recovery when you contact us.

Payment Records

DANA, OVO, GoPay, QRIS, virtual account and bank transfer records are stored with reference codes. Bank context may include BCA, BRI, Mandiri or BNI when those rails appear.

Cookie Choices

Cookies help keep your login session, language setting and cashier state in place. You can clear browser cookies, then sign in again to reset the choice on that device.

Device Checks

We may record browser type, device signal and IP range when your account opens the lobby or cashier. These checks help us spot account access that does not fit your normal pattern.

Retention Period

We keep records for account operation, payment matching and request handling. Some wallet and bank transfer logs stay longer when needed for dispute checks or where local law permits.

Change Requests

You can ask us to correct profile details from the privacy request path. We may ask for phone verification again before editing data linked to wallet status or account access.

Discover Privacy Policy Answers

These answers focus only on privacy handling, account records and your choices with us. If you need help after reading, sign in first so we can connect your request to the correct profile, wallet record and device session without asking for unrelated data.

The Privacy Policy covers registration details, phone verification, login sessions, device signals, cookie choices and cashier records. We use this data to run your account, answer requests and match wallet activity.

We store wallet names, reference codes, time stamps and status results needed to match payments with your account. We do not use wallet records to ask for unrelated personal details.

Yes. Open Account > Profile > Privacy Request after phone verification and describe the field you want corrected. We check the request against account and wallet records before making changes.

Yes. Cookies may keep login state, cashier flow and language choice on your mobile browser. You can clear cookies from the browser settings, then sign in again to refresh the session.

We keep limited activity records so account access, wallet checks and dispute handling can be matched to the right session. The record may show category, title opened, time and device signal.

Sign in, open the account help area, then choose the privacy request path. Include your phone verification status, payment reference if relevant, and the data field you want us to check.

Yes. Access to some account records depends on local law, especially when a request involves payment logs, identity checks or account security. We explain the next step after verifying you.