Reference

Privacy Policy For Your basic55 Account

Our Privacy Policy explains how basic55 handles the details you provide when opening an account, checking wallet status or browsing from Indonesia.

Clear data choicesWallet record contextPhone access checksPolicy contact path
basic55 Privacy Policy For Your basic55 Account
CONTACT ROUTES

Get Privacy Policy Help Near Your Account

A clear contact route matters when you want to ask what data we hold or why an account step needs a check.

Data access request Ask us which account details, sign-in records or payment references are connected with your…
Correction request If your contact detail or account record is incorrect, send the requested change through…
Payment data question When a wallet or bank transfer status needs explanation, tell us the date, method…
DATA CARE

What We Do With Account Data

Privacy Policy choices are easier to use when each data purpose has a practical reason. We use account details to provide access, device signals to protect sign-in, and payment references to match…

Account details

We collect details needed for account access and phone verification, such as your contact number and account identifiers. These details help us match a request to the right profile and prevent another person from changing your account record.

Device signals

A phone or desktop browser can send session and device signals that help us recognise unusual sign-in behaviour. We use these signals for account security and access checks, not as a reason to request your private wallet password.

Cookie controls

Cookies may keep your session active, remember a page setting or help display the correct account state after you move from login to the lobby. You can manage browser cookie controls, although restricting them may affect sign-in continuity.

Wallet references

DANA, OVO, GoPay and QRIS references can appear when we match a payment action with an account status. We use the reference for checking that event and support handling, rather than treating it as access to your wider wallet history.

Retention requests

We keep records for as long as needed for the stated account, security or payment purpose, subject to applicable legal duties. You can ask why a record remains, request a correction or ask about removal through our account contact route.

Account protection

We may confirm your phone verification or ask for limited account context before discussing personal data. This step helps us avoid revealing account details to the wrong person when you contact us about access, cookies or a payment reference.

Privacy Policy Answers For basic55

These Privacy Policy answers address the account questions you are most likely to have before opening or using basic55 from Indonesia. Each answer points to a practical step, from checking a wallet reference to asking for a copy of account data. If your situation needs a decision based on local rules, our contact route can direct the request to the appropriate account team.

The basic55 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask for access, correction or removal where local law permits.

Use the account support path beside the cashier area and ask for a data access request. Include the phone number linked to your account and describe the records you want, such as sign-in history or a QRIS reference. We may verify your identity first.

Yes. The Privacy Policy covers references created when DANA, OVO, GoPay or QRIS activity is matched with your account status. We use those references to check a specific account event and support a payment question, not to access unrelated wallet details.

Cookies can keep your login session connected, remember a page setting and help show the right account state when you move between login and the lobby. You can adjust cookie controls in your mobile browser, but restricting them may interrupt account access.

You can ask us to correct an inaccurate contact detail or account record through the account support route. Tell us what is wrong and what it should say. We may compare your request with the phone verification step before making the change.

We retain each record for the period needed for its account, security or payment purpose, subject to applicable legal duties. The exact period can differ by record type. Ask through account support if you want the reason a particular record is still retained.

You can submit a removal request through the account contact path and explain which data you want considered. We assess the request under the Privacy Policy and applicable rules; some records may need to remain where local law requires retention or account security checks.