Reference

paid4link Privacy Policy for Your Account Data

Our paid4link Privacy Policy explains what we collect when you create an account, verify your phone, browse Live Roulette Prestige or use DANA and QRIS.

Account clarityWallet data contextAccess request stepsCookie choices
paid4link paid4link Privacy Policy for Your Account Data
CONTACT ROUTES

Three Ways to Ask About Privacy

You can raise a Privacy Policy question through the support route shown inside your account, so we can connect the request with the correct phone-verified profile.

Account support route Open the support path after login and select the privacy subject. Add your account phone detail and a clear request, such as access, correction or deletion, so we can check the right record before responding.
Payment reference check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the payment reference and status only. We use those details to locate the relevant record without asking for your wallet password.
Policy change request For a correction or removal request, describe the exact account field or device record involved. We may ask for a phone verification step before changing information, helping prevent another person from altering your profile.
DATA PRACTICES

How We Handle Your Privacy Choices

We keep this policy practical by linking each data use to an account action you can recognise, such as phone verification, a QRIS status check or a return to the mobile lobby.

Account records

We may store your phone verification result, account identifiers and login events so we can maintain the correct profile. These records help us distinguish your account from another device when you return to the lobby.

Device signals

A mobile browser or desktop session can send device and connection signals linked to access activity. We use these signals for account protection and troubleshooting, not as a substitute for your phone verification detail.

Cookies

Cookies can keep a session active, remember a selected setting and help us understand which page produced an error. You can manage browser cookie controls, although limiting them may require another login or affect page operation.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain reference data, status and time. We do not ask you to place a wallet password or one-time code in a support message.

Retention periods

We keep a record only for as long as its account, support, security or legal purpose requires. When that purpose ends, the record is deleted, anonymised or placed beyond routine access according to the applicable retention rule.

Request handling

You can ask for access, correction, clarification or deletion through the account support route. We may verify ownership first, explain any legal reason for retaining a record and confirm what action we took.

Privacy Policy Answers for paid4link

These Privacy Policy answers address the account and device questions we hear most often from people using paid4link in Indonesia. They explain what to include in a request, how payment references are treated and why a phone verification step may be needed. If your situation is not covered, use the support route inside your account and point us to the relevant policy section.

It covers account identifiers, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, request handling and updates to the policy where local law permits.

Yes. The Privacy Policy explains that we may receive a payment reference, amount, status and time for a wallet or bank action. We use those details to match account activity, while your wallet password and one-time code should remain with the relevant payment service.

Open the support route inside your logged-in account and ask for an account data copy. Include the phone detail attached to your profile and describe the records you want, such as login events, cookie details or a QRIS payment reference. We may verify ownership first.

You can request a correction through the same account support route. State which field is inaccurate and provide the replacement detail without sharing a wallet password. We may complete a phone verification step before changing the record, then explain the action taken.

Device and connection signals help us understand a login, identify unusual access and investigate a mobile or desktop error. They are handled as account security and service records. You can ask what device information is linked to your profile through the policy contact path.

There is no single period for every record. We consider the reason for collection, account support needs, security checks and any rule requiring retention. When a record is no longer needed, we delete, anonymise or restrict routine access according to the applicable rule.

Check the current Privacy Policy page for its update date and changed wording. If a section is unclear, send the question through the support path inside your account, including the section title and your concern. Where access or eligibility is discussed, it depends on local law.