How local law shapes access
Access here depends on local law, and we keep it open only where local law permits. When you send a request, we first match the account name, the registered email, and the last device used, then we log the channel, time, and outcome so the file
-
1
stays traceable. Payment rails such as DANA, OVO, GoPay, and QRIS appear only as account references; we use them to confirm the wallet trace behind a request, not as a shortcut around the profile check. If you ask for a correction, closure, or copy of stored
-
2
details, we handle it through the same queue and keep the result attached to your account history. When retention is still required, we keep the minimum file needed for audit, dispute handling, or legal duty, then remove or archive the rest. If a request cannot be
-
3
completed because your region is restricted, we tell you why and stop there.
Service availability depends on jurisdiction. Users are responsible for checking local law before access.