b2slot Platform Privacy Notice

DANA deposit and withdrawal

When you deposit via DANA on b2slot, we record your phone number registered with your DANA account, the transaction timestamp, the deposit amount, and DANA's transaction reference code. Our system encrypts your phone number and stores it separately from your plaintext account data. We do not collect or store your DANA password, PIN, or backup codes. DANA processes authentication on its own secure servers; we receive only a confirmation that your transaction succeeded. Your b2slot account data and DANA account data remain separate—we do not cross-link your DANA data with other account holders. If you withdraw via DANA, we submit your phone number to our payment partner, who routes the payout to your DANA account. Your DANA transaction history shows our payout separately from your b2slot records. We retain your DANA phone number and transaction records for a minimum of five years to support regulatory compliance and dispute resolution. If you change your phone number, update your b2slot account settings so future DANA transactions route to your new number. We do not share your DANA phone number with third parties except to our payment-processing partner under contractual confidentiality obligations. If you request deletion of your b2slot account, we remove your DANA phone number from active systems but retain encrypted copies in our audit logs for five years. Your DANA account remains entirely separate and is not affected by b2slot account closure.

OVO and GoPay usage

OVO and GoPay deposits on b2slot follow similar data flows to DANA: we record your registered phone number, the transaction timestamp, amount, and e-wallet provider's reference code. We do not collect your OVO or GoPay app password, backup codes, or biometric data. Both OVO and GoPay require you to complete identity verification within their apps before linking to b2slot—we rely on their KYC processes and do not duplicate verification on our side. Your b2slot account and OVO/GoPay account remain separate identities; we link them only for payment routing. Our encryption protocols ensure your OVO or GoPay phone number is isolated from plaintext account data. If you update your OVO or GoPay PIN or security settings, those changes occur entirely within the OVO or GoPay app and do not affect your b2slot account directly. We retain your OVO and GoPay phone numbers in encrypted storage for five years to support withdrawal processing and compliance reporting. If you close your OVO or GoPay account, notify our support team so we can update your b2slot payment records and prevent failed withdrawal attempts. We do not store historical OVO or GoPay transactions beyond the reference codes necessary for account reconciliation. If you request data deletion from b2slot, your OVO and GoPay accounts remain active and accessible through their respective apps—we only remove the link from our systems.

BCA, Mandiri, BRI, BNI virtual account

When you deposit via bank virtual account (BCA, Mandiri, BRI, or BNI) on b2slot, we generate a unique virtual-account code for your transaction and record your bank account number in encrypted form. We do not collect your online banking password, PINs, or security tokens. You initiate the transfer from your personal bank app or portal using your own credentials—b2slot never accesses your bank login. Our virtual-account system receives only the settlement confirmation from the bank (amount received, timestamp, your VA code, bank reference number). We encrypt your bank account number and store it separately from your plaintext b2slot identity data. When you withdraw, we initiate a transfer back to the same bank account number you used for your original deposit—we do not allow withdrawal redirection to alternative accounts. We retain your encrypted bank account details for five years to support transaction verification and regulatory audits. If you close your bank account or change banks, notify our support team and provide your new bank details so future withdrawals route correctly. We do not share your bank account information with third parties except to our settlement partner under contractual confidentiality obligations. If you request b2slot account deletion, your bank account number remains encrypted in our audit logs for five years but is removed from active systems. Your bank account itself remains entirely separate and is unaffected by b2slot closure.

Fees, limits and verification

We collect minimal additional data during fee and limit processing. When we calculate your account tier and deposit/withdrawal ceilings, we assess your transaction history, account age, and cumulative deposit amounts—these calculations remain internal to b2slot and do not require new data collection. However, we do collect and store the reason codes if we reject a deposit (insufficient balance in your e-wallet, exceeded daily limit with your bank, account flagged by payment partner, etc.). We retain these rejection codes for ninety days to help you troubleshoot failed transactions. We do not collect fee data beyond what your bank or e-wallet provider reports to us in settlement confirmations. During your first deposit, our verification process triggers KYC data collection: your government ID scan (we record the document type, issue date, expiry date, document number, and photograph), and your banking screenshot (we verify only that the document shows your name and account details—we do not extract full financial statements). We encrypt and store these KYC documents separately from your primary account data. We retain your KYC documents for seven years to comply with anti-money-laundering regulations. If your KYC documents expire or you update your identity, re-submit updated copies via your account settings. We do not share your KYC documents with external parties except to regulatory authorities if legally required.

Resolving a stalled transaction

When you report a stalled deposit or withdrawal, we collect additional data to investigate: your specific payment method used, the exact amount, the timestamp you initiated the transaction, your bank or e-wallet transaction reference number (if available), and any error messages you received. We do not request your password, PIN, or backup codes—never share these with our support team. For stalled deposits, we cross-reference your b2slot deposit record against our payment partner's logs to locate the transaction. This investigation may require us to store temporary debugging data (IP addresses at time of transaction attempt, device fingerprints, payment-gateway logs) in a secure investigation folder. Once resolved, we retain this debugging data for thirty days in case you need follow-up support, then delete it. For stalled withdrawals, we obtain settlement-partner logs showing whether your payout was submitted, accepted, or rejected. We do not share these logs directly with you but summarize the findings in our support response. If a withdrawal is reversed and returned to your b2slot balance, we retain the reversal reason code and bank reference number indefinitely to document what occurred. You have the right to request copies of all investigation records related to your stalled transaction within ninety days of closure—we provide these in response to your written request within ten business days.