Reference

Privacy Policy for Your sigacor88 Account

sigacor88 Privacy Policy explains how we use the details connected to your account, device and wallet activity.

Account data clarityWallet status contextPolicy access anytimeIndonesia wording
sigacor88 Privacy Policy for Your sigacor88 Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear support route helps you ask about personal data without explaining your whole account history repeatedly. Contact us through the support path linked from the account area when you need to ask what we hold, why a phone check is needed or how a wallet reference is connected to a transaction record. Include the email or phone detail attached to your account, but do not send a password or one-time code. We use the account support route to confirm the request belongs to you before discussing private details.

Team online

Account data request

Use the support path from your signed-in account to ask which personal details are linked to your profile. We may ask for an account step or phone confirmation before sharing private records, so a request is not disclosed to the wrong person.

Wallet record question

If DANA, OVO, GoPay or QRIS appears in a payment reference, tell us the date and reference shown in your account. We use those details to locate the relevant record without asking you to send wallet passwords, PINs or one-time codes.

Access or correction

Ask support to correct an outdated contact detail or explain a device record through the same account route. We first verify your connection to the account, then tell you what action is available under local requirements and where access permits.

DATA PRACTICE

How We Handle Your Privacy Choices

Our privacy process follows the path your data takes rather than treating every record as the same.

Account security

Phone verification is used before account access and may be requested again when sign-in behaviour changes. Keep your password and verification code private. We do not ask you to place either one in a support message about Privacy Policy.

Device signals

When you move between a mobile browser and desktop, we may record basic device, browser and session signals. These help us investigate unusual access to your account, but they are handled as security context rather than as a profile of your personal interests.

Cookies

Browser cookies can remember a session choice, policy preference or sign-in state. You can manage browser storage through your device settings, although removing essential cookies may require you to complete phone verification again before account access.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account event can create a reference used for reconciliation. We use the reference and status needed for the account record, not your wallet PIN or private wallet login.

Retention questions

We retain records only while they support account operation, security checks, dispute handling or a legal obligation. If you ask when a particular record is removed, provide its account context and we will explain the retention reason that applies.

Changes to data

You can ask us to correct a name, phone detail or contact route that no longer matches your account. We may confirm the request through the existing account path, then tell you whether the change can be made directly or needs support action.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and wallet questions we expect you to ask before opening access. If your situation is unusual, use the support route connected to your account so we can check the relevant record instead of asking you to share sensitive credentials in open messages.

It covers account details, phone verification, sign-in records, device and browser signals, cookie preferences, support messages and payment references. The policy explains why we use each category, how it supports account access or security, and how you can ask about correction, deletion or retention.

Yes. The Privacy Policy covers the transaction references and status details needed to reconcile DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We do not need your wallet PIN or private wallet password to investigate a payment reference.

Phone verification connects an account request to the contact detail supplied during access and helps reduce mistaken or unusual sign-ins. We may request it before account access or after a device change. Never send the verification code to support or another person.

You can ask through the support path attached to your account. Tell us the contact detail or account context that helps locate your records. We may confirm your identity first, then explain the data categories we hold and any limits required by local law.

Send a correction request through account support and identify the detail that is outdated, such as a phone number or contact route. We may use phone verification or another account step before making a change, so the corrected record belongs to you.

You may ask support about deletion, but some records can remain when needed for account security, payment reconciliation, dispute handling or a legal obligation. We will explain which data can be removed, what must be retained and how access depends on local law.

Open the Privacy Policy link from the account area or the support path on the site. Check it before continuing with phone verification or wallet activity. The policy applies where local law permits, and support can clarify a section tied to your account.