Reference

Privacy Policy For Your boslot4d Account

boslot4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSupport access
boslot4d Privacy Policy For Your boslot4d Account
CONTACT YOUR WAY

Get Privacy Policy Help Beside Login

A clear contact route matters when you want to ask about personal data rather than a wallet status.

Account desk Ask about the Privacy Policy, stored account fields, phone verification, or a correction through…
Wallet questions For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, send the…
Security concern If a login alert or device change looks unfamiliar, contact support through the account…
DATA CONTROL

What We Do With Privacy Details

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

Account records

We use your registered phone number and account details to create access, complete phone verification, and respond to account questions. If a field is incorrect, ask us to correct it through support and we will explain the steps needed to confirm ownership.

Device signals

When you sign in from an Android phone, iPhone, or desktop browser, we may record device and session signals linked to security checks. These signals help us spot unusual access without giving support a reason to request your password.

Payment references

A DANA, OVO, GoPay, or QRIS reference helps us match a wallet event to your account. Bank transfer and virtual account records may also show a reference number. We use these details for status checks, not for collecting secret wallet credentials.

Cookie controls

Our site may use cookies or similar storage to keep a session active, remember a setting, and measure page function. You can manage browser storage through your device settings, although removing essential cookies may require another login.

Retention choices

We retain account, security, support, and payment records only while they serve account operation, dispute handling, security checks, or a legal need. Ask support which category applies to your record and whether deletion or anonymisation can be requested.

Change requests

To ask for access, correction, deletion, or a use explanation, contact the account support route with your registered phone number and request type. We may verify ownership first, then tell you what action is available under local requirements.

Privacy Policy Answers For Account Holders

These Privacy Policy answers address the questions we hear before account access, after a device change, and when a wallet reference needs clarification. Each response stays focused on personal data and the steps you can take. If your question concerns a record not listed here, contact us through the account support route during the stated service hours.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references. We use them for access control, security, wallet matching, and support. Availability and any data request process depend on local law.

We collect the details needed to create and protect your account, including your registered phone number and verification activity. We may also record login, device, support, and payment references. We do not ask you to send a password or one-time code for a privacy request.

Yes. Contact the account support route from the login or cashier path, state the field that needs correction, and provide your registered phone number. We may confirm ownership before changing the record, then explain the result and any further step.

We use DANA and QRIS references to match a payment event with the correct account and investigate a status question. The same approach applies to OVO, GoPay, bank transfer, and virtual account references. Send only the visible reference and date.

Send an access request through account support between 08:00 and 22:00 Jakarta time. Include your registered phone number and the categories you want clarified, such as login, device, cookie, support, or wallet records. We may verify ownership before responding.

We keep records while they support account operation, security checks, payment tracing, dispute handling, or a legal need. Retention differs by record type. Ask support about a specific category and we will explain whether deletion or anonymisation can be considered.

Contact support through the account path as soon as you notice an unfamiliar session or device. Do not send your password or one-time code. We may confirm account ownership, check the relevant security record, and explain the access step available to you.