Reference

secepatoto Privacy Policy for Your Account

Your account data stays tied to the account step, phone check and wallet records you create, so you can see what we collect before opening the lobby.

Account data clarityWallet record controlsLocal-law access
secepatoto secepatoto Privacy Policy for Your Account
SUPPORT DATA PATH

Where To Ask About Account Data

A clear support path helps when a login, phone check or wallet reference needs attention.

Account access If your phone verification or login record looks wrong, contact us through the account support path and describe the device, date and step that stopped you.
Wallet receipt For DANA, OVO, GoPay or QRIS questions, share the payment reference and status shown on your receipt. Keep passwords, PINs and full wallet credentials private.
Privacy request Ask us to access, correct or clarify personal records through the same support route. We may confirm account ownership before discussing data linked to your profile.
ACCOUNT RECORD PRACTICE

How We Protect Login And Wallet Records

Privacy work follows the account actions you can recognise: phone verification, login, wallet selection and support contact.

Data handling

We connect account details with the specific action that needs them, such as phone verification or a DANA status check, instead of treating every record as one unrestricted profile.

Cookies

Our mobile and desktop pages may use cookies or similar signals to keep your login session available and remember the route from account access to the lobby.

Account security

Phone verification and account checks help us distinguish an authorised request from an unfamiliar device. Never send your password, wallet PIN or one-time security code.

Retention

We keep account, payment-reference and support records while they serve account operation, security or legal needs. After that period, records are removed or separated where appropriate.

Correction requests

If your name, phone detail or account record needs correction, contact support from the account route and identify the exact field. We verify ownership before making a change.

Data questions

You can ask who handles a particular record, why it is retained or how it relates to QRIS, bank transfer or virtual account activity through our privacy contact path.

Privacy Policy Answers For DANA And Login

These Privacy Policy answers cover the practical questions we expect before an account is opened: which records we use, how wallet references are handled, what happens on a mobile device and how you can request access or changes. The same rules apply to account activity in Indonesia where local law permits.

It covers account details, phone verification, login activity, device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

No. We ask you to keep wallet PINs, passwords and one-time codes private. We may retain a payment reference or status needed to match an account request with DANA or OVO activity.

Phone verification helps connect an account request to the person controlling that account and supports security checks when access comes from a new device or a sensitive account-change request.

Yes. Use the support contact shown in your account area, ask for a data access request and identify the account. We may confirm ownership before sharing records linked to you.

Send the correction request through our account support path, name the incorrect field and provide the updated detail. We check ownership first, then explain whether the change can be applied.

Cookies or similar device signals may keep your session connected while you move from login to the lobby. Browser controls can limit them, but some account functions may then need another check.

Yes. Certain access, retention and account-data requests depend on local law. We apply the Privacy Policy where local law permits and explain any limit affecting your request.