LEGAL REFERENCE

How virus88 Handles Your Account Data

This page sets out how we collect, store and use the information tied to your virus88 account. We keep the language plain so you can scan it in...

Plain-language policyIndonesia-awareAccount-data focusedUpdated regularlyReader-friendly
Tour the Lobby Read FAQ
virus88 How virus88 Handles Your Account Data

Our Privacy Posture and Jurisdiction

We process your virus88 account data under the rules of the supported regions where you sign in from. That means name, contact details, device fingerprints, session logs and payment references are handled only for purposes tied to running your account — verification, balance movement, dispute checks and security. Where local law permits, we retain transaction records for the period regulators require, then

purge. We do not sell your profile to third parties. Payment processors see only the fields they need to settle a DANA, OVO, GoPay or QRIS movement, nothing more. You can request a copy of what we hold at any point.

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

HELP CHANNELS

Privacy Contact Paths

Privacy Inbox Email our privacy desk directly when you want a copy of your data, a correction to your profile, or a deletion request. We acknowledge within one business day and resolve inside the window regulators set.
Live Chat Desk Open the chat bubble from any virus88 page and ask for the privacy team. The agent routes you to a reviewer who handles consent changes, marketing opt-outs and cookie preferences on your account.
Account Settings Head to your profile panel to toggle communication preferences, withdraw consent for optional analytics, or download a snapshot of your stored data without waiting on an agent reply.
WHY VISITORS TRUST US

How We Keep This Policy Honest

Editorial Review

Our legal and product teams re-read this policy each quarter so the wording tracks the actual data flows inside virus88, not a template copied from another brand. Changes get dated at the foot.

Named Reviewers

Every revision is signed off by a named data steward inside our team. If you ask who approved the current text, our support desk will tell you which role cleared it.

Version History

We keep prior versions of this policy on file. Request the archive through the privacy inbox and we send the dated PDFs so you can see what changed between revisions.

Encryption Standards

Account fields, session tokens and payment references move over TLS and rest behind encrypted storage. Our infrastructure team rotates keys on a schedule documented in our internal security posture.

Access Controls

Only staff with a job reason can open your profile. Each lookup is logged, reviewed, and tied to a ticket so we can trace any internal access back to a cause.

Regulator Alignment

Where local law permits us to operate, we align retention windows and breach-notice timing with that jurisdiction's data authority. Conflicts default to the stricter standard, not the looser one.

Consistency Across Our Policy Pages

Scope
This page covers account data. Our cookie page covers browser identifiers, and our terms page covers contractual rules. The three read together without contradiction.
Language
We use the same plain English here as on the terms and cookie pages, so you don't need a legal dictionary to switch between them.
Definitions
Terms like account data, session log and payment reference carry the same meaning across every legal page on virus88 — defined once, applied everywhere.
Retention
Retention windows quoted here match the figures on the terms page. If one updates, the other updates in the same release.
Contact Routes
The privacy inbox, chat desk and account panel listed here are the same routes referenced on the cookie and terms pages for any data question.
Update Cadence
All three policy pages are reviewed together each quarter. You won't see one drift ahead of the others with mismatched dates at the foot.
Jurisdiction Wording
We use the phrase supported regions consistently. Where local law permits appears in the same context across pages so the reading stays predictable.
AT A GLANCE

What Shapes This Policy Page

01
Plain Sections We break the policy into short, titled blocks rather than one long wall of text. You can jump to the section that answers your question without reading the whole document end to end.
02
Dated Footer Each revision carries a date stamp at the foot of the page so you can tell at a glance whether the version you're reading is the current one or an older cache.
03
Inline Definitions Where a term might be unfamiliar, we define it in the same sentence rather than sending you to a glossary tab. The reading stays linear and quick.
04
Cross-Links Related rules on our terms and cookie pages are linked inline so you can follow a thread between documents without losing your place on this one.
05
Reader Requests We list the requests you can make — copy, correction, deletion, consent withdrawal — in one block so you don't have to hunt across paragraphs for the action you want.
06
Quiet Tone No marketing language sits inside the policy body. The page reads as a reference document, with promotional copy kept to the lobby pages where it belongs.

Privacy Questions We Hear Most

We store the fields you submit at signup — name, contact, date of birth — alongside session logs, device fingerprints and payment references tied to DANA, OVO, GoPay or QRIS movements. Nothing beyond what the account needs to run.

Yes. Email our privacy inbox or open the request from your account panel. We acknowledge inside one business day and deliver the export within the window your local data authority sets for such requests.

We share only what payment processors and identity-verification partners need to complete the task you initiated. We do not sell your profile or pass it to marketing networks outside our own brand environment.

Active account data sits with us while your profile is open. After closure, we retain transaction history for the period regulators in your supported region require, then purge the remainder from live systems.

Toggle the communication preferences in your account panel at any time. The change applies to future sends immediately. Transactional messages tied to security or balance movement remain on, as they are not marketing.

Account fields move over TLS in transit and sit behind encrypted storage at rest. Internal access is gated, logged and reviewed. Our security team rotates keys and audits access on a documented schedule.

The revision date sits at the foot of this page. We review the text each quarter and publish changes with a fresh date stamp, so you always know whether the version you're reading is current.