Acceptable use

Anyone using this website or its demonstration, and any party integrating against the Parity API, the embedded interface or the portal.

Parity is business-to-business infrastructure. It sits between an OPERATOR — the platform that holds the customer relationship — and a VENUE that lists and settles event contracts. Three parties, three sets of responsibilities, and almost every question about this service is answered by working out which one owns the thing being asked about.

THE OPERATOR owns the end customer: the account and its credentials, KYC — identity and age verification — the customer cash ledger, deposits and withdrawals, bonuses, deposit and loss limits, time-outs and self-exclusion, and first-line customer support. Parity holds none of those and cannot act on any of them.

PARITY owns the normalized market catalogue and the market data behind it, the quote, the routing decision, the order lifecycle, positions, execution records, the settlement and reconciliation instructions an operator books against its own ledger, and the analytics over all of that.

THE VENUE owns liquidity, the execution of a contract, the wording of the market it authored, the source it resolves against, and its own settlement mechanics.

Two consequences are worth stating outright. Parity does not warehouse event risk: it does not take the other side of a customer’s position. And Parity does not hold or need a customer cash balance — a filled order or a resolved position produces an amount the operator applies to its own book, not a movement in a wallet here.

Do not attempt to reach data, tenants, accounts or systems you have not been granted access to. Do not attempt to disrupt or degrade the service, including by placing automated load on the API beyond what ordinary evaluation requires.

Do not attempt to circumvent the controls the product applies to orders — quote expiry, stake caps on a stale price, refusals on a price too far behind to trust, or a market an operator has switched off for its traffic — or to place orders against prices the system has declined to quote.

Do not use the service to manipulate the price of any underlying market, to coordinate trading intended to move a published price, or to trade on information obtained in breach of a duty of confidence.

API keys are issued per tenant and are stored by Parity only as a hash — we cannot show you an existing key, only replace it. Keys belong on a server. A key in a browser, a mobile binary or a public repository is a key that has been disclosed, and a sandbox key is protected exactly as carefully as a live one.

An embed session token is short-lived and single-purpose. Do not persist it, do not put it in a URL, and do not send it anywhere except the interface it was minted for.

Market questions, prices and resolutions originate with the venues and are subject to their terms. Do not scrape this service to reconstruct a competing catalogue, and do not redistribute the normalized catalogue as your own data product.

Security vulnerabilities go to security@tryparity.co. Reports made in good faith are welcome and will not be treated as a breach of these terms.

Anything else — suspected abuse, or a problem with the service itself — goes through the contact form; the complaints page explains what to include.

Operational information. This page describes how Parity operates today. It has not been reviewed by legal counsel and is not a contract.

A live commercial deployment needs a named contracting entity, a governing law and jurisdiction, and a jurisdiction-by-jurisdiction analysis of where event contracts may be offered and by whom. Those decisions have not been made. This page names them as outstanding rather than filling in a plausible answer, because an invented one is the detail that gets checked.

If you are evaluating Parity commercially, ask for the current draft of the agreement. That, and not this page, is what would bind either of us.