Reference

Privacy Policy For Your interboss Account

Our Privacy Policy explains how we handle the details you provide when you open an interboss account, sign in from a phone, or use DANA, OVO, GoPay and…

Account dataWallet detailsCookie choicesSecurity checks
interboss Privacy Policy For Your interboss Account
HELP WITH YOUR DATA

Where To Ask About Privacy Policy

A clear contact route helps you resolve a data question without guessing which team to reach. We keep privacy requests close to the account and cashier paths, so you can identify the relevant sign-in, wallet or verification event. Include the email or phone detail tied to your account, the approximate date, and the request you want us to assess. Do not send a password, wallet PIN or full payment credentials. We may ask for an account check before discussing private records.

Team online

Account access

Use the support path beside the sign-in area when you need to ask how your account details are stored or why a phone verification step is required. We use the account identifier you provide to locate the correct record without asking you to share a password.

Wallet status

For a DANA, OVO, GoPay or QRIS privacy question, mention the payment rail and the status shown beside the cashier step. We can separate account records from provider-held transaction details and explain which party should receive the next request.

Change request

Ask through our account help route when a contact detail needs correction, a cookie choice needs clarification, or you want to understand retention. We may verify ownership first, then confirm what can be changed and what must remain for legal or security reasons.

CLEAR DATA PRACTICES

What We Do With Account Details

Privacy Policy controls the practical steps behind your account record, from the first phone check to a later request about stored data.

Account records

We may hold your contact details, phone verification result, sign-in history and account preferences so we can identify your account and address access questions. We do not need your password in a support message, and you should never include one when asking about the Privacy Policy.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may keep a reference, amount status and timing needed to match the account request. The payment provider may retain separate records under its own privacy terms.

Cookie controls

Cookies can remember a session preference and help us detect an unusual sign-in path. Your browser settings let you remove or restrict them, although changing cookie controls may require another sign-in or affect how account pages remember your choices.

Session security

A phone verification step, device signal and sign-in event can help us protect your account from access that does not match your normal pattern. If a check interrupts your session, use the account support path rather than sending sensitive credentials in a message.

Retention reasons

We keep records only for the period needed for account support, payment reconciliation, security checks and applicable legal duties. The period can differ by record type, so a request about deletion may require us to explain why one detail can change while another must remain.

Your requests

You can ask what account data we hold, request a correction, ask about processing or seek clarification about retention. Send the request through our support route with enough account detail for verification; access and eligibility still depend on local law.

Privacy Policy Answers For interboss

These Privacy Policy answers address the searches we expect before you open an account or complete a wallet step. We focus on the information you give us, the device signals created during sign-in, and the practical route for asking about a record. If your question concerns a payment provider’s own data, we will help identify the right boundary between our account record and that provider’s terms.

The interboss Privacy Policy covers account details, phone verification, sign-in activity, device and cookie signals, support requests, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. It also explains retention, security handling and ways to request clarification or correction.

Phone verification helps us connect an account to the contact detail you provide and identify unusual sign-in activity. We use the result for account access and security checks, not as a request for your password or wallet PIN. Access remains where local law permits.

It covers the account-side references we need to match a DANA or QRIS request, such as status and timing. DANA, QRIS and other payment providers may hold their own transaction records under separate terms. We can explain which record sits with us when you contact support.

Yes. Send a correction request through the account support route and identify the contact detail that needs attention. We may verify account ownership before making a change. If a record is required for security, payment reconciliation or legal duties, we will explain why it cannot be removed.

On a mobile browser, cookies may remember a session choice and support sign-in continuity, while device signals can help identify an unusual session. You can restrict or clear cookies in your browser settings. Doing so may require another phone verification step when you return.

Retention depends on the type of record and the reason it is needed. Account support, payment reconciliation, security checks and legal duties can each require different periods. Ask through our support path for a record-specific explanation; we will not promise deletion where a duty requires continued storage.

Use the support route beside the account or cashier area and state that your question concerns the Privacy Policy. Include your account contact detail, the relevant date and the request type, but never send a password, wallet PIN or full payment credentials. Eligibility and access depend on local law.