Reference

Your Privacy Policy Path at st799

st799 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
st799 Your Privacy Policy Path at st799
CONTACT PATH

Get Privacy Help Beside Your Account

A clear contact path helps when a Privacy Policy question is more specific than a page can answer.

Account request Ask us to confirm the personal details connected with your account, including the phone…
Wallet record For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference and…
Policy question Use our account contact route for questions about cookies, retention, data sharing or a…
DATA PRACTICE

How st799 Handles Your Privacy

We handle Privacy Policy matters through practical account controls rather than broad promises. Phone verification helps us distinguish an account holder from an unknown sign-in, while device and session records help us…

Account details

We collect details you provide during account creation and phone verification, then use them to maintain the profile you asked us to create. If a name, phone detail or other account field is wrong, contact us with the correction and the relevant account step.

Sign-in security

Sign-in events and device signals can help us identify an unusual access attempt or explain why a session stopped. Keep your password private and contact us if your device path looks unfamiliar. We may ask for verification before changing access details.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data in your account record. We use those references to check receipts and status, while avoiding requests for your full wallet password or unrelated financial details.

Cookies and devices

Cookies and device storage can remember settings, maintain a session and help us understand a failed account path. Your browser controls can limit cookies, although some account functions may then need another sign-in or may not retain your chosen settings.

Retention choices

We retain account, security and transaction records only for the operational, dispute and legal reasons connected with the service. Ask us about a particular record or deletion request; the result depends on the record type and applicable local law.

Request changes

You can ask for access to your personal data, correction of inaccurate details, or clarification of how a record is used. Send the request through the account contact route, identify the relevant profile or receipt, and we will check your identity first.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take before joining st799. They explain what happens around phone verification, mobile access, local wallet references, cookies and requests for your records. If your situation is different, use the contact path above and mention the exact account or payment step.

The st799 Privacy Policy covers details you provide for account creation and phone verification, plus sign-in, device and transaction references. We use them to maintain access, investigate unusual activity and answer account questions. You can ask which personal records are connected with your profile.

Yes. Privacy Policy coverage includes references created when you use DANA, OVO, GoPay or QRIS, such as a receipt detail, status record or account match. We use those references to check a payment path and do not need your wallet password for that request.

Your phone verification record helps us connect access to the right account, while device and session signals can help explain an unfamiliar sign-in or interrupted mobile path. These records support account security and service checks; contact us if a device entry appears incorrect.

You can contact us to request access to personal data connected with your account or to correct inaccurate details. Include your account identifier and the specific field or record. We may verify your identity before responding, and the available action depends on local law.

Cookies may keep a session active, remember settings and help us understand a failed account path. Your browser can restrict or remove them. If you do, some settings may not remain saved and you may need to complete phone verification or sign in again.

Retention depends on why a record exists, including account security, payment reconciliation, dispute handling and legal duties. We do not assign one period to every record. Ask us about a particular account, DANA receipt, QRIS reference or device event for a focused response.

You may ask us to delete or restrict a record through the account contact route. We first check the request and the record type because some account, security or transaction data may need to remain for legal or dispute reasons. The outcome depends on local law.