Reference

api33 Privacy Policy for Your Account

api33 Privacy Policy explains what we collect when you open an account, check wallet status, or use our Mobile App on your phone.

Account dataWallet recordsCookie choicesContact rights

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

api33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account opening, the phone verification used before account access, and technical records created while you move between the lobby and cashier. We may record payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account

1
activity so we can match a request to the correct account without storing wallet passwords. We also explain cookies, device signals, security checks, retention periods and requests to correct or remove eligible details. If you contact us from Jakarta or elsewhere in Indonesia, the same policy
2
route applies, subject to local requirements. Access and eligibility depends on local law, and the current policy text is the reference we use when handling your request.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Three Ways to Ask About Privacy

A clear contact path helps you resolve a data question without repeating your account story.

Policy contact route Send a Privacy Policy question through the contact path shown on this page. Include your account email and the specific data request so we can identify the correct record.

Wallet record check For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and approximate date. We can compare the account record without asking for your wallet password.

Account correction If your phone, email or verified account detail needs changing, ask through support before opening another account. We may request an account step to confirm that the request is yours.

HANDLING YOUR DETAILS

Six Practical Privacy Commitments

We keep the policy practical by describing the handling that takes place around an Indonesian account.

Collection purpose

We collect account details to create and protect your login, confirm phone ownership, and connect a cashier action with the right account. Each requested detail should have a stated operational reason.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a reference, amount and status. We use those fields for matching and support, rather than requesting wallet login details.

Cookie controls

Cookies can keep a selected language, maintain a session and help us detect unusual sign-in patterns. You can manage browser cookie choices, although changing them may affect the login path.

Device security

Your browser or Mobile App may send device and connection signals when you sign in. We use them to spot account misuse, investigate stalled access and protect the phone verification step.

Retention period

We retain account, security and payment-reference records only for the period needed for the stated purpose, account support and applicable obligations. Ask through the policy route for the period tied to your record.

Changes and requests

You can ask us to correct eligible account details, explain a data use or address a deletion request. We may verify your identity before changing records so another person cannot alter your account.

Privacy Policy Answers for api33

These Privacy Policy answers focus on the questions that arise before opening an account or checking a wallet record. We keep the wording direct, point you toward the relevant account step, and apply access wording based on local law. If your case involves a particular transaction, the policy contact route can match the reference to your account.

It covers account details, phone verification, cookies, device signals, payment references, retention and your request rights. It also explains how we handle support questions linked to DANA, OVO, GoPay or QRIS.

We use your phone number for account identification and the verification step before account access. This helps connect the correct person to the account and can assist when login details or wallet status need checking.

Yes. The policy covers QRIS, DANA, OVO and GoPay references associated with an account, along with bank transfer and virtual account status. We do not need your wallet password to check a reference.

Use the policy contact route and state which account detail is incorrect, such as your phone or email. We may ask for an account verification step before applying a correction.

Retention depends on the purpose of the record, including account security, payment matching and support. Ask us for the period connected to your account record through the policy contact route.

You may submit a deletion request through the policy contact route. We assess which details are eligible, explain any reason a record must remain, and verify the request before making changes.

The current Privacy Policy is available on this page for account questions and data requests. Access to api33 depends on local law, so read the policy before opening or using an account.

api33 Privacy Policy for Your Account

Three Ways to Ask About Privacy

Six Practical Privacy Commitments

Collection purpose

Payment references

Cookie controls

Device security

Retention period

Changes and requests

Privacy Policy Answers for api33

01 What does the api33 Privacy Policy cover?

02 Why does api33 need my phone number?

03 Does the Privacy Policy cover QRIS and wallet data?

04 How can I request a correction to my api33 data?

05 How long does api33 keep account records?

06 Can I ask api33 to remove my personal data?

07 Where can I read the current Privacy Policy?

Related Pages