Reference

Privacy Policy for buku erek erek

Our Privacy Policy explains how we handle the account details, wallet records and device signals connected with buku erek erek.

Account detailsWallet recordsMobile cookiesAccess requests

Explore Our Lobby Read FAQ

How wallet and account data is handled

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

We collect only the details needed to operate your account, confirm phone access, record wallet activity and respond when a payment receipt or status needs checking. That can include your contact details, login events, device type, browser settings, selected payment rail and transaction reference. DANA, OVO,

1
GoPay, QRIS, bank transfer and virtual account records may be retained so we can match a cashier event with your account and resolve a query. We use cookies for session continuity, security checks and page preferences; you can manage browser cookies, though some account functions may
2
then require another login. Our handling and any access eligibility depends on local law. You can ask us what we hold, request a correction, or ask about deletion through the support route below.

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

CONTACT ROUTES

Where to ask about your Privacy Policy

A clear contact path helps you act on this Privacy Policy without guessing which team handles your request.

DATA CONTROLS

What our Privacy Policy covers in practice

We apply this policy to the points where account access creates a record: phone verification, login, wallet selection, receipt matching and support contact.

Account details

We may hold your name or contact detail, phone verification result and account identifiers needed to recognise your access. We use these details to respond to account requests and match a wallet receipt to the correct account record.

Cookie choices

Cookies can keep a mobile browser connected after login, remember selected page settings and support security checks. If you clear them, the next visit may ask you to sign in again or repeat a device check.

Account security

We use login events, device signals and phone verification to identify unusual access. Keep your password and verification code private; our support route does not need either one to discuss a general policy request.

Record retention

We retain account and payment references for as long as needed for account operations, receipt matching, security checks or a lawful request. A DANA, QRIS or bank transfer reference may therefore remain after a page session ends.

Requesting a change

You can ask us to correct a phone detail, contact field or other stored account record. Include the old and new value where relevant, and we may first confirm account ownership before applying the change.

Who to contact

Use the account support route for questions about this Privacy Policy, stored details, cookies or wallet records. For a payment query, add the rail name and receipt reference; for a device query, add your browser type.

Privacy Policy answers for your account

These Privacy Policy answers focus on the searches we hear before account access: what we collect, why wallet records appear, how cookies work and how to request a change. If your question concerns a particular DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, include that detail when contacting us so we can locate the relevant record.

It covers account details, phone verification, login and device events, cookies, wallet and payment references, support requests, retention and requests to correct or delete stored data. Access handling depends on local law and applies where local law permits.

We use your phone detail to support the account access step and confirm that a request comes from the account holder. It can also help us locate a DANA, OVO, GoPay or QRIS record when you provide a matching receipt reference.

Yes. The Privacy Policy covers payment references linked to your account, including DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match cashier events and answer status or receipt questions.

Contact our account support route with your registered phone detail, account identifier and preferred reply route. We may confirm ownership before responding, then explain which stored details can be supplied and how the copy will be sent.

Yes. Send the account field that needs correction and the accurate replacement value. For a phone or contact change, we may repeat the phone verification step or ask for another ownership check before updating the stored record.

Cookies can keep your mobile browser connected, preserve page preferences and support security checks. You can clear or restrict them in your browser settings, but doing so may end a session or require another login and device check.

We keep records for the period needed for account operation, receipt matching, security review or a lawful request. The period can differ by record type, so contact us with the account detail or payment reference for a specific retention question.

Privacy Policy for buku erek erek

Where to ask about your Privacy Policy

What our Privacy Policy covers in practice

Account details

Cookie choices

Account security

Record retention

Requesting a change

Who to contact

Privacy Policy answers for your account

01 What does the buku erek erek Privacy Policy cover?

02 Why does buku erek erek need my phone detail?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy of my account data?

05 Can I ask buku erek erek to correct my details?

06 How do cookies affect Privacy Policy choices?

07 How long are wallet and login records kept?

Related Pages