Reference

OLYMPUS CLUB Privacy Policy

OLYMPUS CLUB Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Clear data purposesWallet record contextRequest access changesCookie choices
OLYMPUS CLUB OLYMPUS CLUB Privacy Policy
REQUEST PATHS

Get Help With Privacy Requests

A clear request path helps you ask what we hold, why we use it or how to correct an account detail. Contact us through the support route shown on the OLYMPUS CLUB site and include the phone number linked to your account, without sending a wallet PIN or password. We use the account and receipt context to locate the right record, including cases where a QRIS status or bank transfer reference needs checking.

Team online

Access request

Ask for a copy of account details connected with your phone verification and sign-in history. We may request an account check before releasing data to the person who controls that account.

Correction request

Tell us which account detail needs changing and why. We may compare your request with the existing phone record or a DANA, OVO or GoPay transaction reference before applying an update.

Wallet status check

If a payment receipt is missing, share the date, rail and reference rather than private credentials. We can trace the relevant QRIS, virtual account or bank transfer record through the support path.

DATA CONTROLS

Your Account Data Across Devices

Privacy protection starts with practical account controls rather than broad promises. We separate sign-in checks from wallet references, keep access records for security review and use device signals to identify unusual account…

Account collection

When you open an account, we collect the details needed for the account path, including your phone number and verification result. We also record sign-in events so we can identify access that does not match your normal session.

Payment matching

A wallet selection such as DANA, OVO, GoPay or QRIS creates transaction context, not permission to see your wallet PIN. References help us match a cashier status with the correct account and receipt.

Cookie choices

Cookies can keep your session and selected account path available between pages. You can manage browser cookie settings, although restricting them may require another sign-in or interrupt parts of the privacy preference flow.

Mobile and desktop

Our mobile browser path and desktop pages may create device and session records for the same account. Moving between devices does not remove earlier records; it adds a new access event for security checks.

Retention approach

We retain account, payment and security records only for the period needed for the stated purpose, account support, dispute handling or legal requirements. When a record is no longer needed, our handling follows the applicable retention process.

Policy changes

If our collection or use changes, we update this Privacy Policy and show the revised date on the page. Check the policy before confirming phone verification, especially when returning after a long period away.

Privacy Policy Questions For Indonesia

These answers address the privacy searches we hear most often before an account is opened. They cover the records created during phone verification, wallet activity, mobile access and support contact, while the full Privacy Policy remains the controlling page for current wording.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify the account path, help match you with the correct account and investigate access or receipt questions. We do not ask you to send a wallet PIN.

Yes. We may keep a transaction reference, selected rail, status and timing so support can match a DANA or QRIS request with your account. The wallet provider's own privacy terms also apply.

You can send an access request through the support path on our site. Include the phone number linked to your account, and we may complete an account check before providing records.

Contact support and identify the detail that needs correction. We may compare your request with phone verification or a payment reference before changing the account record, where local law permits.

Retention depends on the record's purpose, such as account support, payment disputes, security checks or legal requirements. The Privacy Policy does not promise one period for every record.

No separate policy is created for mobile access. The same Privacy Policy covers mobile and desktop sessions, although each device may create its own sign-in and security event.