LEGAL REFERENCE

Our Legal Notice and Account Terms

This is where we set out the rules that frame your topcer33 account. We've kept the language plain so you can scan the parts that matter — eligibility...

PolicyEligibilityJurisdictionDisputesRecords
topcer33 Our Legal Notice and Account Terms

Policy Posture and Jurisdictional Access

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

PLAYER SUPPORT

Policy Contact Paths

If a clause needs clarifying or you want to raise a formal matter, use the routes below. Our policy desk is separate...

Policy Desk Email Send written queries about terms, eligibility or jurisdictional...
Account Review Chat For account-specific clauses — closures, document checks, regional...
Formal Dispute Form When a matter needs escalation, the dispute form...
WHY THIS PLATFORM

Editorial Trust Signals for Policy Review

Our legal pages are maintained by the same team that drafts account terms, so the wording you read matches the wording enforced internally.

Policy Authorship

Each clause is drafted by our in-house terms team and reviewed before publication. We don't outsource legal copy to general writers, which keeps the language consistent with what your account agreement actually says.

Version History

We retain dated versions of every policy update. If a term changed after you opened your account, we can show you which version applied at the moment of your session or transaction.

Jurisdiction Mapping

Access rules are mapped against supported regions in Indonesia. Where local law restricts a feature, the lobby reflects that automatically rather than relying on small print buried in the terms.

Document Handling

Identity files you submit during verification are stored under access controls and retained only for the period our policy requires. We document who viewed each file and when.

Written Replies

Policy matters receive written replies, not verbal summaries. That gives you a record you can refer back to if a clause is reinterpreted or a clarification is needed later.

Internal Audit

Our compliance team audits policy enforcement against the published terms each quarter. Discrepancies are corrected in the next published version with a note in the version history.

SIDE BY SIDE

Consistency Across Our Policy Pages

Our terms, privacy notice and this legal page are written to align, so a clause you read here matches what appears in the others.

01

Terms of Use

This legal page summarises the posture; the terms page carries the binding clause language. Both are updated together so the framing matches the enforceable wording.

02

Privacy Notice

Data retention notes here reference the privacy notice, which sets out exactly which fields we keep, for how long, and which parties may access them under our retention schedule.

03

Account Agreement

The agreement you accept at sign-up restates eligibility, jurisdictional access and dispute paths. The clauses cross-reference this page so you can trace each rule to its source.

04

Payment Terms

DANA, OVO, GoPay and QRIS routing rules sit in the payment terms. This page only references their jurisdictional context — it doesn't restate transactional clauses.

05

Closure Policy

Account closure routes are documented separately. This page points to the policy desk as the entry point; the closure policy lists timing, record retention and balance handling.

06

Dispute Procedure

The dispute form referenced above feeds into the procedure document, which sets out timelines, escalation tiers and the format we use for written replies to formal matters.

07

Update Log

Material changes are recorded in the update log with a date stamp. The log is linked from each policy page so you can confirm which version was active during your session.

AT A GLANCE

Brand Highlights on the Policy Layout

These are the visible elements you'll notice when reading any of our policy pages — they're designed for quick scanning rather than legal density.

Clause Anchors Each clause has a stable anchor link so you can...
Plain-Language Lead Every section opens with a short plain-language line before the...
Version Badge A version badge sits at the top of each policy...
Jurisdiction Note Where a clause depends on regional access, a short jurisdiction...
Contact Inline Policy desk contact details appear inline at the foot of...
Print View Each policy page has a print-friendly view that strips navigation...

Common Questions on Our Legal Notice

Your account is governed by the terms published at sign-up, applied where local law permits in supported Indonesia regions. The jurisdiction note inside each clause tells you when regional rules narrow what's available.

Use the dispute form linked above. It captures the clause, the date, and any transaction references. Submission triggers our written review track, and a case handler replies inside the timelines set in the dispute procedure.

Retention follows the schedule in our privacy notice. Identity files, session logs and payment references are kept for the period our policy requires, then removed under documented controls rather than held indefinitely.

Material changes are flagged inside your account dashboard before they take effect, and the update log records the date. You can compare the active version against an earlier one using the version badge on each policy page.

No. DANA, OVO, GoPay and QRIS routing sits in the payment terms document. This page only references their jurisdictional context so you can trace which rules apply to transactions in your supported region.

Yes. Closure routes are set out in the closure policy linked from this page. The policy desk is the entry point, and timing, balance handling and record retention follow the documented procedure.

The update log lists dated versions and we retain them for reference. If a clause changed after you opened your account, ask the policy desk and we'll send the version that applied at the relevant moment.