Legal notice
This page. Sets out jurisdiction posture, eligibility and how our policy desk operates. Start here before opening any of the deeper policy documents.
This is the legal corner of pompa303. We've put our account terms, jurisdiction posture and policy contact paths in one place so you can read them before you...
pompa303 operates where local law permits and our account terms reflect that. By opening an account you confirm you're of the legal age set in your supported region and that you accept our published clauses on identity checks, account ownership and dispute handling. We hold the right to pause an account when documentation is pending, and we'll always tell you which clause
we're acting under. Our policy texts are versioned — every revision keeps a date stamp so you can see what changed and when. If a clause is ever updated in a way that affects your account, we notify you on sign-in before anything takes effect on your side.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a clause needs clarifying, our policy desk handles it directly. These are the channels we keep open specifically for legal and account-terms questions — separate from general lobby support so your...
Editorial trust matters when the topic is your account terms. Here's how we keep our legal pages accurate, current and worth your time to read.
Every clause is re-read on a quarterly cycle. If wording has drifted from how we actually operate the lobby, we rewrite it that quarter rather than waiting for a complaint to surface the gap.
Each policy update lands with a date stamp and a short note on what shifted. You can scroll back through the changelog and see exactly when a clause moved.
Our terms go through a plain-English pass before publishing. If a clause needs three reads to parse, it goes back to drafting until a first-time reader can follow it.
Policy revisions carry the initials of the reviewer who signed them off. Accountability stays internal but visible, so nothing reaches you unread.
If you flag wording as confusing through our policy desk, that note goes into the next review cycle. Real reader friction reshapes the next draft.
Terms, privacy and account clauses are checked against each other so a rule in one document doesn't quietly contradict a rule in another. Consistency is part of the review.
Our legal corner has sibling pages — terms, privacy, account closure. Here's how this notice lines up with them so you know which page to open for what.
This page. Sets out jurisdiction posture, eligibility and how our policy desk operates. Start here before opening any of the deeper policy documents.
Detailed clauses on account ownership, identity checks and how we handle pauses or closures. Referenced from this notice but kept on its own page for depth.
Covers what we store, how long we hold it and who inside pompa303 can see it. Aligned with the identity-check clauses you'll find in account terms.
Sits beside privacy and explains the small data points your browser shares with our lobby. Short, scoped to browser-side storage only.
Walks through how a disagreement on an account or transaction is escalated, reviewed and answered. Cross-references the policy desk channels listed here.
Explains how to close an account cleanly, what timing applies and which records we retain afterwards under our jurisdiction posture.
A running list of revisions across every policy page, with date stamps. If you want the short version of what changed and when, this is the page to bookmark.
The visible elements on this page are shaped to help you read policy without losing your place. These are the layout choices we lean on across our legal corner.