Reference

Privacy Policy For Your ayulogin Account

Our Privacy Policy gives you a clear view of how we handle phone verification, login records, wallet references and device details when you use ayulogin.

Phone verificationCookie choicesAccount controlsIndonesia access
ayulogin Privacy Policy For Your ayulogin Account
HELP WITH RECORDS

Get Privacy Policy Help Through Your Account

A clear contact path matters when a Privacy Policy question concerns your phone number, a wallet reference or a device record. We route requests through the account help area so we can connect your message with the correct account details. Include the subject of your request and the relevant transaction reference, but never send a wallet PIN or password. If you are in Makassar or elsewhere in Indonesia, the same account path is used where local law permits.

Team online

Account help path

Open the help area after signing in and describe whether you need access, correction or deletion assistance. We may ask for the phone number linked to your account and a recent payment reference so we can check the request without exposing unrelated records.

Payment record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the receipt reference shown by your wallet or bank. We use that reference to locate the relevant record and explain its status through the account support path.

Security concern

If a login or device record looks unfamiliar, use account help and tell us the date, device type and action you noticed. Do not share your password or wallet PIN; we use account checks before discussing private records.

DATA HANDLING

What Our Privacy Policy Keeps Clear

We keep this Privacy Policy practical by connecting each data category to an account action you recognise.

Account details

We use your submitted phone number and account details to create, verify and maintain your account. Before discussing private records, we may match a request to the verified phone path. This keeps an account correction from being applied to the wrong person.

Device signals

When you sign in from a phone or desktop browser, we may record device type, browser details, approximate network data and login time. These signals help us investigate unusual access and are considered alongside your account activity rather than used as a public profile.

Cookies

Cookies help keep a sign-in session active and remember settings such as language or display preferences. You can manage cookies through your browser controls, although disabling some cookies may interrupt account access or require you to sign in again.

Payment references

We retain references, amounts, timestamps and status values needed to match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event. We do not need your wallet PIN for this check, and support should never ask you to send it.

Security checks

Phone verification, login signals and account history can be used together when we assess an access concern. If a request involves changing private details or discussing a receipt, we may ask for a matching account step before responding.

Retention and requests

We keep records only for the period needed for account operation, security checks, payment reconciliation and legal duties. You may request access, correction or deletion through account help; where local law permits, we explain any reason a record must remain.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the searches we receive most often before account creation. They explain what happens during phone verification, how wallet and device records are used, and how you can contact us about a correction or access request. The account help path remains the starting point for a private request.

The ayulogin Privacy Policy covers account details, phone verification, cookies, device and login signals, payment references, support records and retention. It explains why we use each category, how we protect account access and how you can request access, correction or deletion where local law permits.

Phone verification connects an account request to the number you submit and helps us reduce mistaken or unauthorised access. We may use that verified path before discussing private account or payment records. The applicable process depends on local law and the account details available.

Our Privacy Policy uses payment references and status details to match DANA, OVO, GoPay and QRIS activity, but you should not send a wallet PIN to support. Bank transfer and virtual account references may also be retained for reconciliation and account assistance.

Sign in, open the account help path and request access to your records. Include the phone number linked to the account and explain the data category you need. We may verify your identity before responding, and the response route depends on local law.

Yes. Use account help and identify the detail that needs correction, such as a phone number or account record. We may ask for a verification step and supporting context before changing it. Payment references are corrected only after the related record is checked.

We retain records for the period needed to operate your account, investigate security events, reconcile payments and meet applicable legal duties. When you ask about deletion, we check the record type first. Where local law permits, we explain what can be removed and why.

Cookies can keep your session active and remember settings while you move between pages on a phone or desktop browser. You can change browser cookie controls, but disabling required cookies may sign you out or prevent parts of account access from working.