Reference

sabi4d Privacy Policy for Your Account

Our Privacy Policy shows how we handle the account, wallet, device and cookie data connected with your sabi4d access.

Account clarityWallet recordsDevice controlsCookie choices
sabi4d sabi4d Privacy Policy for Your Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact path matters when a Privacy Policy question concerns your own records. After login, use the support contact displayed in your account area and include the relevant account identifier, date…

Account record request Ask us to locate account data linked to your phone verification or sign-in record. Include the account identifier shown in your account area so we can direct the request correctly.
Wallet receipt query For a DANA, OVO, GoPay or QRIS receipt question, send the reference and date through the displayed support route. Keep wallet passwords and PINs out of your message.
Device access concern If a phone or browser you do not recognise appears in your access history, tell us through account support. We can explain the security record and the next account step.
DATA PRACTICES

Six Privacy Checks Behind Your Login

We handle this policy area through practical account controls rather than vague promises. A phone verification event helps connect access to the right account, while device and session records help us investigate…

Account data

We use your account identifier, phone verification result and sign-in events to provide access to your account area. These records also help us answer a request about the correct account.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status. We do not need your wallet PIN or banking password to check a receipt.

Browser cookies

Cookies can preserve sign-in preferences, session continuity and selected settings on your browser. You can manage cookie behaviour in your device or browser controls, though some account functions may change.

Device security

We may keep device type, browser details, session timing and security signals to identify unusual access. If you use a new phone, these records can help us review the sign-in event.

Retention period

We keep account, transaction and security records for the period needed for service operations, dispute handling, fraud prevention or legal duties. When a record is no longer needed, our process addresses its removal.

Change requests

You can ask about access, correction or removal of eligible personal data through the support contact shown after login. We may verify account ownership before changing or disclosing records.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers cover the account steps you are most likely to ask about before opening access. We keep the wording direct, including how payment references, cookies, devices, retention and data requests fit the sabi4d account path. Where a request depends on identity or local rules, we explain the next step through support.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages, wallet references and records needed for security, service operation or legal duties.

These payment names can appear in account and transaction records when you use a local wallet or QRIS. We use references to check status, not to request your private wallet PIN.

We use the verification result to connect access with the correct account and help investigate login questions. We may retain the event as part of account security and service records.

Yes. Contact us through the support route shown after login and describe the account record you want to access or correct. We may verify ownership before handling the request.

Cookies may preserve session continuity, sign-in preferences and browser settings. You can adjust them through your browser controls, although changing cookie settings may affect parts of account access.

We retain records for the time needed for service operation, receipt checks, dispute handling, security work or legal duties. Retention ends when the relevant need no longer applies.

Use the account support contact shown after login and mention the device, session timing and account identifier. Do not send your password, wallet PIN or banking credentials in the request.