Reference

theodd1sout Privacy Policy

Theodd1sout Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS for wallet activity.

Account dataWallet recordsCookie choicesSecure access
theodd1sout theodd1sout Privacy Policy
CONTACT ROUTES

Ask About Your Privacy Policy Rights

A clear contact route matters when a privacy question affects your account or wallet record.

Account privacy request Use our account support channel to ask what personal data is connected to your profile. Include your registered phone number and the requested action, such as access or correction, so we can locate the relevant account record.
Wallet record query For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, identify the payment rail and approximate transaction reference. We use those details to review the linked record without asking you to resend unrelated account data.
Access concern If your account opens on an unfamiliar device or your phone verification does not match, contact support through the account route before sharing further details. We can review the access record and explain the next privacy step.
DATA PRACTICE

What We Do With Your Data

Privacy is part of the account path from phone verification to the lobby, not a separate promise hidden from daily use.

Account creation

When you open an account, we use the details you submit and the phone verification step to create and protect your profile. We do not treat a failed verification as permission to collect unrelated personal details.

Device signals

A mobile browser or desktop session may provide device, browser, and connection signals used to recognise unusual access. These signals help us protect your account; they are not a request for access to unrelated files or contacts on your device.

Cookie controls

Cookies can keep a session active, remember a selected setting, and help us understand whether a page loads correctly. You can manage cookies through your browser, although changing them may require another sign-in during your next account visit.

Wallet matching

Payment records show the rail and status needed to match activity with your account. DANA and QRIS details, for example, help us investigate a receipt or pending status without presenting your wallet activity as a separate public profile.

Retention checks

We retain account and security records for as long as needed for the stated purpose, account protection, or a legal requirement that applies where you access the service. You can ask why a particular record remains stored.

Change requests

To correct or request removal of personal data, contact us through the account support route and identify the record concerned. We may verify account control first, then explain what can change and any reason a record must remain.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the account questions we expect before you open an account or return from a mobile device. They explain the practical data trail around phone verification, wallet status, cookies, and requests. Where the answer depends on a legal requirement or access condition, we state that directly so you know which next step to take.

It covers account details, phone verification, device and browser signals, cookie use, payment status, security records, retention, and privacy requests. The policy applies when you create an account, sign in, use a wallet rail, or contact us about data connected with your profile.

We collect the details needed to create your account and complete phone verification, along with technical signals from the sign-in device. We use those records for account access, security checks, policy administration, and support rather than for unrelated activity.

Yes. The Privacy Policy covers payment status linked to DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use the rail and transaction details needed to match a receipt, investigate a pending status, and protect the account connected to it.

Contact us through the account support channel and include your registered phone number plus a clear request for access. We may verify that you control the account before sharing personal data, and we will explain any record that cannot be provided.

Yes. Send a correction request through the account support route and identify the inaccurate field, such as a contact detail or account record. We may confirm account control first, then update the record when the requested change is supported by the available details.

Cookies can support sign-in continuity, remember selected settings, and show whether a page loads correctly on your mobile browser. You can change cookie settings in the browser itself, but doing so may end the current session or require phone verification again.

The policy is available for you to read, while account access and certain data requests depend on local law. Where local law permits, you can ask about access, correction, deletion, or retention through our account support channel.