Reference

spbu77 Privacy Policy: Your Data Path

spbu77 Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Account dataCookie choicesWallet recordsSecurity requests

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

spbu77 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide when creating an account, completing phone verification and contacting support about a login or wallet status. We may also receive technical details from the browser or mobile device used to reach the lobby, such as session activity, language

1
settings and basic security signals. Payment records are linked to the transaction route you choose, including DANA, OVO, GoPay, QRIS, bank transfer or virtual account, so we can match a receipt with the correct account. We use these records to provide account access, check payment status,
2
protect sessions and meet applicable legal requests. Access depends on local law, and any regional or eligibility decision is handled on that basis. We do not ask you to send payment passwords through an ordinary support request. For a policy correction, contact us through the account
3
support path and include only the details needed to identify your request.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where Privacy Questions Go

A clear contact route helps when you want to ask about a record, correct an account detail or understand a wallet entry. Start from your account support path rather than sending sensitive credentials in a message. We can then connect your request with the relevant login, phone verification or payment receipt while keeping the Privacy Policy request focused.

Team online

Account requests

Use the account support path to ask what personal details are connected with your login or to request a correction after phone verification.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date only; we use those details to trace payment status.

Security concerns

If a session or device seems unfamiliar, report it through support and change your account password before sharing any further account detail.

HANDLING STANDARDS

How We Apply This Privacy Policy

We apply this policy at the points where your account creates a record: registration, phone verification, login, wallet status checks and support contact.

Account data

We use your account and phone-verification details to match you with the correct login, protect account access and respond to requests about your stored data.

Cookies and sessions

Cookies and session signals help keep the lobby connected to your login, remember essential settings and identify unusual browser behaviour during account access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with your account and investigate a status mismatch.

Account security

Phone verification, login checks and device signals work together to reduce mistaken access; we never need your wallet PIN or account password in support messages.

Retention period

We retain account, transaction and support records only for the period needed for account operations, security checks, dispute handling and applicable legal duties.

Change requests

Ask us to correct or explain a record through the account support path, using the smallest useful reference so we can verify the request safely.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions that arise before account access or when a wallet record needs checking. We keep each answer tied to a practical step, whether you are using a mobile browser in Indonesia, checking QRIS activity or asking how to update your account details.

It explains how we handle account details, phone verification, browser sessions, cookies, payment references and support requests connected with your access, including activity linked to DANA, OVO, GoPay and QRIS.

Phone verification helps us match you with the correct account and reduce mistaken access. It may also help us check a request to change account details or investigate an unfamiliar login.

Yes. The policy covers the browser and device session used to reach the account from mobile or desktop. Essential cookies and security signals help keep your login connected to the right session.

We use the payment reference, amount and date needed to match a DANA or QRIS receipt with your account and check its status. Do not send a wallet PIN or password with the request.

You can ask for a correction through the account support path. Include the relevant account reference and explain the change; we may use phone verification before updating or discussing the record.

We retain records for the period needed to operate your account, resolve payment or security questions and meet applicable legal duties. When a record is no longer needed, our handling follows the policy.

Access depends on local law. The Privacy Policy does not change regional eligibility requirements, and you should check the rules that apply to your location before opening or using an account.

spbu77 Privacy Policy: Your Data Path

Where Privacy Questions Go

Account requests

Wallet records

Security concerns

How We Apply This Privacy Policy

Account data

Cookies and sessions

Payment matching

Account security

Retention period

Change requests

Privacy Policy Answers for Your Account

01 What does the spbu77 Privacy Policy protect?

02 Why does spbu77 need phone verification?

03 Does the Privacy Policy cover mobile browser sessions?

04 How are DANA and QRIS records handled?

05 Can I request a correction to my account data?

06 How long does spbu77 keep account records?

07 Where local law permits, can I access the account?

Related Pages