LEGAL REFERENCE

Our Legal Centre, Plain and Readable

This is where we keep the policies that sit behind your ayamjp account — terms, privacy posture, cookie handling and the rules we apply to lobby access. We've...

Account TermsPrivacy PostureCookie HandlingLobby Access RulesPolicy Contacts
ayamjp Our Legal Centre, Plain and Readable

Policy Posture for Indonesia Accounts

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

HELP CHANNELS

Reaching Our Policy Team

Policy Inbox Email our legal desk directly when you need...
In-Lobby Chat Open the chat panel from any lobby screen...
Data Requests Submit access, correction or deletion requests through the...
PLATFORM TRUST SIGNALS

How We Maintain Editorial Trust

Named Reviewers

Every clause on this page passes through a named reviewer on our legal team before it reaches you. Initials and review dates are tracked internally so we can trace who approved what and when changes shipped.

Version History

We keep prior versions of each policy document on file. If you need to see what the terms said the day you opened your account, we can surface that version on request through the policy inbox.

Plain Language Pass

Before publication, drafts get a plain-language pass so clauses read in second person where possible. Legal accuracy stays, but we strip the boilerplate that makes policies feel deliberately confusing to ordinary readers.

Change Notices

Material changes reach you in-lobby and by email, with a window to review before the new wording binds your account. Cosmetic edits are logged but don't trigger a fresh notice on your side.

External Counsel

Indonesia-aware counsel reviews our posture on jurisdiction, payment handling and data retention. Their notes feed straight back into the documents you read here, not into a separate file kept away from you.

Reader Feedback

If a clause reads ambiguously, tell us. We log the report, the reviewer rewrites the section, and the next published version credits the change in our internal log so the loop closes cleanly.

Consistency Across Our Policy Pages

Terms of Service
Sets the rules for your account, lobby conduct and our obligations. Cross-references the privacy page rather than repeating it, so one source of truth governs each topic without contradictory wording.
Privacy Notice
Covers what we collect, why we keep it and how long it stays. Mirrors the retention windows quoted in the terms so you never see two different numbers for the same data category.
Cookie Statement
Explains session, preference and analytics cookies separately. Aligns with the consent prompt you saw on entry, so toggles in your settings match the categories described on this policy page exactly.
Acceptable Use
Describes lobby behaviour we won't host — automation, account sharing, abusive chat. Echoes the enforcement steps named in the terms, so the consequences you read here match what the terms commit us to.
Payment Terms
Documents how DANA, OVO, GoPay and QRIS references move through settlement. Refers back to the privacy notice for data handling rather than restating it in different words on this page.
Complaints Path
Lays out escalation from chat to policy inbox to external review. Each step matches the timelines named in the support section, so you never chase a clause that contradicts an answer from an agent.
Dispute Resolution
Names the forum and the sequence we follow. Sits flush with the jurisdiction clause in the terms, so the venue you read on one page is the venue quoted on the other without exception.
AT A GLANCE

What Defines This Policy Layout

01
Clause Anchors Each clause carries a stable anchor link so you can share a specific paragraph with our support team or a friend without making them scroll through the whole document to find the line in question.
02
Effective Dates Every policy block shows the date it took effect on your account. When we revise, the prior date stays visible in the version log so you can see exactly when a wording shift happened.
03
Reader Mode A reading toggle drops sidebars and widens the column so long clauses become easier on the eye. Useful when you're working through the terms on a phone screen rather than a desktop monitor.
04
Quick Index A condensed index sits at the top of each policy. Tap a heading to jump straight to the clause without scrolling, then use the back-to-index control to return to the list of sections.
05
Print-Friendly View Each policy renders cleanly for print or PDF export, keeping headings and clause numbers intact. Handy if you want a hard copy filed alongside your other account paperwork at home.
06
Language Note Our policies publish in English for Indonesia readers. Where a translated extract helps, we mark it as a courtesy rendering and point you back to the English wording that actually binds your account.

Common Questions on Our Policies

They sit linked from your account settings and from the footer of every ayamjp page. Open either entry and you land on the latest published version, with the effective date shown at the top of the document.

Material changes reach you in-lobby and by email before they take effect. You'll see a short summary of what shifted, with a link to the full revised wording so you can compare against the version you accepted.

Yes. Use the privacy form in your account settings to submit an access, correction or deletion request. We verify your identity against records on file, then return your export in a portable format within the stated window.

Your account operates where local law permits, and the governing forum is named in the terms you accepted at sign-up. If your region moves outside our supported list, the lobby will tell you rather than guess on your behalf.

DANA, OVO, GoPay and QRIS references are held as protected payment data. They move only across the rails needed to settle your transaction, and they're never shared with parties outside that settlement path on our side.

Write to our policy inbox with the clause anchor and your concern. A named reviewer reads the message, replies with our position, and where the wording is genuinely ambiguous, we log it for the next revision cycle.

We do. Earlier versions of the terms, privacy notice and cookie statement sit on file. If you need to see what a document said on a specific date, ask the policy inbox and we'll surface that version for you.