Reference

Privacy Policy For Your buslot Account

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

Account dataCookie choicesWallet recordsPrivacy requests
buslot Privacy Policy For Your buslot Account
CONTACT ROUTES

Get Privacy Help Near Account Access

A clear contact path matters when you want to ask about personal data rather than a lobby question.

Account privacy request Use the support contact displayed in your account area to ask what personal details we hold. Include your account identifier and the request type, such as access, correction or deletion, so we can check ownership before replying.
Wallet record question If a DANA, OVO, GoPay or QRIS receipt appears against the wrong account, send the transaction reference through our support path. We use the reference to inspect payment status without asking you to share a wallet PIN.
Login and device concern Tell us if a phone, browser or sign-in record looks unfamiliar. We may ask you to complete phone verification before discussing account details, helping us avoid releasing private information to someone else.
DATA PRACTICES

How We Handle Your Privacy Choices

Privacy controls work best when they are tied to real account actions. We separate necessary account records from optional cookie preferences, use verification before discussing private details, and assess retention as the…

Account details

When you open an account, we may collect contact details and phone-verification results needed to establish account access. We use these details to identify your account, respond to privacy requests and reduce the risk of an unauthorised change.

Device signals

A phone or desktop browser can send technical signals such as browser type, session time and security events. We use them to recognise a disrupted sign-in and investigate unusual access, not to request your device password.

Cookies

Cookies can keep a session working and help us remember choices made on the site. You can adjust cookie controls through the browser path available on your device, although disabling necessary cookies may interrupt account access.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record may be connected to your account for status matching. We use payment references and receipts for reconciliation, while wallet PINs remain yours and should not be sent to us.

Account protection

Phone verification helps us check identity before we discuss account data or a requested change. If your sign-in path behaves differently on mobile and desktop, contact support through the account route instead of sharing a password or verification code.

Retention and changes

We retain records only for the period needed for account operation, security checks, payment questions, legal duties or disputes. To ask for correction, deletion or a copy, contact us through the displayed support route and complete any ownership check we request.

Privacy Policy Answers For buslot

These Privacy Policy answers focus on the questions that commonly arise before account creation or after a wallet transaction. They explain the practical path for data access, correction, cookies, device records and contact requests, while local availability depends on local law.

The buslot Privacy Policy covers account and contact details, phone verification, device and browser signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, privacy requests and account-security checks.

We may collect the contact details needed for your account path, phone-verification results, sign-in events and technical device signals. If you use a wallet or bank rail, we may also receive a payment reference or receipt status so the transaction can be matched to your account.

Use the support contact shown in your account area and state whether you want access to stored data or a correction. Include your account identifier, but never include your password, wallet PIN or one-time code. We may verify ownership before releasing or changing private details.

Yes. The Privacy Policy explains that necessary cookies can maintain a sign-in session and remember site choices on a mobile browser or desktop. Your browser controls can limit optional cookies, but blocking necessary cookies may interrupt the path from account access to the lobby.

We use payment references, receipts and status details to match a DANA, OVO, GoPay or QRIS transaction with the correct account and answer a payment query. We do not need your wallet PIN, so do not send it through support or attach it to a request.

We keep account information for the period needed to operate access, protect accounts, resolve payment questions, meet applicable legal duties or handle disputes. The exact period can depend on the record type and the circumstances, and you can ask support to explain retention for your request.

You can send a deletion request through the support route displayed after account access. We will check that you control the account and assess whether any record must remain for security, payment reconciliation, legal duties or a dispute. Availability and eligibility depends on local law.