Reference

Privacy Policy for Your fantech gue314d Account

The fantech gue314d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
fantech gue314d Privacy Policy for Your fantech gue314d Account
CONTACT YOUR WAY

Get Help With a Privacy Policy Request

A clear contact path matters when you need to ask about your account data or a wallet record. We ask you to use the support route connected with your fantech gue314d account and include the email or phone detail used during account access. That lets us locate the correct record without exposing another person’s information. If your request concerns a QRIS receipt, DANA status or device session, mention that specific detail so our team can direct it to the right check.

Team online

Account contact

Send a Privacy Policy question through the account support route and identify the email or phone detail attached to your login. We use that information to match the request to the correct account before discussing personal data or changing a stored detail.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the wallet name and the relevant account activity. We can then separate a privacy request from a cashier-status question and avoid sending payment details to an unverified contact.

Device access

If you see a session you do not recognise on your phone or desktop browser, tell us the device path and approximate sign-in time. We use those clues to review account access and help protect the personal data connected with that session.

DATA HANDLING DETAILS

What We Do With Your Account Data

We keep this Privacy Policy practical by connecting each data use to an account task you can recognise.

Account details

We may handle your name, email address, phone detail and verification status to create and protect your account. The account step is tied to your sign-in path, so we can confirm which profile should receive a response when you ask about stored data.

Wallet references

DANA, OVO, GoPay and QRIS activity can create records such as a payment reference, status and time. We use these details to match a cashier event to your account, not to treat a wallet label as permission to access unrelated personal data.

Cookies and sessions

Cookies can preserve your sign-in state and remember a privacy choice while you move between the account page and mobile lobby. Browser and session signals also help us investigate access problems without requiring you to repeat every account step.

Account security

We use sign-in records, device information and verification steps to identify unusual account access. If a phone or desktop session looks unfamiliar, contact support with the approximate time and device path so we can assess the event tied to your profile.

Retention approach

We retain personal data only as long as it supports the account relationship, security checks, payment reconciliation or a legal need. When a record no longer serves one of those purposes, our handling follows the deletion or anonymisation process available for that record.

Your privacy request

You can ask for access to your data, correction of an inaccurate detail, clarification of a wallet record or a deletion assessment. Include your account contact detail and the request type; we may need to verify ownership before sharing or changing information.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and payment records you are most likely to ask about before opening or using fantech gue314d. We explain the practical route for each request, including what detail to send and why an ownership check may be needed. Where service eligibility is discussed, it depends on local law.

The Privacy Policy covers account details, verification information, sign-in activity, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use those records and how you can ask about, correct or assess them.

We may collect the contact detail you submit, account credentials or verification status, sign-in records and device information used during access. We use these details to create the correct profile, protect the login and respond to a Privacy Policy request from the account holder.

Yes. Our Privacy Policy covers payment references and status details associated with QRIS, DANA, OVO and GoPay, as well as bank transfer and virtual account activity. These records help us match a cashier event to your account and handle a question about its status or history.

Use the account support route and state that you want a copy or description of your stored data. Include the email or phone detail connected with your login and identify any specific record, such as a device session or QRIS reference. We may verify ownership first.

You can request a correction when an account contact detail, verification item or other personal record is inaccurate. Send the request through support from the connected account route, describe the incorrect value and provide the updated detail. We review ownership before applying a change.

Retention depends on the purpose of the record. We may keep account, security and payment-reconciliation data while the account relationship, an access investigation or a legal need remains. When that purpose ends, the record is handled through the applicable deletion or anonymisation process.

Contact support with the device type, whether you used the mobile lobby or desktop browser, and the approximate sign-in time. Do not send a password. We use those details to locate the session, assess the account-access event and advise on the next security step.