Reference

Open sweet55 Privacy Policy With Clarity

sweet55 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and wallet screens.

Account recordsWallet referencesCookie choicesContact path
sweet55 Open sweet55 Privacy Policy With Clarity
ASK OUR DESK

Contact Support About Your Privacy Policy

A clear support route helps when a Privacy Policy question concerns a login event, wallet receipt or device record.

Account questions Use the account support area when you want to ask what personal details we hold or why phone verification appears in an access record. Include your registered phone number so we can match the request without asking you to send a password or private login code.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference and approximate time through support. We can compare that reference with the account record and explain which data is needed to check status, without requesting your wallet PIN.
Security concern If a sign-in or device entry looks unfamiliar, contact support from the account path as soon as possible. We can review the access details linked to your account, guide a credential change and record the security request for follow-up.
DATA HANDLING

Browse sweet55 Privacy Controls Clearly

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Account details

When you open an account, we use the details you submit to create access, send account messages and connect your phone verification step. Check your entries before continuing, because an incorrect phone number can make it harder to identify your account or answer a records request.

Cookie choices

Cookies and similar device storage can remember a sign-in preference, preserve a session and help us understand which page produced a technical error. Your browser settings can restrict them, although changing those settings may require another login before the account path works.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we handle references such as amount status, channel and time so support can match a receipt. We do not need your wallet PIN to investigate a payment record.

Device security

We may record browser type, device signals, login time and approximate network details to identify unusual access. If you switch from a phone to desktop, those events can appear as separate entries and may prompt an additional account check.

Retention period

We retain a record only for the operational, security or legal purpose connected to it, then remove or restrict it when that purpose ends where applicable. A support request can ask us to explain why a particular account or receipt record remains.

Change request

To request correction, deletion or a copy of eligible personal data, contact us through account support and identify the record precisely. We may need to confirm account ownership before acting, so another person cannot change your details without your knowledge.

Get Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the records created by login, phone verification, cookies and local wallet activity, along with the steps for asking about access or correction. If your question is not listed, use the account support path and include only the details needed to identify the issue.

The sweet55 Privacy Policy covers personal details, phone verification, login and device events, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask about correction or deletion.

Yes. Privacy Policy applies to references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use channel, time and status details to match a receipt to your account. We do not ask for your wallet PIN when checking that record.

We collect limited device and login signals to protect your account and investigate unusual access. A phone browser and a desktop browser can create separate events, including time and browser details. This helps support explain an access concern without needing your password.

Send the request through your account support area and state whether you want a copy or a correction. Include your registered phone number and identify the relevant record. We may confirm account ownership first, then explain what can be supplied or changed.

We keep records for the operational, security or legal reason that requires them, rather than retaining every detail indefinitely. The period can differ for account details, receipt references and support messages. Contact us through account support if you need the reason for a specific record.

Yes. Privacy Policy explains that cookies or similar storage may preserve a session, remember a setting or help identify a technical problem. You can adjust browser controls, but doing so may sign you out or require another login before the account path is available.

Use the account support area and describe the Privacy Policy question with the smallest useful set of details. For a wallet matter, include the DANA, OVO, GoPay or QRIS reference. For a security matter, mention the unfamiliar login time and avoid sending passwords or codes.