Reference

Open ger4d Privacy Policy With Clarity

ger4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS payment steps.

Account detailsWallet referencesDevice access
ger4d Open ger4d Privacy Policy With Clarity
CONTACT PATHS

Switch To Direct Privacy Support

A clear contact route helps you ask about your personal data without explaining the same issue repeatedly. We connect privacy questions with the account details needed to locate a record, while avoiding requests for wallet passwords or full payment credentials. If you are in Denpasar or elsewhere in Indonesia, send your account identifier and the subject of your request through our available support channel. We may ask for a verification step before changing account data or discussing a private record.

Team online

Account message

Use the account support path for a privacy question linked to phone verification, login records or a profile correction. Include the email or phone reference on your account and describe the change you want. We check ownership before discussing private details or applying an update.

Payment query

For a DANA, OVO, GoPay or QRIS data question, send the transaction reference, date and payment status rather than a wallet password. Our support team can compare the reference with the account record and explain what is retained for payment matching.

Security concern

If you think someone accessed your account, contact us through the account support route and mention the device or sign-in time you do not recognise. We may pause sensitive changes while ownership is checked, helping protect profile and payment-linked records.

DATA PRACTICES

Browse Our Privacy Handling Steps

We keep the Privacy Policy practical by tying each data use to an account or security task. Phone verification helps us confirm account ownership; device signals help identify unusual sign-ins; and cookie…

Account collection

When you open an account, we may collect your contact details and verification status. We use these details to create the profile, send account messages and confirm that a privacy request comes from the person connected with the account.

Device signals

A mobile browser or desktop session can share technical signals such as browser type, session time and approximate network details. We use them to maintain sign-in security and investigate an unfamiliar access event, rather than to read unrelated files on your device.

Cookie choices

Cookies can keep a session active, remember a setting or show us which page path needs repair. You can adjust cookie controls in your browser, although restricting essential cookies may affect account access, payment status checks or the way the policy page loads.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, amount, timestamp and processing result. These details help us reconcile status questions while avoiding storage of your wallet password or unrelated wallet content.

Retention steps

We keep account, support and payment-linked records for as long as needed for the stated service, security checks or applicable legal duties. After that point, records are deleted, anonymised or restricted, subject to any period we must still observe.

Your requests

You can ask for access, correction, deletion or a copy of personal data by contacting support with your account identifier and request type. We may confirm ownership before responding, and where local law permits we explain any reason a record cannot be changed immediately.

Ask About ger4d Privacy Policy

These Privacy Policy answers address the account, device and payment questions we hear most often from people in Indonesia. They explain what to send, what we may verify and how the policy works alongside access conditions. If your situation is not listed, use the account support route with a short description and the relevant reference.

The ger4d Privacy Policy covers personal data connected with account creation, phone verification, sign-in activity, device signals, cookies, payment references and support messages. It also explains retention, security handling, correction requests and deletion requests for access where local law permits.

Phone verification helps us confirm account ownership and reduce mistaken or unauthorised changes. We may use the verification status when you request profile access, correct contact details or ask about a DANA, OVO, GoPay or QRIS payment record.

Yes. The Privacy Policy covers payment references, timestamps, amounts and processing states linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use these details to match status questions and do not need your wallet password.

Contact us through the account support path and request a personal data copy. Include your account identifier and the email or phone reference connected with it. We verify ownership before releasing private records and explain the response route where local law permits.

You can request a correction by naming the field that is wrong and supplying the accurate replacement. We may ask for phone verification or another ownership check before changing it. Payment records may need to remain unchanged when they document a completed reconciliation.

We retain payment-linked references only for the operational, security or legal period connected with the record. This can include a DANA, QRIS, bank transfer or virtual account status needed to resolve an account query. Afterward, we delete, anonymise or restrict it.

Send a Privacy Policy concern through our account support route with your account identifier, request type and relevant date. For an unfamiliar sign-in, include the device or session detail. Do not send wallet passwords; we verify ownership before discussing private records.