Reference

Open sawer4d Privacy Policy Clearly

sawer4d Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
sawer4d Open sawer4d Privacy Policy Clearly
CONTACT PATHS

Ask About Privacy Near Account Help

A clear contact path matters when your account details or wallet history need attention. We connect Privacy Policy questions with the same account-help route used for login and payment receipt checks, so…

Account access Use our support chat when you need to ask how phone verification, login records or device details are handled. Share your registered number and request subject only; we will not ask you to reveal a password or one-time code.
Wallet status For a DANA, OVO, GoPay or QRIS privacy question, include the transaction date and visible reference. Our account-help route can connect the policy request with a receipt or status check without asking you to send a wallet password.
Correction request If your profile detail needs correction or removal, contact support from the account path and describe the field involved. We may ask for an account check before changing records, so the request is tied to the correct person.
DATA PRACTICES

Explore How We Handle Your Records

We handle Privacy Policy requests through the same account flow that protects access to the lobby.

Account details

We use your phone number and account identifiers to create access, complete verification and answer account questions. Keep your registered number current so a privacy request can be matched to your account without exposing details to an unrelated person.

Device signals

When you move from login to the lobby on a phone or desktop, we may record device and session signals linked to access security. These signals help us investigate unfamiliar logins and are handled as part of the account privacy process.

Cookie controls

Cookies and similar storage can remember session choices and help us understand whether a page is working. You can manage available browser controls, although switching them off may affect login continuity or the way your Privacy Policy page loads.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce references, timestamps and status results. We use these details to connect a payment event with the right account and to answer receipt questions, not to collect your wallet password.

Security checks

Phone verification and account checks help us confirm who is asking for private records. If you request a change while logged out, we may ask for additional proof through the support path before discussing account data or altering a profile field.

Retention requests

We keep different records for different operational and legal periods, including account activity, security events and payment references. Ask support which category applies to your request, and we will explain available correction, access or deletion steps where local law permits.

Check Common Privacy Policy Answers

These Privacy Policy answers address the questions we expect you to ask before opening an account or sending a data request. They cover the records created by login, phone verification, cookies and Indonesian wallet activity, while keeping the next step clear. If your situation is not covered, use the support route with the smallest amount of personal detail needed to identify your account.

It covers account details, phone verification, login and device signals, cookies, payment references, support requests, retention and available privacy choices. It explains how we use these records to provide access, check account security and resolve wallet status questions where local law permits.

Phone verification links account access to the number you provide and helps us distinguish your request from an unrelated person. It can also support login protection and privacy checks. We do not need your one-time code or wallet password when you contact support.

Yes. The Privacy Policy covers references, timestamps and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a payment event to your account and investigate a receipt or status question.

Contact the account-help route and state that you want a data access request. Include your registered phone number and the record category, such as login, device or QRIS status. We may verify account ownership before explaining or providing records where local law permits.

Yes. Send a correction request through support and identify the profile field that is wrong. We may ask you to complete an account check before making a change. This protects your details from an unauthorised edit and follows the Privacy Policy request process.

Retention depends on the record category and operational or legal need. Account activity, security events and payment references may not share the same period. Ask support about the category you mean, and we will explain the available retention or deletion route where local law permits.

Cookies or similar storage can keep a session active and help us identify page or login problems. Browser controls may let you limit them, but disabling some storage can interrupt account continuity. The Privacy Policy explains how to ask about cookie-related records or choices.