Reference

hacksaw Privacy Policy For Your Account

Your hacksaw Privacy Policy explains what we collect when you create an account, open Lightning Roulette or use DANA and QRIS, and why each detail supports account access.

Account detailsDevice activityWallet recordsYour privacy choices
hacksaw hacksaw Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact route matters when your account details or wallet reference look unfamiliar. We keep privacy questions close to the account support path, so you can ask about a phone verification record, a QRIS receipt or access to your personal details without describing the issue to several teams. Use the support route shown in your account area and include the email or phone linked to your profile.

Team online

Account access

If you cannot reach the account area after phone verification, tell us which device path you used and the last successful login. We use those details to locate the correct record without asking for your wallet password.

Wallet status

For a DANA, OVO, GoPay or QRIS reference, send the receipt number and account contact details through support. We can check which payment record is attached to your profile while limiting exposure of unrelated wallet data.

Data requests

To ask for access, correction or removal, identify the account email or verified phone number and describe the request. We may ask for a further account check before changing records, so another person cannot alter your profile.

DATA CONTROLS

How We Handle Privacy Day To Day

Privacy controls should match the steps you actually take, from opening an account on mobile to checking a wallet reference beside a game lobby.

Data handling

We use account contact details for login, phone verification, recovery and privacy requests. Activity records can show that your account opened Lightning Roulette or Mega Fishing, helping us protect access and investigate a disputed session.

Cookies

Browser cookies can keep your session connected while you move from the account page to the lobby. Clearing them may sign you out or trigger phone verification again; this does not erase records already held for account service.

Account security

We may compare a new device path with earlier login details before allowing account access. If a device check fails, use the account support route rather than sharing a DANA, OVO or GoPay password with anyone.

Record retention

We keep identity, payment reference and support records only as long as needed for service, security, dispute handling and legal duties. A request to remove data may not cover records that we must retain for those purposes.

Policy questions

You can ask which data is connected to your account, why we use it or whether a specific device event is stored. Include your verified contact detail so we can discuss the correct profile without exposing it to another person.

Change requests

If your phone number, email or account detail changes, contact us through the account support path. We verify the request before updating it, because an unchecked change could interrupt access to your wallet records and account recovery.

Privacy Policy Answers For hacksaw

These Privacy Policy answers focus on the account moments that matter before you open access: phone verification, mobile sessions, wallet references, cookies and requests for data changes. If your question is not listed, use the support path inside your account and give us the verified contact detail connected to the issue.

The hacksaw Privacy Policy covers account details, phone verification, device activity, cookies, support records and payment references linked to DANA, OVO, GoPay, QRIS, virtual account or bank transfer use. It also explains retention, security checks and how to request access or corrections.

We use your phone number for account creation, verification, recovery and certain security checks. A verified number helps us match a privacy request to the right account. We do not need your DANA, OVO or GoPay wallet password for these account steps.

The Privacy Policy allows us to record useful device and session signals, such as a new mobile path or a browser session, to protect account access. These signals can prompt another verification step, but they are not presented as a public profile.

We can store payment references, status details and receipts connected to your account, including QRIS, DANA, OVO, GoPay, virtual account and bank transfer activity. We use these records to match account support and disputes, not to request or store your wallet password.

Use the support path in your account area and identify the verified email or phone number on the profile. Ask for access to your data, a correction or a retention explanation. We may complete an account check before releasing or changing personal details.

You can request removal of personal details through the account support path. We assess the request under the Privacy Policy and local requirements. Some identity, payment or support records may remain when needed for security, disputes, account service or legal duties.

We make this Privacy Policy available for Indonesian account access where local law permits. Eligibility and access depends on local law. If you are in Bandung or elsewhere in Indonesia and cannot reach the policy or account area, contact support through the available account path.