Reference

Open to338 Privacy Policy Clearly

to338 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesSecurity checks
to338 Open to338 Privacy Policy Clearly
REQUEST A RESPONSE

Choose Your Privacy Contact Route

A clear contact path helps when your Privacy Policy question involves account access, a wallet receipt or a device session. We ask you to contact us from the email or phone details attached to your account where possible, because that lets us compare the request with the correct account record. If you are in Surabaya or another Indonesian location, the same route applies; access depends on local law. Include the subject of your request and the account step where the issue appeared, without sending a password or wallet PIN.

Team online

Account request

Use our account support route when you want to ask what personal data is linked to your profile, correct a phone detail, or request access to eligible records. We may ask for phone verification before discussing account-specific data, so another person cannot obtain your account details.

Wallet record

For a Privacy Policy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, send the receipt reference and approximate account step through support. Do not include your wallet PIN. We use the reference to locate the relevant record and explain its handling.

Security concern

If an unfamiliar device session or login detail appears, contact support through the account help route and change your password from the account settings path. We can review the access record after verifying you, while you should avoid sharing one-time codes or full payment credentials.

HANDLING THE DETAILS

Explore What Our Privacy Policy Covers

We handle Privacy Policy requests as account matters rather than treating them as general lobby questions.

Account details

When you open an account, we use the details needed to create and maintain your profile and to complete the…

Device sessions

A phone or desktop browser can create session and security records when you sign in.

Cookie choices

Cookies can remember session state and help pages load correctly after login.

Wallet references

DANA, OVO, GoPay and QRIS activity can create references used to match a cashier step, receipt or status question with…

Retention period

We keep personal data only while it supports the account, security review, payment reconciliation, dispute handling or a legal duty…

Change requests

You can ask us to access, correct or remove eligible personal data, or ask why a particular record is used.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and access questions we hear most often from Indonesia. They cover what happens at registration, how wallet references and device data are used, and how to request a change. If your situation is different, contact us through the route described above and avoid sending passwords, PINs or one-time codes.

The to338 Privacy Policy covers account details, phone verification, login and device session signals, cookies, lobby activity, support messages and payment references. It explains why we handle each category, how retention works, and how you can ask for access, correction or an eligible removal where local law permits.

We collect the details needed to create your account and record the phone verification step before access. Sign-in and device session data may also be created as you use the account. We do not ask you to place a password, wallet PIN or one-time code in a support message.

We use payment references from DANA, OVO, GoPay and QRIS to match a cashier action, receipt or status request with the correct account. Those references help us investigate a payment question; they are not a reason to use unrelated profile data. Bank transfer and virtual account references follow the same purpose.

Yes. Contact support from the email or phone route attached to your account and state whether you want access, correction or removal of eligible data. We verify account ownership before replying. Some records may need to remain for security, dispute handling or legal duties where local law permits.

Cookies can keep a mobile session working after login and help us recognise the current account path. You can limit or clear them through your browser controls, but that may sign you out or affect session functions. The policy explains the purpose of cookies and the practical effect of changing them.

Change your password from account settings, then contact support with the approximate time and device detail if available. Do not send a one-time code, wallet PIN or full payment credential. We verify you before discussing account records and can review the session through the account security route.

Use our account support route for questions about personal data, cookies, device sessions, phone verification or wallet references. Include the account step and request type, but leave out passwords and PINs. We use your verified account contact details to locate the request and respond according to local law.