Reference

gendutwin Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a gendutwin account, verify your phone, browse on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice detailsCookie choices
gendutwin gendutwin Privacy Policy for Your Account
CONTACT DATA CARE

Get Privacy Help Beside Your Account Path

A clear contact route matters when you want to ask about personal data rather than a wallet status. Our support path lets you identify the account concerned, describe the request and attach only the receipt or screen detail needed to locate it. Keep your phone verification details private while contacting us. We can help you understand a record connected with DANA, QRIS or a mobile browser session without asking for a password.

Team online

Account data request

Use the support route linked to your account to ask what personal details are held, why they are used, and which verification step connects them to your profile.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the account identifier and transaction reference only; we use those details to locate status without requesting wallet credentials.

Device access concern

Tell us if a mobile browser session or phone verification looks unfamiliar. We can review the account path with you while keeping passwords and private wallet codes out of messages.

SECURITY AND RETENTION

What Your Privacy Policy Covers Daily

Privacy choices work best when they match the way an account is actually used. We separate account identifiers, payment references, device signals and cookie settings so a request can be directed to…

Account details

We may hold your account identifier, phone verification result and sign-in history to connect the right person with the right account path and investigate an unfamiliar access event.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match account activity with a receipt or status question without storing your wallet password.

Mobile browser signals

When you open the lobby on a phone, technical details such as browser type, session time and device signals may help us detect unusual access and keep the account path consistent.

Cookie controls

Cookies can support sign-in continuity and page settings. Your browser controls let you clear or restrict them, although some account steps may then need to be repeated.

Retention choices

We keep records for as long as needed for account security, transaction matching or legal duties. You can ask us to explain the reason a particular record remains stored.

Change or access request

Contact support with the account identifier and a clear request to access, correct or clarify your data. We may verify ownership before making a change or sharing a copy.

Privacy Policy Answers for gendutwin Accounts

These Privacy Policy answers address the practical searches you may make before opening an account or returning to the lobby. Each answer stays focused on personal data, wallet references, device access and contact steps. If your question concerns eligibility, remember that access depends on local law and is available where local law permits.

It covers account details, phone verification, wallet references, device signals, cookies, retention, security checks and requests to access or correct personal data connected with your account.

Yes. It explains that DANA, OVO, GoPay and QRIS references may be used to match an account action, receipt or status question without requesting your wallet password.

Phone verification helps connect account access with the correct person and can support an unusual-access check. We use the result for account security rather than asking you to share a password.

You can contact support with your account identifier and ask for access to the personal data connected with your profile. We may verify ownership before preparing or sharing a copy.

Send a clear correction request through the account support route. Include the affected detail and account identifier, but do not send wallet credentials; ownership checks may apply before changes are made.

Retention depends on the purpose of each record. Wallet and transfer references may remain for account security, transaction matching or legal duties, and support can explain why a record is still held.

Yes. Ask support which cookie setting or session detail concerns you, and use your browser controls to clear or restrict cookies. Some account steps may need to be repeated afterward.