Reference

garudajitu Privacy Policy Explained

Our Privacy Policy explains how garudajitu handles the details you provide when opening an account, checking wallet status or contacting support.

Clear data purposesWallet record contextAccount access stepsPrivacy contact route
garudajitu garudajitu Privacy Policy Explained
PRIVACY HELP DESK

Privacy Questions Near Your Account

A clear support path helps when your account details, phone verification or wallet reference needs attention. We ask you to contact us from the signed-in account where possible, because that lets us compare the request with the correct record without asking you to post private details in an open channel. For access, use the route that applies to your account and local eligibility.

Team online

Account request

Send a Privacy Policy question from your account support route. Include the email or phone linked to the account, but do not send a password, wallet PIN or full payment credentials.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the date and reference fragment through support. We use those details to locate the relevant record safely.

Access correction

For a name, phone or contact correction, explain the requested change after signing in. We may ask for an account step that confirms you control the record before updating it.

DATA HANDLING PRACTICE

How We Protect Your Account Data

Privacy depends on practical account habits, not broad promises. We separate sign-in details from routine service records, limit requests to the details needed for a specific case and use account checks before…

Account details

We use the contact details you submit for account access, phone verification, service messages and support replies. Keeping your phone number current helps us identify the correct account when you request a change.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us reconcile an account request. We do not need your wallet PIN or full banking password for that check.

Cookies and browser

Cookies may keep a session active or remember basic site preferences. On a shared device, sign out and remove stored site data through your browser settings after leaving the account.

Account security

Phone verification before account access helps connect a request to the account holder. Never share a password or verification code with another person, including someone claiming to speak for support.

Retention period

We keep account, support and transaction references only as long as needed for the stated service, security checks, dispute handling or legal duties. Retention can differ by record type and local law.

Changes and requests

To ask for access, correction or clarification, contact us through the signed-in account support route. We may confirm your identity first, then explain what can be changed under applicable local requirements.

Privacy Policy Questions From Indonesia

These answers address the account and payment-data questions we expect you to ask before opening an account. They cover what we collect, why wallet references appear, how browser storage works and how you can contact us. Where access or a request is restricted, the result depends on local law and the details connected to your account.

It covers account details, phone verification, sign-in activity, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

A wallet or bank reference helps us match a payment-status question to the correct account. We use the reference for reconciliation and support checks, not as a request for your PIN or password.

Contact us through the support route inside your signed-in account and state that you want a data access request. We may confirm your phone or account details before responding.

Yes, send the requested correction through account support after signing in. We may ask for a verification step to confirm control of the account before changing contact or identity details.

Cookies can maintain a browser session and store basic preferences on mobile or desktop. If you share a device, sign out and remove site data through the browser settings.

Retention depends on the record, its service purpose, security needs, dispute handling and legal duties. We retain transaction references only for the period needed under the applicable requirements.

Yes. Use the account support route for access, correction or clarification requests. If you cannot sign in, provide only the minimum account detail needed to locate the request safely.