Reference

sigma168 Privacy Policy for Your Account Data

Our Privacy Policy explains what account details we collect, why we use them and how you can request access or changes.

Clear data purposesWallet record contextAccess request pathCookie choices

How Our Privacy Policy Covers Wallet Records

sigma168 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to details you provide during account creation, including contact details, phone verification results and records linked to your account activity. We may also receive transaction references when you use DANA, OVO, GoPay or QRIS, along with bank transfer and virtual account references

1
needed to match a cashier request. We use these records to operate access, check payment status, detect unusual sign-in activity and answer account requests. Device type, browser signals, approximate location and cookie choices may be recorded to keep sessions working and understand page use. We retain
2
records only for operational, dispute, security or legal needs, then remove or restrict them through our retention process. Where access or eligibility is discussed, it depends on local law. The policy applies to the data handling connected with sigma168, not to separate services linked from another
3
provider.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

SUPPORT PATHS

Get Privacy Answers Beside Login Support

A clear contact route helps when you need a copy, correction or explanation of an account record.

Data access request Ask our support desk for the personal data connected with your account. We may request a phone verification step before releasing records, so the reply goes to the correct account holder.

Correction request Tell us which account detail needs changing and why it is inaccurate. Include the relevant account step, such as a phone number update or wallet status record, without sharing your password.

Wallet record help For a DANA, OVO, GoPay or QRIS reference, send the transaction date and status shown in your account. We use that path to separate a payment query from a privacy request.

DATA PRACTICE

What sigma168 Does With Account Data

We keep our Privacy Policy practical: each data category has a reason tied to account access, payment matching, security or support.

Data handling

We use contact details for account access, verification and support replies. Activity and transaction records help match wallet status, investigate disputes and maintain a usable record of requests made through the account.

Cookies and sessions

Cookies can keep your login path, language setting and selected page state available during a visit. You can adjust browser cookie controls, though blocking them may require another sign-in.

Account security

Phone verification and sign-in checks help us confirm an account request belongs to you. Never send a password or one-time code to support; our team does not need either detail.

Retention approach

We keep account, wallet and support records for the period needed for service operation, dispute handling, security checks or legal duties. After that, records are removed, restricted or separated from direct account details.

Who handles requests

Our support desk receives privacy questions, access requests and correction requests through the account contact path. We may ask for matching details before discussing records tied to your phone number.

Changing your data

You can request a correction, ask what data is held or question a processing purpose. Describe the requested change clearly, and we will assess it under the Privacy Policy and local law.

Privacy Policy Questions About Your Account

These answers cover the searches we hear most often about the sigma168 Privacy Policy. They explain the records behind phone verification, mobile sessions and local wallet references, then point you to the support desk when a request needs account matching. If your situation involves access or eligibility, the outcome depends on local law.

It covers account details, phone verification, device and cookie signals, support messages, activity records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm account ownership before access changes, data copies or wallet-related support. It also gives our security checks a practical signal when a sign-in pattern appears unusual.

Yes. We may store transaction references and status details needed to match DANA or QRIS activity with your account. We do not need your wallet password or one-time code for a support request.

Use the support desk linked near login and ask for an account data copy. Include the phone number tied to the account, then complete any ownership check we reasonably need before sending records.

Yes. Send a correction request through the account support path and identify the inaccurate field, such as a phone detail or wallet reference. We assess the request under this Privacy Policy and local law.

Retention depends on the record and its purpose. We may keep account, payment, security or support records for operation, dispute handling or legal duties, then remove or restrict them when no longer needed.

Cookies can remember a session and selected page settings on your device. Browser controls can limit them, but some account steps may ask you to sign in again or confirm your device.

sigma168 Privacy Policy for Your Account Data

Get Privacy Answers Beside Login Support

What sigma168 Does With Account Data

Data handling

Cookies and sessions

Account security

Retention approach

Who handles requests

Changing your data

Privacy Policy Questions About Your Account

01 What does the sigma168 Privacy Policy cover?

02 Why does sigma168 request phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my data from sigma168?

05 Can I ask sigma168 to correct account data?

06 How long does sigma168 keep my account records?

07 How do cookies affect my sigma168 Privacy Policy choices?

Related Pages