Reference

srikandi189 Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account, device and payment details you provide when using srikandi189.

Account dataWallet recordsCookie choicesAccess requests
srikandi189 srikandi189 Privacy Policy for Your Account
CONTACT PATHS

Three Ways To Ask About Privacy

A clear contact path matters when a privacy question affects your account or wallet record. We ask you to use the support route shown after login and include the account detail needed to locate your request without sending unnecessary personal data. For a receipt, device concern or access question, describe the exact step and payment rail so we can check the relevant record.

Team online

Account data request

Ask us to show the account details linked to your phone verification. We may request an account step to confirm that the request comes from you before releasing personal records.

Wallet record query

For DANA, OVO, GoPay or QRIS entries, send the transaction reference visible in your account. We use that reference to separate your payment record from another account.

Device access concern

Tell us when a login or cookie choice looks unfamiliar, including whether you used a mobile browser or desktop. We can review the related access record and explain the next account step.

HANDLING DETAILS

How We Handle Six Data Areas

We keep this policy practical by linking each data type to a real account action. A phone number supports verification, a device record helps us investigate an unfamiliar login, and a payment…

Account details

We use your submitted contact and verification details to create, secure and locate your account. If a detail changes, request an update through support rather than sending a new copy through an unrelated channel.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include references, amounts and status timestamps. We use them to match a receipt with the correct account and resolve a query.

Cookies

Cookies can remember a session, language choice or device setting so the account path opens correctly. You can adjust cookie controls in your browser, although some login functions may then need another check.

Device signals

We may review browser, operating system and access-time signals when protecting an account or diagnosing a stalled login. These signals help us compare a new mobile path with your prior account activity.

Retention period

We keep personal records for the period needed to operate the account, resolve payment questions or meet a legal request. When that purpose ends, we delete or anonymise the relevant record.

Changes and rights

You may ask what data we hold, request a correction, question its use or ask whether deletion is available. We will explain any identity check and any record that must remain for a stated legal reason.

Privacy Policy Questions For Your Account

These answers address the searches we hear most often about the Privacy Policy, from wallet records to cookies and account access. If your situation involves a specific DANA receipt, mobile device or phone verification step, include that detail in your support request so we can focus on the correct record.

It covers account details, phone verification, device signals, cookies, access activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use phone verification to confirm the account holder during access and privacy requests. If you ask for account data or a correction, this step helps us avoid sending details to the wrong person.

Yes. The Privacy Policy covers references, status details and related account records for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity.

Use the support route shown after login and ask for an account data request. Include your verified account detail, but do not send extra identity documents unless our support response specifically asks for them.

Yes. Tell us which field is incorrect and provide the account step needed to confirm ownership. We will explain the correction process and update the relevant record when verification is complete.

Cookies can retain a session or device setting, while browser controls let you adjust them. Clearing cookies may sign you out and require phone verification again during your next account access.

We retain payment references only as long as needed for account operation, receipt checks, disputes or legal needs. After that purpose ends, the record is deleted or anonymised where appropriate.