Reference

oyo999 Privacy Policy for Your Account

oyo999 Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can ask for access or changes.

Account dataWallet recordsCookie choicesAccess requests
oyo999 oyo999 Privacy Policy for Your Account
CONTACT DATA CARE

Where to Ask About Privacy

A clear contact route helps you resolve a privacy question without repeating your account story. Start from the support path linked to your account and include the email or phone detail used during sign-in, plus the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record, not to request an unnecessary password. If you cannot access your account, describe the device path and the last completed step so we can check identity safely.

Team online

Account privacy request

Ask for a copy, correction, or deletion of personal data through the account support route. Include your registered contact detail and the specific Privacy Policy request so we can identify the right record without asking for your password.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, send the payment date, amount reference shown to you, and wallet name. We use the receipt trail to locate a status record while limiting the personal details included in the request.

Access problem

If phone verification or sign-in stops on your mobile browser, tell us the device type and the step where it stopped. We may ask for an identity check before discussing account data, which helps keep the record with its owner.

HANDLING DETAILS

What Privacy Controls Cover at oyo999

Privacy protection is part of each account action, from the first phone check to a wallet status enquiry.

Collected account details

We may hold your name or chosen account label, contact detail, phone verification result, sign-in history and messages sent to support. These records let us connect your request to the correct account and avoid discussing private details with the wrong person.

Cookies and devices

Cookies can remember a session choice, while device and browser signals can help identify an unusual login. You can manage browser cookie settings, but switching them off may require another sign-in or remove saved preferences from the account path.

Wallet and payment records

A DANA, OVO, GoPay or QRIS reference may be stored with the account action it relates to. Bank transfer and virtual account records can also support receipt matching, status checks and resolution of an interrupted payment enquiry.

Account protection

Phone verification, sign-in checks and limited account details help us protect your profile. We will not ask you to share a password in a privacy request. If a request involves sensitive records, we may first confirm that you control the account.

Retention decisions

We keep records only for as long as they serve account operation, security, dispute handling or a legal requirement. When a retention period ends, data may be deleted or separated from direct account identifiers, subject to applicable law.

Changing your details

You can ask us to correct an outdated contact detail or explain why a record remains stored. Send the request through account support and name the field or record concerned. We may retain a limited audit entry showing that the change was handled.

Privacy Policy Answers for oyo999

These Privacy Policy answers focus on the questions you may have before opening an account or sending a wallet enquiry. They explain the practical route for data access, correction, deletion, cookies and account checks. If your situation is not covered, contact support with the smallest useful set of details, such as your registered contact point and a payment reference.

The oyo999 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use those records for access, account protection, receipt matching and legal duties, and how you can ask about information connected with you.

Use the account support route and ask for a data access request. Include the contact detail used during registration and describe the records you want, such as sign-in history or DANA receipt references. We may confirm account control before sharing any personal data.

Yes, you can ask us to correct an outdated contact detail, account label or other inaccurate record. Send the request through support, identify the field clearly, and explain the correct value. We may keep a limited change record where account security or legal duties require it.

Send a deletion request through account support and identify the account contact point. We assess it under applicable rules. Where local law permits, we remove data that no longer needs to be retained, but some records may remain for security, disputes or a legal requirement.

Cookies may remember a session choice or browser preference, while device signals can help us identify unusual sign-in activity. You can adjust cookie settings in your mobile browser. Turning them off may remove saved choices or require a fresh phone verification step.

A wallet name or payment reference helps us match your account action with a receipt or status enquiry. We may use DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account data, to investigate the specific transaction without requesting your password.

Yes. Available rights, identity checks and retention duties can vary because access depends on local law. Where local law permits, you may request access, correction or deletion through support. We assess each request using the account details needed to confirm ownership.