Reference

giga33 Privacy Policy for Your Account

The giga33 Privacy Policy explains what account, device, wallet and support details we use, why each detail is needed, and how you can ask about it.

Account clarityWallet statusCookie choicesContact requests
giga33 giga33 Privacy Policy for Your Account
POLICY HELP PATH

Where To Ask About Privacy Policy

A clear contact route matters when you want to understand a record or correct an account detail.

Account privacy request Ask about the personal details connected to your account through the support path shown after login. We may ask you to confirm an account detail before discussing or changing private records.
Wallet record question For DANA, OVO, GoPay or QRIS status concerns, send the relevant receipt reference through account support. We use that reference to separate a payment record from unrelated account activity.
Access concern If a sign-in or verification step exposes an unexpected privacy issue, contact us from the account area and describe the device path. Do not include passwords or complete wallet credentials.
DATA HANDLING

How Our Privacy Policy Works In Practice

We keep this policy practical by linking each data use to an account task: access, verification, wallet reconciliation, support or site function.

Account details

We handle the contact and verification details you submit when opening or securing an account. These details help us distinguish your account from another person’s request and maintain the correct access path.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us check whether an account action has a matching status. We do not ask for your wallet password through support.

Device and sign-in data

We may record device type, browser details, approximate connection data and sign-in events to identify unusual access. A mobile sign-in and a desktop sign-in can therefore appear as separate security events.

Cookies and settings

Cookies can keep an account session active, remember selected settings and help us understand basic page errors. You can manage or remove cookies through your browser controls, although some account steps may then need repeating.

Retention and deletion

We retain records while they support account security, payment reconciliation, support handling or applicable legal duties. When a record no longer serves those purposes, we remove it or reduce its link to your account.

Changes and corrections

To request a correction, access copy or privacy change, contact us through the account support path with the affected detail. We verify the request before making a change or explaining why a record remains.

Privacy Policy Questions For giga33 Accounts

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. They explain the practical route for data access, corrections, cookies and wallet references, while local eligibility depends on local law.

The giga33 Privacy Policy covers account details, verification records, device and sign-in data, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS or bank transfer.

We use contact and verification details to connect you with the correct account, protect sign-in access and handle privacy requests. The requested details should match the account step you are completing.

Yes. The Privacy Policy includes the payment status or reference needed to match DANA and QRIS activity with your account. We do not need your wallet password to check that status.

Use the support path inside your account and identify the record you want to access or correct. We may verify an account detail first, then explain the available action under local law.

Cookies can maintain your account session, remember settings and help identify page errors. You can manage them in your browser, but disabling some cookies may require you to repeat an account or sign-in step.

We keep records for as long as they support account security, payment reconciliation, support handling or applicable legal duties. After that need ends, we remove or de-link the record where appropriate.

Yes. Contact us through the support route displayed in your account and describe the concern without sending passwords or full wallet credentials. Include a receipt reference only when your request concerns payment status.