Reference

bimaspin Legal: account, data and access terms

bimaspin sets out the Legal basis for account access, data handling and payment records in one place, so you can check the conditions before opening an account.

Account conditionsData requestsLocal-law access
bimaspin bimaspin Legal: account, data and access terms
CONTACT ROUTES

Get Legal help through your account path

A clear contact route matters when a Legal question affects login, identity details or a payment record.

Account access If phone verification or login blocks access, use the account help route displayed after login and state which Legal condition you need clarified. Do not send a password in your message.
Payment records For DANA, OVO, GoPay or QRIS questions, include the receipt, date and transaction reference. Our support path can then connect the payment status with the correct account record.
Policy questions When you need a policy explanation or want to question an account decision, send the relevant section and your requested outcome through the contact route shown in your account.
DATA PRACTICE

How we handle Legal data requests

Legal work depends on accurate records and a clear way to request changes. We use account details, phone verification results and payment references only for the operational purposes explained in the applicable…

Data collection

We may hold account identifiers, phone verification details and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity when the policy requires an account record.

Cookie choices

Cookies can keep sign-in state and page preferences on your browser. Review your browser controls before continuing if you want to restrict or remove stored cookie data.

Account security

Use your own phone and keep login details private. We do not need your password when you ask for Legal help, and you should verify the account route before sharing a document.

Record retention

Account and payment records may remain available for the period required by our operating policy or applicable law. A deletion request does not automatically remove records we must retain.

Correction requests

To request a change, identify the field that is wrong, explain the correction and provide a matching account detail. We may ask for phone verification before applying an update.

Contact ownership

Send data and Legal requests through the support route displayed in your account. Include one clear question, the relevant reference and a safe reply path so we can respond accurately.

Legal answers for bimaspin accounts

These Legal answers address the questions you may have before opening an account or asking us to change an existing record. They cover local access, identity checks, payment references, cookies and contact steps. If your situation is not listed, use the account support route and quote the policy section that concerns you.

The bimaspin Legal page covers account access, phone verification, data handling, cookies, payment records, policy changes and requests to correct or remove information where applicable.

Yes. Access or eligibility depends on local law. Check your local position before opening an account, and use the service only where local law permits.

Phone verification helps connect an account to the correct contact detail before access. It may also be needed when you request a Legal change, account correction or payment-record clarification.

DANA and QRIS references may be kept with the related account record so we can check payment status. Keep your receipt and transaction reference when contacting support about a mismatch.

Yes, send the requested correction through the account support route. Name the field, explain the change and provide matching account details; phone verification may be requested before an update.

Cookies may preserve sign-in state and browser preferences. You can adjust cookie controls in your browser, although restricting them may affect account access or page settings.

Use the support route displayed inside your account and quote the relevant policy section. Include your account identifier and a concise question, but never include your password.