Compliance policy

We build for users in jurisdictions where the venue is accessible.

Polymarket and Kalshi have different regulatory profiles. We respect both. This page documents how we approach geographic restrictions, KYC, and what we will and won't do.

Polymarket

Geographic restrictions are real.

Polymarket's Terms of Service prohibit access from certain jurisdictions. As of May 2026: United States (with limited QCEX beta exception), France, Germany, Italy, Belgium, Poland, Switzerland, Singapore, Thailand, Netherlands, Portugal, plus all OFAC-sanctioned countries.

i
If you're in a Polymarket-accessible jurisdiction

(India, Israel, Canada outside Ontario, UAE, HK, Argentina, Brazil, Mexico, Nigeria, South Africa, Turkey, Korea, Spain - confirm current status with Polymarket), we'll quote your project normally.

×
If you're in a blocked jurisdiction

We won't ship a Polymarket bot, won't advise on VPN access, won't accept the project. For US residents wanting prediction markets, see Kalshi - CFTC-regulated, fully legal.

Kalshi

Regulated US venue. Trade legally in all 50 states.

Kalshi is a CFTC-licensed Designated Contract Market. US residents can trade legally with KYC. We build Kalshi bots without geographic restriction concerns for US clients.

CFTC OVERSIGHT

Kalshi operates under CFTC supervision. Trade rules, settlement, dispute resolution all federally regulated.

KYC REQUIRED

Each client must be KYC'd by Kalshi before bot deployment. Standard process - we'll guide you through.

TAX REPORTING

Kalshi issues tax documents. Cleaner than crypto-settled venues. We don't give tax advice; consult your accountant.

Our process

What we verify before quoting.

01 · JURISDICTION DECLARATION

Every quote request includes a jurisdiction field. We don't quote without it.

02 · GEOGRAPHIC REVIEW

For Polymarket projects: we confirm the jurisdiction is in the accessible list and document it in the project file.

03 · CODE-LEVEL ENFORCEMENT

Cross-venue bots include programmatic geographic checks that refuse to fire from blocked regions. Not just a policy - an actual code path.

04 · WRITTEN COMPLIANCE CLAUSE

Every contract has a compliance clause. You attest to your jurisdiction. We rely on that attestation.

×
What we will not do.

We will not advise on VPN setup for blocked jurisdictions. We will not deploy bots whose intended operator is in a blocked jurisdiction. We will not help structure entities to obscure the operating geography. If you push on any of these, we end the conversation. This is not about being precious - it's because we want to be in business in five years.

Questions

Edge cases? Get in touch.

Compliance situations are sometimes nuanced - multi-jurisdiction teams, holding companies, corporate vs personal accounts. Send us the specifics; we'll come back with a clear yes or no within 2 business days.