Reference

Read the goalparlay Privacy Policy

The goalparlay Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use account tools linked with DANA, OVO…

Account dataWallet referencesDevice accessPolicy choices
goalparlay Read the goalparlay Privacy Policy
PRIVACY CONTACT PATH

Contact us about your privacy choices

A clear contact route matters when you want to ask about account data, correct a detail, or understand a wallet reference. Use the support contact shown after you sign in, and include the account step or receipt reference that caused your question. We may ask for enough account information to locate the right record, but you should not send a password or full payment credentials. Our team can also explain how to request a data change when access depends on local law.

Team online

Account contact

Use the support route inside your signed-in account for a privacy request. Tell us whether your question concerns phone verification, a device sign-in, or a profile detail so we can direct it to the right record.

Wallet reference

If your question relates to DANA, OVO, GoPay or QRIS, include the visible receipt or status reference rather than private wallet credentials. This lets us match the account event while limiting the data you share.

Access concern

When a login or account-access concern involves personal data, contact us through the account support path and describe the device step. We may verify ownership before discussing records or applying a requested correction.

DATA HANDLING DETAILS

See how we handle account data

We keep this policy practical by connecting each data use to an account action: access, verification, wallet status, security, support or legal duties.

Collection

We collect details you enter during account creation and phone verification, plus technical data such as browser type, device signals and session activity needed to connect requests with your account.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be linked to an account event. We use the reference to reconcile status and support requests without asking for your wallet password.

Cookie controls

Cookies and similar browser storage can keep a sign-in session working and remember selected account settings. Clearing them may sign you out or remove saved choices, but it does not erase records already held.

Security checks

Phone verification and device-session checks help us distinguish an account owner from an unfamiliar sign-in. If a sign-in looks unusual, we may request an additional account step before sharing private details.

Retention

We retain account, support and transaction references only for as long as needed for the stated service purpose, security checks, dispute handling or legal duties. You can ask us to explain the reason for a retained record.

Change requests

You can ask us to correct inaccurate profile data, explain a data use, or clarify a disclosure through the signed-in support route. We may confirm account ownership before making a change or responding.

Browse answers about Privacy Policy

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access. They cover collection, wallet references, device behaviour, corrections and contact steps for goalparlay in Indonesia. Where a request affects eligibility or access, the outcome depends on local law.

The goalparlay Privacy Policy covers data collected during account creation, phone verification, sign-in, support contact and wallet-related account steps. It also explains device signals, cookies, retention, security checks, disclosures and the way you can ask about or correct your records.

Phone verification helps connect an account to the contact detail supplied during access and supports checks when a sign-in looks unfamiliar. We may use the result to protect private account data, and we may request another ownership check before discussing records.

Yes. The Privacy Policy covers account-linked references showing a DANA, OVO, GoPay, QRIS, bank transfer or virtual account step. These references help us check status and respond to support questions; they are not a request for your wallet password.

We may collect technical signals such as browser type, device information, session details and access timestamps. A phone and desktop can produce different signals, which helps us identify a session, investigate unusual access and protect the account record.

You can request a correction through the support contact shown inside your signed-in account. State which profile detail is inaccurate and provide the relevant account step. We may verify ownership first, then explain whether the change can be made under local law.

Retention depends on why the record exists. Account, support and transaction references may be kept for service operation, security checks, dispute handling or legal duties. You can contact us through the account path and ask which reason applies to a particular record.

Sign in and use the support contact displayed in your account area. Include a clear privacy question and, where relevant, a receipt or status reference. Do not send passwords or full wallet credentials. Access or eligibility depends on local law.