Our Legal Posture, In Plain Language
This is the legal corner of priaqq, written for you in clear English. We've grouped the terms, privacy stance and account rules that govern your use of our...
Policy Posture and Jurisdiction Scope
Our terms apply where local law permits and only across supported regions. If you're accessing priaqq from Indonesia, the agreement you accept at sign-up governs your account, your activity in the lobby and the way we handle your data. We follow standard privacy practice: we collect what's needed to verify identity, fund your wallet through DANA, OVO, GoPay or QRIS, and keep
the platform secure. You retain rights to request, correct or delete the personal data we hold, subject to record-keeping obligations. Disputes are handled first through our policy contacts, then escalated to the channels named in the full terms document linked from your account dashboard.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy Contact Paths
Privacy Desk
Write to our privacy desk if you want a copy of the data we hold, a correction to inaccurate fields, or a deletion request. We respond inside the window stated in our privacy clause.
Terms Queries
For clause-level questions about the user agreement — wording, scope, jurisdiction references — our terms team replies in English and routes complex matters to a senior reviewer when needed.
Account Disputes
Disagreements about account standing, closures or suspension reasons go through the disputes channel. Bring your account ID and we'll trace the decision back to the specific policy clause applied.
Editorial Trust Signals For Policy Review
Plain Language
Our terms are drafted in everyday English first, then checked against legal templates. If a clause needs jargon, we add a short note next to it so you know what it actually means in practice.
Version History
Each policy carries a visible last-updated stamp. When we revise wording, the prior version stays accessible for thirty days so you can compare what shifted between releases.
Named Reviewers
Policy edits pass through a named compliance reviewer before publication. We avoid anonymous changes — accountability for the wording sits with a real desk inside our team.
Indonesia Scope
Clauses reference Indonesia explicitly where the rule differs by region. You won't have to guess whether a paragraph applies to your account or to a market we don't serve.
Data Minimum
We collect the minimum needed to run your account and process DANA, OVO, GoPay or QRIS movements. Optional fields are labelled, and marketing consent is separated from service consent.
Escalation Routes
If our first response doesn't resolve your concern, the policy notice lists the next step. We don't hide escalation behind generic inboxes or unanswered ticket queues.
Consistency Across Sibling Policy Pages
| Terms vs Privacy | Terms cover what you agree to when using priaqq; privacy covers what we do with your data. Both reference the same defined terms so wording stays aligned across documents. |
|---|---|
| Privacy vs Cookies | The privacy notice describes data handling broadly; the cookie statement narrows in on browser-side storage. Cross-links sit at the top of each so you don't have to hunt. |
| Account Rules vs Terms | Account rules are the day-to-day behaviour expectations inside the lobby; terms are the umbrella contract. Account rules cannot contradict the parent terms — terms always win. |
| Disputes vs Support | General support handles how-to questions; the disputes route is reserved for policy-grounded disagreements. Routing the right query to the right desk speeds up resolution. |
| Indonesia vs Regional | Indonesia-specific clauses sit under named headings. Regional notes are clearly separated so you read only what governs your account, not paragraphs about other markets. |
| Policy vs Marketing | Promotional pages describe what's in the lobby; legal pages describe the rules. We never embed offers inside legal copy, and we never bury obligations inside marketing. |
| Past vs Current | Archived versions stay reachable for the stated retention window. Current policy is always the one rendered here — the archive is reference, not active agreement. |