Reference

Privacy Policy For Your stm303 Account

Our Privacy Policy explains how we collect, use and protect the account, wallet and device data you provide when you open an stm303 account.

Account dataWallet recordsDevice accessPolicy requests
stm303 Privacy Policy For Your stm303 Account
HELP WITH YOUR DATA

Where To Ask About Privacy Policy

A direct support route helps when your Privacy Policy question concerns an account step, wallet record or device login.

Account access Use the account support channel when your phone verification, login record or device access…
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference through…
Policy requests Ask us to view, correct or remove eligible account data through the same private…
ACCOUNT DATA CARE

What We Handle And Why

Privacy Policy choices are easier to understand when each data use has a clear operational reason.

Account creation

When you open an account, we collect the contact details and phone verification result needed to create the login path.

Payment matching

A DANA, OVO, GoPay or QRIS payment can create a reference, amount and status record linked to your account.

Device signals

The mobile browser or desktop session may provide device and login signals used to spot an unusual access attempt.

Cookie choices

Cookies can keep your session active, remember selected settings and help us understand whether a page request worked.

Retention period

We keep account, payment and security records only while they serve account operation, dispute handling, fraud checks or a legal…

Change requests

Contact us if your phone detail is wrong, your account data needs correction or you want to ask about deletion.

Privacy Policy Answers For stm303

These Privacy Policy answers cover the searches we hear most often before an account is opened. They focus on account data, Indonesian wallet records, cookies, access requests and the checks we use to protect your details. If your situation is different, contact us with a focused question rather than sending more personal data than needed.

The stm303 Privacy Policy covers data connected with your account, phone verification, login activity, device signals, cookies and payment references. It also explains retention, security handling, correction requests, deletion questions and the private support path for asking about your records.

We use phone verification to create a clear account path, help prevent mistaken access and confirm that a Privacy Policy request comes from the account holder. The result is connected to account security and support checks rather than unrelated content on your device.

Yes. When you use DANA or QRIS, we may keep the payment reference, status and account match needed to confirm the transaction or answer a receipt question. We do not need unrelated wallet content, and you should hide extra details when contacting support.

Send a private support request that names the account detail you want to see, such as phone verification, login events or a GoPay payment reference. We may ask you to confirm account ownership before explaining what can be supplied under the Privacy Policy.

You can ask us to correct inaccurate account data or discuss removal where local law permits. We first confirm the request concerns your account, then explain whether a record can be changed, removed or retained for security, payment disputes or a legal duty.

Cookies may keep your session active, remember settings and show whether a page request completed. Browser controls let you block or clear them, but some account functions may require another login. The Privacy Policy explains these uses without asking for unrelated device files.

Use our private support path and state whether your question concerns account access, a wallet receipt, cookies, retention or a data change. Include only the minimum locator needed, such as your registered phone detail, and wait for our identity-check instructions.