Reference

Open indodepo Privacy Policy Before Account Access

Our indodepo Privacy Policy explains what account details we collect, why we use them, and how you can ask for changes before opening access.

Clear data purposesWallet record contextAccount request path
indodepo Open indodepo Privacy Policy Before Account Access
CONTACT YOUR WAY

Browse Support Paths For Privacy Requests

A privacy question should have a clear route, especially when it concerns a phone number, wallet reference or login record.

Account data request Ask us to explain, correct or remove a detail connected with your account. Include the contact route you used and the account step involved, such as phone verification, so we can locate the request without asking for unrelated wallet details.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the payment date and visible reference through our support route. We use that context to check the record while limiting the request to the transaction detail you identify.
Cookie or device help Tell us whether you are using a mobile browser or desktop browser when asking about cookies, login sessions or device data. That detail helps us explain the relevant setting and separate browser storage from account records.
DATA HANDLING

Switch Through Your Privacy Controls

Privacy depends on practical handling, not just wording on a page. We separate account details from payment references where our operating process allows, use access checks before discussing account records, and keep…

Account details

We may use your submitted contact details to create and maintain your account, complete phone verification and respond to account requests. We do not need unrelated wallet details to handle a basic request about your profile data.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us match a payment status. We handle that reference for the stated account process rather than treating it as a broad profile record.

Cookies

Cookies can keep a browser setting or session working while you move from login to the lobby. You can manage browser storage through your device settings, although removing it may require another login or reset selected preferences.

Account security

Phone verification and session checks help us distinguish an account request from an unknown login. Never send a full password through support. If a login record looks wrong, tell us the device type and approximate access time.

Data retention

We keep records only as long as needed for the purpose described in the Privacy Policy, account protection or a legal requirement. A request to delete data may be limited where a record must remain for one of those reasons.

Policy changes

When this Privacy Policy changes, we update the page so you can compare the current wording with your next account visit. For a question about a new clause, contact us and identify the section or date you saw.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions that matter before you open an indodepo account: what we collect, how payment references fit into the record, and how to request access or correction. We keep the answers practical for Indonesian account use, including mobile browsers, phone verification and local wallets. If your situation is not covered, contact us with the smallest useful detail and we will route the question to the appropriate support path.

It covers account details, phone verification, device and browser data, cookies, payment references and support requests. It also explains why we use each category, how retention works, and how you can ask for access, correction or deletion where local law permits.

Phone verification helps connect an account request with the person trying to access it and supports account security. We may use the related contact detail for that stated purpose, while a question about another record can be sent through the privacy support route.

Yes. The Privacy Policy covers operational references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer or virtual account steps. We use those references to check a payment status or account request, not as permission for unrelated use.

You can contact us to ask what account data we hold and how it is used. Include the account contact route and the specific category you want checked. We may need an access check before discussing records linked to your account.

Send a correction request through the site contact route and identify the inaccurate field, such as a contact detail or payment reference. We will assess the request against the account record and may ask for verification before changing it.

Use the privacy contact path and state which data you want removed. We assess deletion requests against account operation, security and legal retention needs, so some records may need to remain where local law requires them.

Yes. The Privacy Policy applies when you access the account on a mobile browser or desktop browser. Cookies and device details may differ by browser settings, while account records such as phone verification remain connected to the account process.