Reference

hollywings Privacy Policy Explained

hollywings Privacy Policy sets out how we collect, use and protect details connected with your account, mobile browser access and wallet activity.

Account dataWallet activityCookie choicesAccess requests
hollywings hollywings Privacy Policy Explained
DATA HELP PATH

Where To Ask About Your Privacy Policy

A clear support route helps when you want to ask what data we hold or why an account check appeared.

Account privacy request Ask through the account support path when you want access to personal data, a…
Wallet record question Tell us whether your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual…
Security concern If a sign-in or device event looks unfamiliar, contact support through your account path…
DATA PRACTICES

Inside Our Privacy Policy Process

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

Account details

We use the contact details and phone verification information you submit to create, secure and maintain your account.

Cookie controls

Cookies can keep your browser session connected and remember selected settings.

Device security

We may use device type, browser details and sign-in events to identify unusual access.

Payment references

A QRIS, wallet, bank-transfer or virtual-account reference can help us match an account request with its status.

Retention choices

We keep records only for the period needed for the stated account, security, service or legal purpose.

Change requests

Where local law permits, you can request access, correction or deletion of eligible personal data.

Privacy Policy Answers For hollywings

These Privacy Policy answers address the account and payment questions we expect you to ask before opening an account. They explain the practical route for checking data, changing details and raising a security concern. If your situation is not covered, use the support path shown in your account and identify the relevant device or payment reference without sharing secret credentials.

It covers account details, phone verification, browser and device signals, cookies, payment references, support requests, security events and retention. It explains how we use those records for account access and service activity where local law permits.

Phone verification helps connect an account to the contact detail you provide and supports safer account access. If you ask about the record, contact support using that same verified detail rather than sending a password or wallet PIN.

Yes. The policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions. We use those references to investigate account requests without requesting your private wallet credential.

Use the support path inside your account and ask for an access request. Include your verified phone or email detail, and describe the record you want checked, such as cookies, sign-in events or a QRIS payment reference.

Where local law permits, you can ask us to correct eligible account information. Send the request through account support, state what is wrong, and provide the updated detail. We may verify your identity before changing the record.

Retention varies by record type and the account, security, service or legal purpose involved. We do not promise one period for every record. Ask support to identify the category and explain the retention basis connected with your request.

Contact support through your account path and describe the device or browser event. Do not send a password, wallet PIN or full payment credential. We can use account security signals to assess the concern and explain the next step.