Reference

Your Privacy Policy, Written For You

We keep your Privacy Policy choices tied to your account, device, and payment records so you know what we store and why.

DANAOVOGoPayQRIS
indobom88 Your Privacy Policy, Written For You
REQUEST CHANNELS

Where to Send Privacy Requests

If you want a copy of your records, a correction, or a removal request, send it through the account path we list in your dashboard, then follow up by live chat, email, or WhatsApp. We ask for your account email, phone number, and the latest payment reference so we can match the request safely. That process works the same on Android, iPhone, and desktop, and it keeps the thread tied to your own account.

Team online

Live Chat

Open chat from your signed-in account and tell us which record you want changed. We may ask for your account email and one recent DANA, OVO, GoPay, or QRIS reference before we act.

Email

Use email when you need a written trail for a correction or data copy request. Include the old detail, the new detail, and the device you used so we can match the record.

WhatsApp

Send a WhatsApp follow-up if you cannot stay in chat. We use it for request checks, document re-sends, and short privacy questions that need a quick reply today.

HANDLING PRACTICES

How We Handle Your Records

We keep the policy simple: collect only what is needed, use it for the request in front of us, and hold it only as long as the law or the service flow…

Account Data

We store the details you enter at sign-up, plus your contact fields and request history, so we can confirm ownership and answer follow-up questions without asking you to repeat everything.

Cookies

Cookies keep your session open, remember language settings, and reduce repeated checks on the same browser. You can clear them through your browser settings whenever you want, on any device.

Device Checks

We log device type, browser, IP address, and sign-in time. That lets us spot unusual access and ask for another verification step before any sensitive change is accepted.

Retention

We keep request files only while they are needed for service work, dispute handling, audits, or legal duties. After that, we remove or mask parts that are no longer needed.

Change Requests

To update a detail, open your profile and send the correction through live chat or email. Include the old and new values so we can process it without confusion.

Contact Trail

Every privacy thread stays attached to your account until the case is closed, so you do not need to restate the same facts each time you reply later.

Privacy Questions We Hear Most

These are the questions we see before account creation, after sign-in, and when you want a record changed. The same policy applies on Android, iPhone, and desktop, and the same request path works whether your payment rail is DANA, OVO, GoPay, or QRIS. If local law does not allow a request, we will say so clearly and tell you the valid next step.

We keep the details you enter, your login records, and payment references from DANA, OVO, GoPay, or QRIS when you use them. That helps us confirm requests, resolve mistakes, and keep your account history clear.

Yes. We use cookies and similar tools to keep you signed in, remember language settings, and reduce repeated checks on the same browser. You can clear them through your device settings whenever you want.

Yes. Open your profile, send the correction request through live chat or email, and include the old and new detail. We may ask for a quick verification step before we change anything.

We keep records only for as long as needed to run the service, settle a request, or meet a legal duty. After that period, we remove or mask the parts we no longer need.

Only staff who need the record for account checks, payment handling, or privacy requests can view it, and they do so under access controls. We do not open account files wider than needed.

Use live chat, email, or WhatsApp and mention that you want a privacy request. Send your account email and the latest transaction reference so we can match the thread quickly.

Yes. Where local law applies, it sets the access, retention, and release process. If a request is not allowed in your region, we will explain the reason and the next valid step.