Reference

Open the bowototo Privacy Policy

Our bowototo Privacy Policy shows how we handle your account details, phone verification, device signals and wallet records before you enter the lobby.

Account dataWallet recordsCookie choicesContact steps
bowototo Open the bowototo Privacy Policy
CONTACT ROUTES

Reach support about your privacy

A clear contact route helps when you need a copy, correction or explanation about your data. Start with our support chat and include the account phone number, the email linked to your profile, and the subject of your request; never send a wallet PIN or full authentication code. We may ask for account details to confirm that the request comes from you.

Team online

Privacy request

Use support chat to ask what account, device or payment records we hold, and tell us whether you want a correction, access copy or deletion assessment.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date. We use those details to locate status records without requesting your wallet password.

Account verification

Phone verification may be needed before we discuss personal data. Keep your sign-in details private while we match the request with the correct bowototo account.

HANDLING DETAILS

Explore our data handling steps

We keep this policy practical by linking each data category to an account action: sign-in, phone verification, wallet status, support or security review.

Data we receive

We may receive your name, contact details, phone verification result, sign-in history, device or browser signals, support messages and payment references connected with your account.

Cookies in use

Cookies can keep a session active, remember selected settings and provide basic page performance signals. You can manage browser cookie controls, though some account steps may then work differently.

Account security

Phone verification and sign-in checks help us connect an account request with the right person. We do not ask you to place a wallet PIN or full code in support chat.

Retention period

We retain relevant account, support and transaction records only for operational support, security checks, dispute handling or legal duties, then assess whether continued storage is needed.

Request changes

You can ask us to access, correct or assess deletion of eligible personal data through support chat. Include your account phone number and a clear description of the requested change.

Data questions

Questions about this Privacy Policy belong with our support team. We may verify your identity first, especially when a request concerns wallet records or account recovery.

Check Privacy Policy answers first

These questions cover the account, device and payment details most often connected with a Privacy Policy request. If your situation is not listed, contact support chat with the account phone number and transaction reference where relevant.

It covers data linked to your account, phone verification, browser or device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

Phone verification helps connect account access and privacy requests with the correct person. It can also help us investigate a sign-in concern without asking you to share a wallet PIN.

Yes. The Privacy Policy explains that DANA and QRIS records may include a reference, date, amount and status so we can match a cashier event with your account.

Contact support chat with your account phone number and request an access copy. We may ask for an identity check before discussing personal details or releasing account-related records.

Yes. Tell support chat which detail is inaccurate and provide the corrected value where appropriate. We assess the request against account security, operational needs and applicable legal duties.

We keep relevant records for account support, security checks, disputes or legal duties while they are needed. We then assess whether continued retention has a clear operational or legal reason.

Yes. It covers data handled when you sign in through a mobile or desktop browser, including session cookies, device signals and account actions taken before entering the lobby.