Reference

Open susu4d Privacy Policy for Your Account

Our Privacy Policy explains how we collect and use details linked to your susu4d account, from phone verification before access to wallet records for DANA and QRIS.

Account dataWallet recordsCookie choicesRequest access

Browse Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

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

This Privacy Policy sets out what we collect when you create an account, complete phone verification, sign in from a mobile browser, or contact support about a wallet status. We may handle account identifiers, device signals, login records, payment references and messages needed to check a

1
DANA, OVO, GoPay or QRIS transaction. We use these details to provide account access, investigate receipt mismatches, protect the account from unauthorised activity and meet applicable legal duties. We do not treat a payment name alone as a full identity record; the transaction reference and account
2
details are considered together when a status check is requested. We retain records only for operational, security or legal reasons described here. Access to susu4d depends on local law, and this policy applies where local law permits. If a local rule gives you additional rights, we
3
will follow that rule for the relevant request.

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

CONTACT ROUTES

Reach Support About Privacy Policy Requests

A clear contact route helps when you need to ask about a Privacy Policy record, account detail or payment reference. Use the support link on susu4d.

DATA PRACTICES

Explore How We Handle Privacy Policy Data

We keep this policy practical by linking each data use to an account action, such as phone verification, a wallet status check or a security review of a…

Collection at login

When you sign in, we can record the account identifier, login time, browser type and basic device signals.

Phone verification

Phone verification comes before account access where required by our account flow.

Cookies and sessions

Cookies can keep a browser session working and help us remember security choices.

Payment references

A DANA, OVO, GoPay or QRIS reference may be stored with account and status details so we can match a…

Security controls

We limit account-data access to operational purposes, use verification before discussing private records and examine unusual sign-in details.

Retention and changes

We retain records for the period needed for account operation, security checks or legal duties.

Browse susu4d Privacy Policy Questions

These Privacy Policy answers focus on the questions we expect Indonesian account holders to ask before completing account access. They explain the data connected with phone verification, browser sessions and local wallet references, while keeping the request path clear when you need a record changed or checked.

It covers account details, phone verification, browser and device signals, cookies, support messages, payment references and retention. It also explains how to request access, correction or deletion assessment where local law permits.

We use the phone number for the account-access step and to match the verification message with your account. This helps protect sign-in activity, and we do not ask you to disclose a one-time code to support.

Yes. The policy includes DANA, OVO, GoPay and QRIS references connected with your account. We use a payment reference, date and account details to check status without requesting your wallet password.

Use the support link on susu4d.club and state that you are making a Privacy Policy access request. Include your account identifier and a reachable contact route; we may verify ownership before releasing records.

Yes. Send the support team the field you believe is incorrect and the corrected detail. We may request account verification, then assess the change against security needs and applicable local law.

We keep records while needed for account operation, security investigation or legal duties. When you ask about deletion, we assess the specific record, its purpose and any retention rule that applies.

Contact support through the account path on susu4d.club and describe the device, login time or session you do not recognise. Do not send your password or one-time code while we verify ownership.

Open susu4d Privacy Policy for Your Account

Reach Support About Privacy Policy Requests

Explore How We Handle Privacy Policy Data

Collection at login

Phone verification

Cookies and sessions

Payment references

Security controls

Retention and changes

Browse susu4d Privacy Policy Questions

01 What does the susu4d Privacy Policy cover?

02 Why does susu4d need phone verification data?

03 Does the Privacy Policy include DANA and QRIS records?

04 How can I request my susu4d account data?

05 Can I ask susu4d to correct personal data?

06 How long does the Privacy Policy keep my data?

07 What should I do about an unfamiliar device record?

Related Pages