Reference

cepat33 Privacy Policy: Your Data Path

The cepat33 Privacy Policy explains what we collect when you open an account, verify your phone, sign in on mobile or desktop, and use DANA, OVO, GoPay or…

Phone verificationWallet recordsCookie choicesAccount requests
cepat33 cepat33 Privacy Policy: Your Data Path
HELP PATH

Open the Privacy Support Route

A clear support route helps you ask about personal data without sending sensitive details through an open chat. Start from the support link beside the account or cashier area, include your registered phone detail and state whether your question concerns login records, a wallet receipt or cookies. For account access, we may request a matching verification step before discussing the record.

Team online

Account data request

Use the support path beside your account area to ask what personal details are connected to your cepat33 profile. We first match the request to your registered phone detail.

Wallet record query

For DANA, OVO, GoPay or QRIS records, include the transaction reference and date rather than sharing a wallet password. We use those details to locate the correct payment entry.

Cookie question

If a browser keeps an old session or cookie choice, tell us the device path you used, such as Android browser or desktop browser, so we can direct the request.

CONTROL CHECKS

Switch On Account Privacy Controls

We keep the Privacy Policy practical by linking each data purpose to an account action you recognise: phone verification, wallet status, cookie selection or a request to change details.

Data handling

We use submitted account details to create your profile, confirm phone ownership and connect account activity with the correct sign-in. We do not need your wallet password to locate a transaction reference.

Cookie settings

Cookies can preserve a session and remember selected settings on your browser. You can clear or restrict them through browser controls, although a new sign-in may then be required.

Account security

Phone verification and account checks help us distinguish your request from an unknown sign-in. Never place a password, one-time code or wallet PIN inside a privacy request.

Record retention

We retain account, access and payment references only for the operational, dispute-handling or legal purpose connected to them. A retention question can be raised through the support route.

Change request

If your phone detail or account record needs correction, send the requested change from the support path. We may ask for verification before editing information tied to your profile.

Access conditions

Requests and account access are handled where local law permits. We may explain a restriction when identity, security, another person’s data or a legal requirement affects the request.

Browse Privacy Policy Questions

These Privacy Policy answers address the searches you may make before opening an account: what we collect, how wallet references are used, how cookies behave and how to request a change. We keep the route tied to your actual account step, from phone verification through a DANA or QRIS receipt check.

It covers account details, phone verification, device and browser signals, cookie choices, access records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone detail to create and verify the account, distinguish your request from an unknown sign-in and connect a privacy request with the correct profile before discussing its records.

Yes. We may store a payment reference, amount status and date needed to match DANA or QRIS activity to your account. Do not send a wallet PIN or password with a request.

Cookies can keep a session active and remember browser settings. You can clear or restrict them in your browser. After clearing them, cepat33 may ask you to sign in again.

Use the support link near your account or cashier area, describe the exact correction and include your registered phone detail. We may complete a verification step before changing the record.

Retention depends on the purpose: account access, payment matching, dispute handling, security or a legal requirement. Ask through support for the category and reason connected with a particular record.

We handle a data request where local law permits. Send it through the account support path; we may limit or delay access when identity, security, another person’s data or law requires it.