Reference

Privacy Policy for Your shop33 Account

Clear handling of your account details, wallet records and device activity is the purpose of the shop33 Privacy Policy.

Account clarityWallet recordsCookie choicesSecurity steps
shop33 Privacy Policy for Your shop33 Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support

A clear contact path matters when you want to ask about your Privacy Policy rights or an account record. We keep policy help close to the account and cashier paths so you can refer to the relevant wallet status, receipt or login event. Tell us what you want changed, accessed or clarified, and include the account detail needed to locate the request. We use the same policy process for questions raised from mobile or desktop.

Team online

Account request

Use the support path connected with your account when you want a copy of personal details, clarification about a login record or help checking whether a phone verification step was recorded. We may ask for account identifiers so we send the response to the right account holder.

Wallet query

For a question about DANA, OVO, GoPay or QRIS records, include the payment reference and approximate time shown in your account. Our support process can match the receipt or status check with the relevant account activity without asking you to resend unrelated personal details.

Policy correction

If a Privacy Policy detail appears inaccurate, contact us through the account support route and describe the correction clearly. We review the request against account records, may confirm your identity, and explain the result or any reason a record must remain for security or legal purposes.

SIX DATA PROMISES

What We Do With Your Data

The Privacy Policy is practical: it connects each data category with a reason we need it and a way you can ask about it.

Account details

We use the details you provide during account opening to create your profile, support sign-in and connect your requests with the correct account. Keep your contact details current so a privacy response or security message can reach you without confusion.

Device activity

When you move from login to the lobby on a phone or desktop, we may record device and access signals used to protect the account. These signals can help us investigate an unfamiliar session without treating normal changes between devices as a policy breach.

Cookie controls

Cookies can remember session settings and help us understand whether a page loads correctly. Your browser provides controls for removing or restricting them. Some account functions may not work as expected after those changes, and the Privacy Policy explains the purpose of each cookie category.

Payment records

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference may be retained to match a receipt, check wallet status and resolve an account question. We do not need unrelated payment details for a request, so share only the reference connected with the issue.

Security handling

We use account checks, phone verification and access controls to reduce the chance of another person receiving your data. Never send a password in a support message. If you notice an unfamiliar login, tell us through the account support path so we can review the event.

Retention and changes

We keep personal records only while they serve account, security, dispute or legal needs described in the policy. You can request access, correction or deletion where applicable. If a record must remain, we explain the reason and identify the part of your request we can address.

Privacy Policy Questions About shop33

These Privacy Policy answers cover the questions we expect before an Indonesian account holder opens an account or checks a wallet record. They explain the data involved, the available request path and the limits created by security or local law. If your situation is not listed, contact support with the smallest useful set of account details.

The shop33 Privacy Policy covers account details, phone verification, login and device activity, cookies, payment references and support requests. It also explains why we use those records, how we protect them, how long they may remain, and how you can ask for access or correction.

We may collect details you submit for an account, records created when you sign in, device signals, cookie data and payment references. A DANA, OVO, GoPay or QRIS receipt can be used to match wallet status, while unrelated payment details are not needed for that request.

Use the account support path and state that your request concerns the Privacy Policy. Ask for access to a specific category, such as login activity or a QRIS receipt record. We may confirm account ownership before sending details, so the response reaches the correct person.

Yes, you can ask us to correct inaccurate account details or explain why a record is wrong. Include the affected field and the account identifier through support. We compare the request with our records, apply the correction where appropriate, and tell you if verification is required.

Cookies can keep a session active, remember selected settings and show whether a page is functioning correctly. Your browser can restrict or remove them. The Privacy Policy describes their purposes, while account features may behave differently if you block cookies needed for sign-in.

We retain records for the account, security, dispute or legal purpose described in the Privacy Policy, rather than keeping every record without a reason. A wallet reference may remain while a receipt or status issue is being resolved. You can ask which retention purpose applies.

Yes. Access, eligibility and some data requests depend on local law. We assess your request against the applicable rules and our security process, then explain what we can provide, change or remove. Contact support if you need the policy applied to your specific account situation.