How athena777 Handles Your Account Data
This page is the privacy policy for athena777 and nothing else. We wrote it for you, the account holder in Indonesia, so the rules around your name, phone...
Policy Posture and Jurisdiction Wording
We collect only what your account needs: your registered phone, the e-wallet handle you link for DANA, OVO, GoPay or QRIS transfers, your verified identity fields, and the session data that keeps your lobby secure. We process this where local law permits and only in supported regions of Indonesia. We do not sell your data to third parties. Game providers receive the
minimum needed to render a round on your screen. Retention follows the windows our licensing requires, after which records are archived or deleted. You can ask us to export or correct your file at any time through the policy contact channels below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy Contact Paths
If a clause on this page is unclear, or you want to act on a data right, three channels reach the privacy desk directly. We answer in Bahasa Indonesia or English and treat policy requests separately from general lobby support so nothing gets buried in a wallet ticket.
Privacy Mailbox
Write to our policy inbox with your registered phone number and a short summary of the request. We confirm receipt the same business day and queue your file for a written reply within seven days.
In-App Policy Ticket
Open the help menu inside your account, choose the privacy category, and your message routes straight to the data team rather than the general lobby desk. Attach screenshots if a clause needs context.
Account Deletion Line
For closure or erasure requests we keep a dedicated channel so the file is handled by a senior reviewer. Expect an identity check before we action anything permanent on your record.
Editorial Trust Signals for This Policy
This policy is reviewed by named people, not generated and left alone. The signals below explain who touches the text, when it changes, and how we keep wording...
Named Reviewer
A privacy officer signs off every revision before it goes live, and the role is held by a person, not...
Revision Cadence
We revisit this page on a fixed quarterly cycle and any time a rail like QRIS adjusts its data terms...
Plain-Language Pledge
Clauses are rewritten until a first-time reader can follow them without a legal background. If a section still reads like...
Scoped Data Use
We log only what the account flow needs to function. Marketing analytics run on aggregated counts, never on identified records...
Vendor Discipline
Game studios and payment partners receive contractually scoped fields. We refuse data-sharing requests that fall outside the stated purpose, even...
Audit Trail
Every export, correction or deletion request is logged with timestamp and reviewer name. You can ask for a copy of...
Consistency Across Our Policy Pages
We keep wording aligned across every legal surface so a clause on this page does not contradict the terms or cookie notice. The points below show where this...
| Versus Terms of Service | The terms describe what the account does; this page describes what we hold about you while it runs. Definitions are mirrored so neither document drifts from the other. |
|---|---|
| Versus Cookie Notice | Cookies sit in their own page with switches you control. This policy references the categories but does not duplicate the on-off controls, keeping each surface focused on one job. |
| Versus KYC Page | Identity checks are described operationally in KYC. Here we cover only the retention windows and lawful basis for keeping those documents on file after a check is complete. |
| Versus Payments Page | Wallet linking instructions live on the payments surface. This policy covers what happens to the handle once stored, not how to attach DANA or GoPay in the first place. |
| Versus Complaints Path | Dispute handling for game outcomes has its own route. Privacy complaints follow the channels on this page and feed a separate reviewer queue to avoid mixed escalations. |
| Versus Marketing Consent | Opt-in switches for messaging sit in your account settings. This page explains the lawful basis behind those switches without re-listing the toggles themselves. |
| Versus Closure Flow | Closing an account is a product action; erasing the underlying record is a privacy action. We separate the two so a closure does not accidentally trigger irreversible deletion. |
What This Policy Page Includes
These are the visible elements you will find as you scroll the privacy surface. They define how the policy is laid out, not which wallets we...
Scope Block
The opening clause names exactly which athena777 properties this policy covers and which sit under separate notices. It also flags the supported regions of Indonesia where the document applies.
Data Categories
A labelled list of every field we hold, from registered phone to session tokens. Each category is paired with a lawful basis so you can see why a field exists on your record.
Retention Windows
Tables showing how long each category stays on file, written as months or years rather than vague phrases like indefinitely. Expired records move to archive or deletion automatically.
Rights Panel
A summary of access, correction, portability and erasure rights with the exact channel for each. Response windows are quoted in business days, not in marketing language.
Changelog Footer
The foot of the page carries the last revision date and a short note on what changed. Older versions are kept on request so you can compare wording across releases.
Contact Block
Names the privacy desk and the escalation path if a reply runs late. This is where to start before involving any external supervisory authority for an unresolved concern.