Reference

Privacy Policy for Your heylink Account

Our Privacy Policy explains what account details we collect when you open access, how wallet records from DANA, OVO, GoPay and QRIS are used, and how you can…

Account dataWallet recordsCookie choicesContact route
Explore Our Lobby Read FAQ
heylink Privacy Policy for Your heylink Account
ASK ABOUT DATA

Get Privacy Policy Help Near Login

A clear contact path matters when you want to understand a privacy record, correct an account detail or check why a wallet reference appears in your history.

Account data questions Ask us which account details are connected with your phone verification, how a login event is used, or how to correct a spelling or contact detail. Include the registered phone number in the support request, but never send your password or a wallet PIN.
Wallet record checks For a DANA, OVO, GoPay or QRIS record, share the date, amount reference shown in your account and the payment rail used. We can explain the record’s purpose and direct you to the right path when a receipt or status needs checking.
Policy access route Open the Privacy Policy from the policy link in the account area and contact support when wording needs clarification. Your request can ask about collection, use, retention or correction, while access and eligibility remain dependent on local law.
CONTROL YOUR RECORD

Privacy Choices Around Account Use

We handle this policy area through account-level steps rather than broad claims. Phone verification helps connect access activity with the right account, while device and login signals help us investigate unusual entry.

Data we receive

When you open an account, we may receive contact details, phone verification results, login timestamps, device signals and payment references. These details help connect your account activity with the requested wallet or bank step, while your bank keeps its own transaction record.

Cookie function

Cookies can keep a session active, remember a page setting and help the account area load correctly on your device. Your browser offers controls for cookie storage. Turning some cookies off may affect login continuity or parts of the policy and wallet path.

Account security

We use phone verification and login activity checks as part of account security. Keep your phone, password and wallet PIN private, and contact support if an entry does not look familiar. Do not send a one-time code in a support message.

Payment references

A wallet or bank reference lets us investigate a status question without treating the payment rail as part of our own account database. For QRIS, DANA, OVO, GoPay, BCA, BRI, Mandiri or BNI steps, keep the receipt available for a focused request.

Retention approach

We retain information while it serves account operation, security checks, payment questions, dispute handling or a lawful requirement. Retention can differ by record type. Ask support how a specific account detail or receipt reference is handled under this Privacy Policy.

Requesting changes

You can request access to a data record, correction of an account detail or clarification of its use through the policy contact route. Tell us the request type and registered phone detail. We may need an account check before discussing private information.

Privacy Policy Answers Before Access

These Privacy Policy answers focus on the questions you may have before opening or using a heylink account in Indonesia. They cover the details tied to phone verification, cookies, payment references, account access and correction requests. If your situation involves a specific DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry, keep its receipt reference ready when contacting support. Availability depends on local law.

The heylink Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, support requests and retention. It explains why these details may be handled for account access, security, payment status checks and lawful requirements in supported Indonesia regions.

We may handle your contact details, registered phone information, verification status, login events, device signals and account activity needed for the service. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps may also appear in our records.

Contact us through the policy support route and state that you want access to your data under the Privacy Policy. Add your registered phone detail and the record you mean, such as a login event or payment reference. An account check may be required.

Yes. Send a correction request through support with the registered phone detail and the field that needs changing. For a wallet or bank record, include the receipt reference rather than a PIN. We will explain the next account step and any legal constraint.

Cookies may keep your session active, remember a page setting and support account-area functions on your device. You can manage storage through browser controls. If a change affects login continuity, contact support so we can explain which policy or account function is involved.

We keep payment references for as long as they are needed for account operation, status checks, security, dispute handling or a lawful requirement. The period can vary by record. Ask support about a particular DANA, QRIS, bank transfer or virtual account reference.

Yes. Account access and eligibility depend on local law, and service availability may differ by location. The Privacy Policy still explains how relevant account and payment details are handled where local law permits. Contact support if you need the policy link for your account area.

Related Pages

heylink Indonesia About Us GoPay Instant Payout Lightning Roulette Room Account information