Reference

elegantotologin Privacy Policy

The elegantotologin Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Account clarityWallet recordsCookie choicesPhone verification
elegantotologin elegantotologin Privacy Policy
CONTACT YOUR WAY

Where Privacy Questions Go

A clear contact path helps when you want to understand a record, correct an account detail or ask why a cookie appeared.

Account contact Use the support contact route from your account when you need a copy, correction…
Wallet evidence For a DANA, OVO, GoPay or QRIS question, provide the date, amount reference and…
Access concerns If a sign-in alert, phone verification request or device change looks unfamiliar, tell us…
DATA HANDLING

What Privacy Controls Cover

Our Privacy Policy is designed around the records that arise during an actual account journey, from phone verification to a mobile lobby session and a wallet status check.

Account details

We use your submitted name, phone number and login details to create and maintain the account you asked for.

Device signals

A mobile browser may provide session data, device type, language setting, approximate region and security events.

Cookie settings

Cookies can remember a session, support account access and show whether a page loads correctly.

Wallet references

A payment event can contain a DANA, OVO, GoPay or QRIS reference, or a bank transfer and virtual account status.

Retention choices

We keep account, security and transaction records for as long as needed for the stated service purpose, dispute handling or…

Change requests

You may ask us to correct inaccurate details, provide a copy, explain a use or remove data where no legal…

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened or when a wallet record needs checking. We explain what elegantotologin receives, how the data connects to phone verification and device access, and which route you can use for a request. For every access or eligibility question, the position depends on local law. Keep your account email available when contacting us so we can protect the details attached to your account.

It covers account details, phone verification, device and browser signals, cookies, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, request handling and the reasons we may need to confirm account ownership.

We use your phone number to create the requested account path, send or confirm an access check and help identify an unfamiliar login. Phone verification can be required before private account details are discussed. We do not use it as a reason to request your wallet PIN.

No. Our Privacy Policy concerns the payment reference and status needed to match an account event, not your DANA password, QRIS secret or wallet login. If you ask about a receipt, give us the visible reference and date so we can investigate without collecting confidential wallet credentials.

We may receive device type, browser details, language setting, session identifiers, approximate region and security events connected with access. This helps us keep a mobile session working and identify unusual sign-ins. We do not need access to private photos, messages or unrelated files on your device.

Contact us through the account support route and describe whether you want a copy, correction, explanation or removal request. Use the email attached to your account where possible. We may confirm your phone or account details first, then explain what we can change and what must remain.

We retain each category for the period needed for account operation, security checks, payment questions, dispute handling or applicable legal duties. When that purpose ends, we remove, aggregate or restrict the record where practical. Support can explain the relevant retention reason for a specific account detail.

You can adjust cookie choices in your browser, including on an Indonesian mobile device. Required session cookies may still be needed for account access, and refusing them can sign you out or remove saved preferences. We use non-essential cookie data only for the purposes described in this Privacy Policy.