LEGAL REFERENCE

How We Handle Your Account Data

This is the v87 com privacy policy — the part of our brand home where we explain, in plain language, what we collect when you open an account...

Account dataKYC recordsCookie controlsPayment metadataIndonesia scope
Account access Read FAQ
v87 com How We Handle Your Account Data

Our Privacy Posture and Your Rights

We collect what's needed to run your account — your name, contact details, device fingerprint and the transaction trail tied to DANA, OVO, GoPay or QRIS top-ups. Where local law permits in supported Indonesia regions, we retain verification documents for the period regulators require, then purge them on schedule. You can ask us to show you the file we hold on you,

correct anything stale, or close the account and have non-mandated records removed. We don't sell your data to third parties; we share only with payment processors and identity-check partners who help us keep your wallet safe. Cookies set by us track session state, not your wider browsing.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PLAYER SUPPORT

Privacy Contact Paths

Team online

Data Request Inbox

Email our privacy desk with the address tied to your account and we'll confirm receipt within one business day, then return your data file in a readable format shortly after.

Live Chat Privacy Queue

Open chat from the lobby footer and pick the privacy topic — the agent routes your question straight to a reviewer who can act on deletion or correction requests.

KYC Document Desk

For document-related concerns, our verification team handles uploads over an encrypted channel and confirms when files are stored or removed from our records.

TRUST MARKERS

How This Policy Is Maintained

Versioned Edits

Every change to this policy is logged with a date stamp at the foot of the page, so you can see when wording shifted and what the previous clause said before the edit landed.

Legal Review

Our in-house counsel signs off on each revision and runs an annual check against Indonesian data-handling expectations, so the text you read here matches what we actually do.

Security Owner

A named security lead owns the data-protection program, runs internal audits and signs the breach-response runbook we follow if anything ever touches your records.

Processor List

We keep a current list of the payment and identity vendors who touch your data, and we publish material additions in the change log below this policy.

Retention Schedule

Documents and logs follow a fixed retention clock; once the regulatory window closes, automated jobs remove them from active systems and from our backups on the next cycle.

Plain Indonesian English

We write this policy in the same en-ID voice as the rest of our brand home, so nothing important is buried in legalese you'd need a translator to unpack.

Consistency Across Our Policy Pages

Privacy vs Terms
This page covers data; our Terms cover account conduct. Where they touch — say, on KYC — both pages use the same wording so you don't get conflicting answers.
Privacy vs Cookies
Cookies get their own short notice, but the categories named here match the toggles in that banner exactly, with no hidden third group sitting outside either page.
Privacy vs KYC
Verification rules live in the KYC notice; this policy explains the storage side, and the two cross-reference the same retention window so there's no gap.
Privacy vs Payments
Payment pages list DANA, OVO, GoPay and QRIS flows; this policy explains what metadata those flows leave behind and who on our side can read it.
Privacy vs Promo Terms
Promotion terms reuse the contact channels named here, so a data question raised inside a promo dispute lands with the same privacy reviewer.
Privacy vs Closure
Account closure steps reference the deletion clause on this page word-for-word, including which records we're required to keep after you leave.
Privacy vs Complaints
Our complaints page points back here for the data-access route, keeping one canonical inbox rather than scattering privacy requests across multiple forms.
AT A GLANCE

What Shapes This Policy Page

Clause Index A sticky index sits on the left of the policy...
Change Log At the foot of the page we list every revision...
Plain-Language Boxes Each formal clause is followed by a short plain-language box...
Inline Definitions Terms like processor, controller and retention are defined inline the...
Request Buttons Action buttons for access, correction and deletion sit beside the...
Mobile Layout On phones the clause index becomes a collapsible drawer and...

Privacy Questions We Hear Often

We collect your name, date of birth, contact details, device identifiers and the payment reference tied to DANA, OVO, GoPay or QRIS. Anything beyond that is optional and clearly labelled at the point we ask for it.

We hold verification documents for the retention window Indonesian regulators expect of us. Once that window closes, automated cleanup jobs remove the files from active storage and from our backup cycle on the next pass.

Yes. Email the privacy inbox from the address on your account, and we'll confirm receipt within one business day, then return a readable export of the records we hold within the statutory response window.

We share data only with payment processors, identity-check partners and infrastructure vendors who help us run your account. We don't sell your information, and the current processor list is published alongside this policy.

On closure we remove records that aren't legally required to retain. Items tied to anti-fraud and tax obligations stay on file for the mandated period, then drop off the schedule like any other retention entry.

The cookie banner lets you accept, reject or customise non-essential categories. Session cookies needed to keep you signed in stay on by default; switching them off will prevent the lobby from holding your login between pages.

Start with the data request inbox or the privacy queue in live chat. If you'd prefer a written trail, the email route gives you a timestamped record and routes straight to our named privacy reviewer.