Reference

oma55 Privacy Policy For Your Account

oma55 Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Auto Roulette or use a local wallet, and how we…

Clear data purposesCookie choicesAccount access recordsLocal wallet references
oma55 oma55 Privacy Policy For Your Account
PRIVACY HELP

Ask oma55 About Your Data

A direct support request gives you a practical route when a Privacy Policy question concerns your account rather than a general answer.

Account privacy request Use the support contact displayed after sign-in to ask what personal data is connected with your account, why it is used or which part of the Privacy Policy applies. We may confirm your phone detail before releasing account-specific information.
Cookie choice question If a cookie remains after you change browser settings, tell us your device type, browser path and approximate time of the change. We can explain which cookie supports account access and which setting controls optional site measurement.
Payment record check For a wallet or bank record request, include the payment rail, date and reference rather than a PIN. DANA, OVO, GoPay, QRIS, virtual account and bank transfer details help us locate the correct record without asking for unnecessary credentials.
DATA PRACTICE

Browse How We Handle Privacy

We keep this policy close to the actions that create personal data: opening an account, confirming a phone, signing in on a mobile browser, contacting support and checking a wallet record.

Account data

When you open an account, we may collect the details needed to create and maintain it, such as contact information and phone verification status. We use those details for sign-in, account messages and checks connected with your access.

Cookie controls

Cookies can remember a session or help us understand site use when your browser permits it. You can review browser cookie controls on the device you use for oma55, and you can ask support which cookie purpose relates to a specific page.

Security checks

A sign-in from a new phone or an unusual account action may lead to an additional check. We use these signals to reduce unauthorised access, and we will not ask you to disclose your password or wallet PIN for a privacy request.

Payment references

A payment record can show a rail such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, along with a reference and status. We use that operational detail to match your account request and investigate a missing or unclear record.

Record retention

We retain account, support and transaction records only for the period needed for the stated service purpose, account security, dispute handling or legal duties. To ask whether a particular record is still held, contact us with enough detail to identify it.

Changes and access

You can ask us to correct inaccurate personal data, explain its use or provide an account-related copy where the request is permitted. Include your account contact detail and a clear description; we may verify ownership before making a change.

Find Privacy Policy Answers

These Privacy Policy answers focus on the questions you are likely to have before opening or using an oma55 account in Indonesia. They cover the data created by phone verification, mobile sign-in, cookies and local payment references. If your situation is different, contact us through the account support route and include only the details needed to identify your request. Access depends on local law.

The oma55 Privacy Policy covers personal data linked with your account, including account creation details, phone verification, sign-in activity, support messages, cookies and payment references. It also explains why we use those records, how we protect access and how you can ask about correction or removal.

We may collect the contact and account details needed to create your profile, maintain sign-in and complete a phone verification step. We can also record security events, support conversations and transaction references. The policy explains the purpose of each category rather than treating every record the same way.

A payment record may contain the rail used, a reference, amount and status, but you should never send a wallet PIN or password to support. DANA, OVO, GoPay and QRIS records help us match a transaction question to your account and resolve an unclear status.

Contact us through the support route shown in your account and state whether you want access, correction or an explanation of use. Include the account phone or email and describe the specific record. We may verify that you control the account before sharing or changing personal data.

Cookies may keep a mobile session active or support site measurement, depending on your browser settings. You can review cookie controls on the phone used to sign in, then ask support about a particular cookie if its purpose is unclear. Changing cookies may affect account access.

We keep records for the period needed for the stated service purpose, account security, dispute handling or legal duties. The period can differ by record type, including account, support and payment references. Ask us about a specific record using its date, rail or account contact detail.

You can submit a removal request through the account support contact, and we will assess it against the purpose for holding the record and any applicable legal duty. Some account, security or transaction records may need to remain for a defined period. Access depends on local law.