Reference

sui4d Privacy Policy for Your Account

Our Privacy Policy tells you what we collect when you open an account, check your phone, or use DANA and QRIS, and why each step is needed.

Account collectionWallet recordsCookie choicesYour data requests
sui4d sui4d Privacy Policy for Your Account
PRIVACY HELP PATH

Reach Us About Your Privacy Policy

A clear request path helps when you want to ask about account data, a wallet reference, or a cookie choice.

Account data request Tell us whether you want to access, correct, or question data connected with your…
Payment reference check For DANA, OVO, GoPay, QRIS, or bank transfer records, include the payment reference and…
Policy contact route Ask about cookies, retention, or a data change through our account help route.
YOUR CONTROL PANEL

Your Data Choices Across Devices

The Privacy Policy is applied across the device paths you use to reach the lobby, whether you sign in from an Android browser, another mobile browser, or desktop.

Collection at account opening

We collect the details needed for account creation and phone verification before access is granted. This lets us connect your requests, sign-in events, and payment references to one account record.

Device and session signals

Browser type, device indicators, session time, and access events may support account-security checks. These signals help us examine unusual sign-ins without treating them as wallet credentials.

Cookie preferences

Cookies can keep a sign-in session active and remember selected settings. Your browser controls can remove or restrict them, although some account steps may then need to be completed again.

Payment record handling

DANA, OVO, GoPay, QRIS, virtual account, and bank transfer references help us reconcile account activity. We do not need your wallet password to match a payment record.

Retention and removal

We retain records for the period needed for account operation, security checks, disputes, and applicable requirements. You may ask what remains stored and request removal where that option applies.

Requests and verification

When you request a copy, correction, or change, we may verify your registered phone and account details first. This protects your data from a request made by someone else.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. Each response stays focused on data collection, account access, cookies, payment references, retention, and the request path available to you.

It explains how we collect, use, protect, retain, and change account data, device signals, cookies, and payment references connected with your access where local law permits.

Phone verification links your account to the contact detail you submitted and helps protect access. It also lets us confirm that a data request comes from the account holder.

Yes. The policy covers DANA and QRIS references, as well as OVO, GoPay, virtual account, and bank transfer records used to reconcile account activity.

We may collect browser type, device indicators, session time, and access events for account-security checks. These details help us examine unusual sign-ins across mobile and desktop paths.

Contact our account help route with your registered phone and the change you want. We may verify the account first, then explain whether the requested correction or removal applies.

Retention depends on account operation, security checks, payment questions, disputes, and applicable requirements. You can ask which categories remain stored and why a period is needed.

Yes. Ask us to explain the cookies connected with login continuity or saved settings. You can also adjust browser controls, though certain account steps may need to be repeated.