Reference

Open sapu4d Privacy Policy Before Access

sapu4d Privacy Policy explains how we collect, use and protect the details connected to your account, wallet status and mobile access.

Account dataWallet recordsCookie choicesAccess requests
sapu4d Open sapu4d Privacy Policy Before Access
CONTACT ROUTES

Reach Us About Your Privacy Request

A clear support route helps when you want to ask about a Privacy Policy entry, correct an account detail or understand a wallet record.

Account privacy request Use the account support route to ask for a copy, correction or explanation of…
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the payment date, amount reference…
Access and correction If a Privacy Policy request concerns mobile-browser access, account closure or an incorrect phone…
DATA PRACTICES

Switch On Clear Account Data Safeguards

Privacy depends on small operational choices, so we describe them in plain terms rather than hiding them behind broad promises.

Collection at account opening

We collect the phone detail and verification result needed to create and protect your account. If you browse the lobby without completing an account step, technical browser data may still record the session, but it is not treated as a completed profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries help us match a cashier event with your account. We use the reference and status needed for checking, rather than asking you to provide a wallet password or full private credential.

Cookies on mobile

Our mobile browser path can use necessary cookies to keep a session connected while you move from login toward the lobby. Clearing browser cookies may sign you out or remove saved preferences, so you may need to repeat the phone verification step.

Security controls

Phone verification, session checks and account activity records help us distinguish your access from an unfamiliar device. We do not ask you to publish a password in a support message, and a privacy request can receive an account check before any change.

Retention and removal

We keep account, payment and security records only for the period needed for service operation, dispute checks and applicable legal duties. Ask us what remains for your profile; we can explain the category, purpose and available removal or restriction route.

Request ownership

We handle Privacy Policy questions through the account support path so the request stays connected to the correct record. You can ask for access, correction or clarification, and we may request matching details before releasing information or changing an account field.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the questions we expect you to ask before creating an account or checking a wallet status. They cover the information collected, mobile cookies, payment references, correction requests and local access wording. If your situation is not listed, use the account support route with only the details needed to identify your request.

It covers account details, phone verification, browser and device records, cookies, payment references, security events, retention and your request options. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be used to check an account-related payment status.

Phone verification connects an account request to the person controlling the submitted number and helps us protect access from an unfamiliar device. We record the verification result for security and account handling, not as a reason to request your password through support.

We use the payment reference, wallet name and status needed to match a DANA or QRIS event with your account and investigate a receipt question. You should not send a wallet PIN, password or complete private credential when asking us to check the record.

Yes. The policy applies when you reach the account path or lobby through a mobile browser, as well as desktop access. Necessary cookies may keep your session connected; clearing them can sign you out and require phone verification again before account access.

Use the account support path and state whether you want access, correction or an explanation. Add your verified phone number and the specific field or record involved. We may perform an account check before responding, so another person cannot request changes for you.

Retention depends on the purpose of the record, such as account security, payment reconciliation, dispute handling or a legal duty. Ask support what category applies to your request and whether removal, restriction or another lawful handling option is available.

Access or eligibility depends on local law. We expect you to check the rules that apply to your location before opening an account, and our Privacy Policy still explains data handling for an account request made where local law permits access.