Reference

spy77 Privacy Policy for Wallet and Account Data

Our Privacy Policy shows how spy77 handles your account details, device signals and wallet records when you use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity checks
spy77 spy77 Privacy Policy for Wallet and Account Data
CONTACT PATHS

Wallet Status Questions Reach Our Support Route

A clear support path matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account access Use the support route connected to your signed-in account when a Privacy Policy question…
Payment receipt For DANA, OVO, GoPay or QRIS questions, include the receipt reference and payment rail.
Policy request Ask us about data access, deletion or consent changes through the account support path.
HANDLING DETAILS

Mobile Legends Device Data Under spy77

We keep this Privacy Policy practical by describing the records created during ordinary account use, including mobile access around Mobile Legends and wallet status checks.

Account data

We may handle your name, contact details, account identifiers and verification responses so we can create, secure and maintain your account. We do not need unrelated personal details for these account steps.

Device signals

When you use a phone or desktop, we may record browser type, device markers, session time and security events. These signals help us detect unusual access without reading unrelated device content.

Cookies

Cookies and similar storage can keep your session active, remember selected settings and help us understand basic page performance. Your browser controls can limit cookies, although some account functions may then need another sign-in.

Account security

Before we discuss account records or change important details, we may ask for a phone verification step or other ownership check. This helps prevent another person from using your support request.

Retention periods

We keep account, payment and security records only while they serve the stated purpose or a legal duty. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Your requests

You can ask what personal data we hold, request a correction or ask about deletion and consent choices through our support route. We assess each request under applicable law and explain any necessary limit.

Privacy Policy Questions About DANA and Accounts

These Privacy Policy answers address the searches we expect before you open an account from Indonesia. We cover wallet records, device access, correction requests and the verification step used to protect your account. If your question is not listed, send it through the support path attached to your account.

Our Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests created through your account. It also explains retention, security checks and your available data requests.

Yes. The Privacy Policy covers payment references and wallet status connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records used to match an account.

We use device type, browser signals, session times and security events to protect account access, identify unusual sign-ins and keep a support response tied to the correct account. We do not need unrelated device content.

Send a data access request through the support route in your signed-in account. We may complete an ownership check before responding, then explain the records we can provide under applicable law.

Yes. Tell us which account detail is incorrect and provide the corrected version through support. We may ask for phone verification or another ownership check before changing records linked to your account.

We retain payment and account records while needed for the stated service purpose, security work or applicable legal duties. After that period, we remove them or separate them from direct identifiers.

The policy is available for you to read, while account access and eligibility depend on local law. If a local rule affects a request or account step, we will explain the relevant limit.