Reference

ular4d Privacy Policy, Made Clear

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or check wallet status through DANA, OVO, GoPay and QRIS.

Account recordsCookie choicesWallet dataAccess requests

Explore Our Lobby Read FAQ

Explore What Our Privacy Policy Covers

ular4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to data connected with your ular4d account, including the phone number used for verification, sign-in records, device details, support messages and payment references. We use these records to open your account path, protect access and match a wallet status when you select

1
DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We do not ask for data unrelated to these account tasks. Browser storage may remember a session or your cookie choice, while security logs help us detect unusual access. We keep records only for the period
2
needed for account service, security, dispute handling or legal duties. Where local law permits, you may ask what we hold, request a correction, or ask us to review a deletion request. Eligibility and access depends on local law, so a policy request does not change those
3
conditions.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Reach Our Privacy Help Path

A clear account route helps when a privacy request and a wallet record appear together.

Account access request Use the account help path to ask for a copy of personal data linked to your phone verification. We may ask for account checks before releasing records, so your details stay with the right account.

Wallet record question Mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account when a payment reference needs checking. Naming the rail helps us narrow the record without asking you to repeat unrelated account details.

Correction request Tell us which profile field is wrong and what should replace it. We compare the request with your account step and phone verification before changing a record used for access or security.

DATA PRACTICES

Check How We Handle Your Records

Your privacy choices are tied to practical account controls rather than broad promises. We separate sign-in data, wallet references and support messages so a request can be handled against the correct record.

Data collection

We collect account fields, phone verification results, device signals, session events and payment references when they support access, security or a requested wallet check. We avoid collecting unrelated personal details.

Cookie controls

Cookies can keep your signed-in path and remember a browser setting. You can clear them through your browser controls, though removing session cookies may require another account sign-in.

Account security

We use phone verification and sign-in checks to reduce mistaken access. Never send us your password or a complete wallet secret; our privacy path does not need either item.

Record retention

We retain account, security and payment references for the period needed to provide access, resolve a query, examine a dispute or meet a legal duty, then review whether continued storage is needed.

Correction process

A change request should name the affected field and account contact. We may compare it with phone verification or a recent account step before updating records that protect your access.

Sharing questions

Ask through the account help path if you want to know why a record was used or who handles a service task. We explain the relevant purpose without asking for unnecessary credentials.

Ask About Your Privacy Policy Rights

These Privacy Policy answers address the account questions we expect from Indonesian customers before they open an account. They cover wallet references, mobile browsing, cookies, corrections and access requests. For a personal request, use the account help path so we can connect the question with the correct phone verification record.

It covers account details, phone verification, device and session records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Where local law permits, you can ask for a copy of personal data linked to your account. Start through the account help path and complete any identity check needed to protect your records.

Phone verification links an account request to the correct person and helps reduce mistaken sign-ins. It can also support a correction or access request when several wallet references appear in one account.

We use DANA and QRIS references to match a requested payment status or account query. They are retained only for service, security, dispute handling or legal duties described in this policy.

Yes. Your browser settings can clear cookies, but this may end the current session and require another sign-in. Cookie removal does not automatically erase account records held for other purposes.

Send the field name and corrected value through the account help path. We may ask you to confirm the phone linked to the account before changing a record used for access or security.

No. Access or eligibility depends on local law. This Privacy Policy explains data handling and request routes, but it does not replace the local conditions that apply to your account.

ular4d Privacy Policy, Made Clear

Reach Our Privacy Help Path

Check How We Handle Your Records

Data collection

Cookie controls

Account security

Record retention

Correction process

Sharing questions

Ask About Your Privacy Policy Rights

01 What does the ular4d Privacy Policy cover?

02 Can I request my data under the Privacy Policy?

03 Why does ular4d need phone verification?

04 How are DANA and QRIS records handled?

05 Can I clear cookies on my mobile browser?

06 How do I correct an account record?

07 Does the Privacy Policy change local access rules?

Related Pages