Reference

Privacy Policy for ips66 Accounts

Our Privacy Policy explains how ips66 handles the details connected to your account, wallet activity and device access.

Account recordsWallet activityDevice accessPolicy requests
Explore Our Lobby Read FAQ
ips66 Privacy Policy for ips66 Accounts
POLICY HELP PATH

Three Ways To Ask About Privacy

A clear contact route matters when a privacy question sits beside a wallet or login issue. Start from the account support path and describe the request in plain English, including the email or phone detail linked to your account. We may ask for a verification step before discussing records, especially when your message concerns DANA, OVO, GoPay or QRIS activity. If you are in Makassar or elsewhere in Indonesia, the same policy request path applies where local law permits.

Team online

Account support path

Use the support route connected to your account when you want to ask about stored details, a phone verification record or a privacy choice. We check the account context first, so we can discuss your request without revealing data to someone using a different login.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the transaction reference and approximate date rather than sending a full wallet password. We use the reference to locate the relevant entry and may request account confirmation before describing its status.

Correction request

If a profile detail is outdated, ask us through the account contact route and state what should change. We compare the request with the verified account step before making an adjustment, while preserving records that must remain for support or legal reasons.

SIX DATA PRACTICES

What We Do With Your Records

Privacy at ips66 is handled through ordinary account operations rather than hidden assumptions. We separate login details from payment references where the process allows, limit staff access to a support need and…

Account details

We use your submitted account details to create and maintain your access, complete the clear phone verification step and respond to requests tied to your profile. We do not ask for a wallet password through a policy message or use your account details for an unrelated request.

Payment references

A payment record can include a rail name such as DANA, OVO, GoPay or QRIS, along with a reference needed to match account activity. We use that record for cashier checks and support, not as a reason to request your full wallet credentials.

Cookies and sessions

Cookies may keep a signed-in session working when you move between the lobby and account area. They can also help us understand which policy page was opened. You can adjust cookie controls in your browser, though some account functions may then require another sign-in.

Device signals

When you use a phone or desktop, technical signals such as browser type, session time and basic connection details can help us protect the account. We use them to investigate unusual access and support a login question, not to read unrelated files on your device.

Retention choices

We keep account, payment and support records only while they serve account operation, dispute handling, security checks or a legal duty. A deletion request can be limited when a record is needed for those purposes, and we explain the reason through the account contact route.

Change requests

To request access, correction or removal of a personal detail, contact us through the verified account path with the exact change you want. We may confirm your phone or account step first, then assess the request under local requirements and reply with the available action.

Privacy Policy Questions For ips66

These Privacy Policy answers address the questions we expect before an account is opened or a wallet record is queried. You can use the same support path for a question that is not listed here. Keep your message focused on the account detail, device session or payment reference involved, and do not send a password. We handle access requests where local law permits and confirm identity before discussing private records.

The ips66 Privacy Policy covers account details, phone verification, payment references, device signals, cookies, support messages and retention. It explains why we use each category, how we protect access and how you can ask for a copy, correction or removal where local law permits.

Phone verification helps us connect an account request to the person who opened the account and reduce mistaken access. We may use that verification record when you ask about profile data or a DANA, OVO, GoPay or QRIS transaction linked to your account.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a cashier event or answer a status question, while avoiding requests for your full wallet password.

You can ask for a correction through the verified account support path. State the detail that is wrong and the replacement you want. We may confirm your phone or account step before changing it, and some records may stay unchanged when retention or legal duties apply.

Cookies can keep your session active and help us understand use of the policy page or account path. Your browser settings can limit or remove them. If a session cookie is blocked, you may need to sign in again before reaching account or wallet pages.

Retention depends on why the record exists. We keep account, payment and support details while needed for account operation, security checks, dispute handling or a legal duty. If you request removal, we assess which records can be deleted and explain any required exception.

Use the support route connected to your account and describe whether you want access, correction, removal or an explanation of a record. Include a transaction reference when relevant, never a password, and be ready for an identity check before we discuss private data.

Related Pages

ips66 Indonesia Account information ips66 Casino Access guide Auto Roulette