LEGAL REFERENCE

How We Handle Your Account Data

This is the surya77 login privacy policy — the page that tells you, in plain words, what we collect when you open an account, why we keep it...

Plain-language policyIndonesia-focusedAccount-data scopeWallet-awareUpdated regularly
See the Lobby Read FAQ
surya77 login How We Handle Your Account Data

Our Privacy Posture and Your Rights

We collect only the account fields we need: your sign-in identifier, verification details, wallet reference for DANA, OVO, GoPay or QRIS, and the session logs that keep your lobby secure. Where local law permits, we store this data on encrypted infrastructure and share it only with the payment partners processing your top-ups. You can ask us to export, correct or delete your

record at any time, and we'll respond within the timelines set by the supported regions you're accessing us from. Marketing messages are opt-in — you control them from your account panel, not us.

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

SUPPORT

Privacy Contact Paths

If you have a privacy question, these are the routes that reach our data team directly. Each one is monitored by staff trained on the surya77 login policy, not generic lobby agents.

Team online

Privacy Inbox

Email our data desk for access, correction or deletion requests tied to your account. We acknowledge within one business day and resolve within the windows your region allows.

Live Chat Escalation

Open the chat bubble in the lobby and ask for the privacy queue. The agent will route you to a reviewer who can pull your data record and walk you through any change.

Account Panel Controls

Sign in and head to settings — you can toggle marketing consent, refresh your wallet references for DANA, OVO, GoPay or QRIS, and download a copy of what we hold.

EDITORIAL CLARITY

Why You Can Rely On This Policy

Our privacy page isn't a copy-paste template. It's reviewed by the people who actually run the surya77 login account stack, and refreshed whenever the rules around Indonesia wallet processing shift.

Reviewed Quarterly

We sit down every quarter to re-read this policy against current Indonesia data rules and the wallet partner agreements behind DANA, OVO, GoPay and QRIS, then publish any wording change here.

Named Data Owner

A specific team owns this document — not an outsourced legal mill. When you email the privacy inbox, a reviewer who knows our lobby architecture answers, not a generic ticket bot.

Encrypted Storage

Account credentials, wallet references and session logs sit on encrypted volumes with key rotation. Only staff with a logged business reason can pull a record, and every access leaves an audit trail.

Minimal Collection

We ask for the fewest fields the lobby needs to keep you signed in and your top-ups moving. If a field isn't required for play or compliance, it isn't on the form.

Partner Vetting

Every payment and game partner we share data with is checked against a privacy checklist before they touch a single record. We drop any partner that can't meet our standard.

Clear Retention

We don't keep your data forever. Retention windows are written into this policy, and once a window closes the record is purged from active and backup storage on schedule.

Consistent Across Our Policy Pages

This privacy policy lines up with the other legal pages on surya77 login — terms, cookies, account closure — so you're not chasing contradictions between documents.

Same DefinitionsWords like account, wallet reference and session log mean the same thing here as they do in our terms page, so cross-reading is straightforward.
Shared Update LogEvery policy page on the brand carries the same revision date format and changelog style, so you can see at a glance which document was touched.
Aligned RetentionThe retention windows we list here match the ones in our account closure policy — close your account and the deletion clock starts on the same schedule.
Single Contact DeskPrivacy, terms and cookie questions all reach the same internal team, so you never get bounced between inboxes for a layered question.
Matched JurisdictionAll policies reference supported regions in the same wording, so the access boundaries you read on one page hold true on every other legal page.
Wallet Wording ParityDANA, OVO, GoPay and QRIS are described identically across privacy, terms and the payment legal page — no surprise definitions hidden between documents.
Consent SyncThe marketing toggle in your account panel controls every channel at once. Flip it off here and the terms-side communication clauses respect the same choice.
PLATFORM SNAPSHOT

What This Policy Page Shows You

These are the visible parts of our privacy layout — the building blocks that make the page easy to scan instead of a wall of legal text. Each one is here for a reason...

01
Section Anchors The page is broken into labelled blocks so you can jump to the part you need — collection, storage, sharing, retention — without reading everything in order on a small phone screen.
02
Plain-Language Body We write each section in everyday English first, then add the precise wording where the law needs it. You shouldn't need a legal background to know what we do with your account data.
03
Wallet Context Chips The chip row reminds you which payment rails this policy covers — DANA, OVO, GoPay and QRIS — so you can see at a glance that your top-up flow is in scope.
04
Revision Date Every published version carries a clear revision date at the top of the policy, so you know whether you're reading the current text or an older snapshot held by a search engine.
05
Inline Contact Points Where a section talks about a right you can exercise, the contact path sits right next to it. You don't have to hunt for an email address at the bottom of the page.
06
FAQ Companion The questions block below answers the items the privacy desk hears most often, so common worries are resolved on the same page rather than via a back-and-forth email thread.

Privacy Questions We Hear Most

We collect your sign-in identifier, verification fields required by Indonesia rules, your wallet reference for DANA, OVO, GoPay or QRIS, and session logs. Nothing more is taken unless you explicitly add it to your profile.

Active account data is held while your account is open. After closure, identifiers and transaction records are retained only for the period supported regions require, then purged from active and backup storage on a documented schedule.

Yes. Email the privacy inbox or open the chat queue and request an export. We'll verify it's you, then send a structured file covering your account fields, wallet references and recent session logs within the legal window.

Only with partners that need it to run the lobby — payment processors for DANA, OVO, GoPay and QRIS, and the game studios powering your sessions. Each partner is vetted and bound by a written data agreement before any record moves.

Sign in, open the account panel and toggle marketing consent off. The change applies across email, SMS and push at the same time. You'll still get essential service notices tied to your account and top-ups.

We store a tokenised reference, not your raw DANA, OVO, GoPay or QRIS number. The token lets us match your top-ups without keeping the underlying wallet identifier sitting in our database in plain form.

We update the revision date at the top, log the change, and if it materially affects your rights we notify you in-account before it takes effect. Older versions stay available on request through the privacy inbox.