Reference

BOSKELINCI Privacy Policy for Your Account

The BOSKELINCI Privacy Policy shows what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
BOSKELINCI BOSKELINCI Privacy Policy for Your Account
CONTACT THE TEAM

Where Privacy Questions Go

A privacy question should have a clear route, especially when it concerns an account or wallet record.

Account support Open the account help path and describe the Privacy Policy request, such as access…
Wallet status For a DANA, OVO, GoPay or QRIS reference, share the receipt number and date…
Access concern If a phone change or sign-in check blocks your request, use the displayed support…
DATA HANDLING

Six Practical Privacy Commitments

The Privacy Policy is applied through ordinary account steps rather than hidden settings.

Account creation

When you open an account, we collect the contact details and verification data needed to create your access.

Device signals

A phone or desktop session may provide browser, device and sign-in details.

Cookies

Cookies can keep your selected session active and help us understand which policy page was opened.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity is handled through references and status details.

Retention period

We keep personal records only for the period needed for account operation, security checks, dispute handling or legal duties.

Change requests

To correct an account detail or ask about deletion, send the request through the signed-in support path.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the practical questions that arise before account access: the data we receive, the reason for collecting it, the way wallet references are handled and the steps for making a request. Read them alongside the full policy, then use the account support path if your situation involves a specific device, payment reference or correction.

It covers account details, sign-in and device signals, cookies, support messages, payment references and retention. It also explains your route to request access, correction or deletion where local law permits.

We use your contact detail to create account access, send necessary account messages and confirm a requested change. A verification step helps us avoid discussing personal records with the wrong person.

No. Our payment records use references, status, amount and time for matching. We do not ask for your DANA, OVO, GoPay or QRIS wallet password in support messages.

Use the signed-in account support path and state that you want an access request under the Privacy Policy. We may verify account ownership before explaining the available records and delivery method.

Yes, send a correction request through account support and identify the field that is inaccurate. We check the requested change, update eligible records and explain any detail that must remain unchanged.

Retention depends on the record type and the reason it was collected, including account operation, security, disputes or legal duties. Ask support about a specific category rather than a general estimate.

Cookies can retain a sign-in session and remember a policy-page choice, while device signals can help identify unusual access. You can clear cookies in your phone browser, though some account steps may then repeat.