Reference

basis33 Privacy Policy For Your Account

basis33 Privacy Policy explains how we handle the details you provide when opening an account, checking wallet status or entering the lobby from your phone.

Account clarityWallet referencesPhone accessPolicy requests
basis33 basis33 Privacy Policy For Your Account
HELP WITH REQUESTS

Three Ways To Ask About Privacy

A clear contact path matters when you want to check or change personal data. Start from the support route inside your basis33 account and describe the request in plain English, including the phone number linked to the account. If your question concerns a DANA or QRIS receipt, include the reference rather than sending a full wallet password or security code. We may ask for account details to confirm that the request comes from you. For access questions, eligibility depends on local law.

Team online

Account support chat

Use the support chat shown after you sign in when you want to ask which account details we hold or why a verification record appears. We will use the account path to match your request and may ask you to confirm the phone number attached to your basis33 profile.

Payment record check

For a wallet-data question, send the payment rail and reference visible on your receipt, such as QRIS, DANA, OVO or GoPay. Do not send a wallet PIN, one-time code or full banking password. We use the reference to locate the relevant account record.

Correction request

If your name or phone detail needs changing, tell us which field is wrong and what it should say. We may request a phone verification step before making an account change, helping us avoid altering another person’s basis33 record by mistake.

DATA HANDLING

How We Manage Account Privacy

Privacy work is part of the account flow, not a separate promise. We limit access to account records according to the task being handled, protect sign-in and verification…

Account details

We collect details you submit to open and maintain an account, such as your name and phone number.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount and status record connected to your account.

Cookies and sessions

Cookies can keep a required preference or session state while you move from login to the lobby on a phone.

Security controls

We protect account access by checking sign-in activity and asking for verification when an account change needs confirmation.

Retention period

We keep account, support and payment-matching records only for the period needed to provide the requested service, resolve disputes or…

Your request route

You can ask about access, correction, deletion or the use of your personal data through account support.

Privacy Policy Answers For basis33

These Privacy Policy answers address the questions you may have before opening an account or while using the service from Indonesia. We explain the records connected with login, phone verification, local wallet references, cookies and support requests. If your situation needs a decision about access, deletion or retention, contact us through the account support path with enough detail for us to locate the correct record. Availability depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. We use those records for account access, receipt matching, security, support and required legal duties. The policy applies to basis33 account activity and related service conversations.

We may collect the name, phone number and verification details you submit, along with session, device and browser records created during access. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may also be recorded to match a payment with your account.

Phone verification helps us confirm that the person requesting account access or a profile change controls the linked phone number. It also helps us investigate an unfamiliar login or wallet status. Keep each code private; support does not need your wallet PIN or banking password.

You can ask for details about the personal data connected with your account through the signed-in support route. Include your linked phone number and state that you want an access request. We may confirm your identity first, and the response depends on local law and required records.

Tell support which field is incorrect and provide the replacement detail through the account path. We may ask you to complete phone verification before changing the profile. This check protects your account from an unauthorised edit and helps us keep payment matching accurate.

We retain records for as long as needed for account services, payment receipt checks, support, dispute handling and legal duties. The period can differ by record type and applicable rules. You can ask support about a specific record, although deletion may be limited by local law.

You may submit a deletion request through account support and explain which data you want removed. We confirm identity before assessing it. Some records may need to remain for legal, security or dispute reasons, so the outcome depends on local law and the record involved.