Reference

Privacy Policy for Your osis33 Account

osis33 Privacy Policy explains how we collect, use and protect the details connected to your account, phone verification and wallet activity.

Account clarityWallet recordsMobile privacy
osis33 Privacy Policy for Your osis33 Account
CONTACT ROUTES

Privacy Help Near Your Account

A clear contact route matters when a Privacy Policy question concerns your own account.

Account request Use the support route beside account access when you want to ask what personal details we hold or why phone verification is needed. We may confirm the account phone number before discussing records, and you should never send a wallet PIN or complete payment credential.
Wallet record For a DANA, OVO, GoPay or QRIS data question, include the payment rail and receipt reference rather than your wallet password. We use those details to locate the relevant account event and explain what was recorded, subject to identity checks and local-law requirements.
Access concern If a mobile sign-in displays another device or an unfamiliar account event, contact us through the account support path before trying repeated payment steps. We can review the session details connected to your account and tell you what verification action is required.
HANDLING DETAILS

How We Handle Your Privacy

We treat the Privacy Policy as an operating process, not a footer that disappears after account creation.

Account data

We may hold the phone number, account identifier and verification state used to let you sign in. These details help us distinguish your account from another session and reduce confusion when you contact support about access or a wallet record.

Device signals

A mobile browser can provide session, browser and device signals connected with a sign-in. We use these signals to detect unusual access and troubleshoot a failed account step; they are not a substitute for your phone verification or wallet password.

Cookies

Small browser files may keep a session active, remember a basic preference or help us understand whether a page loaded correctly. You can clear them through your browser settings, although doing so may require you to repeat sign-in and phone verification.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with an account event. We use the reference to match status and receipts, while wallet PINs and full payment credentials should remain with your payment provider.

Retention period

We keep personal records only for the period needed for account operation, security checks, dispute handling and lawful requests. When a record is no longer needed, our process is to delete it, anonymise it or restrict access where retention still applies.

Change request

To request correction, removal or a copy of eligible personal data, contact support from the account route and state the exact change. We verify ownership first, explain any limit caused by a payment dispute or legal duty, and record the outcome.

Privacy Policy Questions About osis33

These Privacy Policy answers focus on the account and payment questions you are most likely to search before opening access. They explain what we collect, how mobile sessions work, and which contact step to take when you need a correction. Where access or eligibility is discussed, it depends on local law.

The osis33 Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages and payment references. It explains how we use those records for access, security, receipt matching and lawful requests, including activity linked with DANA, OVO, GoPay, QRIS or bank transfer.

No wallet password should be sent to us through chat, email or an account form. Our records may contain a DANA or QRIS payment reference and its status so we can match an account event. Your wallet credentials remain with the relevant payment provider.

Contact us through the support path linked from account access and state that you want a copy of eligible personal data. Include your account phone number and a clear request. We verify ownership before discussing records, then explain the available response and any lawful restriction.

Mobile session and browser signals help us identify unusual sign-in activity, keep a session working and diagnose a failed verification step. They are used alongside your account details, not as a replacement for phone verification. Clearing browser data can require another sign-in.

You can ask for correction or removal through the account support route. We first confirm that you control the account, then check whether the record is still needed for security, a payment dispute or a lawful request. If deletion cannot happen immediately, we explain why.

We retain payment records for the period needed to match receipts, investigate account disputes, protect access and meet lawful duties. A reference for OVO, GoPay, virtual account or bank transfer may therefore remain after a session ends. Records are deleted, anonymised or restricted when applicable.

The same Privacy Policy applies to your Indonesia account and mobile sessions, including access from Jakarta or another city. We may adjust access or data handling when required by local rules, because eligibility and access depends on local law. The current policy wording remains available on this page.