Reference

Open stek 88 Privacy Policy Clearly

Your account details, wallet records and device activity are handled under the stek 88 Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet record controlsPhone verification contextLocal-law access
stek 88 Open stek 88 Privacy Policy Clearly
PRIVACY SUPPORT

Contact Us About Privacy Questions

A clear contact path helps you resolve a privacy concern without repeating your account story across different teams.

Account data request Ask us to confirm which account details we hold, why they are used and whether a correction is needed. Include your registered phone number or account reference through the site support route, while leaving out wallet passwords and full payment credentials.
Wallet record check For a DANA, OVO, GoPay or QRIS question, send the payment date, selected rail and receipt reference. We use those fields to locate the relevant status without requesting your private wallet login details or asking you to share a security code.
Access and deletion If you want a copy, correction or removal request assessed, contact support from the account path where possible. We first verify the requester, then explain any record that must remain for security, payment reconciliation or a legal obligation.
DATA PRACTICES

Check Security Around Your Account

Privacy work is practical: we separate account identity, payment references and device signals so each is used for a defined purpose.

Account data

We use details such as your registered phone number and account activity to create access, verify ownership and investigate sign-in concerns. We do not describe these details as wallet credentials, and our support team can explain the purpose connected to a specific record.

Cookies and devices

Cookies and device signals can preserve preferences, help keep a session connected and flag unusual access. If you switch from a mobile browser to desktop, some settings may need to be confirmed again; your account remains tied to its verified access path.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may produce a reference, amount status and timestamp. We use these fields to match a receipt and resolve a wallet question, not to request your separate wallet password.

Account security

Phone verification is part of the account security process before access is completed. Keep your phone available, avoid sharing verification codes and contact us through the site support link if a sign-in or device check does not look like yours.

Retention choices

We retain records for the period needed for account security, payment matching, support history and applicable legal duties. A deletion request can be assessed through support, although some transaction or security records may need to remain for those defined purposes.

Policy changes

When this Privacy Policy changes, we place the revised wording on this page and identify the updated policy date where applicable. Check this page before using the account again, or contact support if a new passage affects a data request you already sent.

Find Privacy Policy Answers Before Access

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening an account with stek 88. We cover the data collected during phone verification, the way payment references are handled, cookie behaviour on mobile devices and the route for requesting access or correction. Eligibility depends on local law, so use the support path when your location or account status needs a direct check.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, payment references, support records, retention and requests to access or correct data. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be matched to your account.

Phone verification helps us confirm that the person completing account access controls the registered number. It can also help us investigate an unfamiliar sign-in. Do not share a verification code with anyone; use the site support route if the number or device shown is not yours.

Our Privacy Policy concerns payment references and status details used to match a receipt, not your separate DANA or QRIS wallet password. The same approach applies to OVO, GoPay, bank transfer and virtual account records. Never send a wallet password or security code to support.

Use the support link on the site and state whether you want access to a record or correction of an account detail. Provide your registered phone number or account reference so we can verify the requester. We may ask for additional proof before releasing or changing data.

Cookies and device signals may keep a session connected, remember preferences and help identify unusual access. Clearing them can require another sign-in or phone check when you return on mobile. Your browser controls remain available, while account security checks can still apply where local law permits.

We retain each record for the period needed for its stated purpose, such as account security, payment matching, support history or a legal duty. You can ask support about a particular record. Some transaction and security entries may remain after an account change request.

This page carries the current Privacy Policy wording, including any revised policy date shown with the text. If a change is unclear or affects a request you already made, contact us through the site support link and include the relevant section or account reference.