Parlays without
leverage.
Up to 0x on stocks, crypto & more.No margin. No liquidations. Max loss is the ticket.
Build a ticketOpen the boardMarkets
Multipliers lock when your ticket fills.
Build a leg
Drag this button onto the slip or tap it.
Keys are stored only in this browser and sent only to the provider. CoinGecko gives live crypto prices and charts; Polygon gives stocks and ETFs from the last completed session with intraday bars.
Connecting a wallet reads your address and balance only. Nothing is signed or sent until you place a ticket.
What a ticket is
A ticket is a stake plus three to six legs. Each leg is a yes-or-no call on a price, settled by an oracle. Each leg has a multiplier, and the combined multiplier is all of them multiplied together. The payout is the stake times the combined multiplier, paid only if every leg hits.
| Term | Meaning |
|---|---|
| Stake | What you pay for the ticket. Your maximum loss. |
| Leg | One yes-or-no call on a price, settled by an oracle. |
| Leg multiplier | What that leg pays on its own. Less likely calls pay more. |
| Combined multiplier | All leg multipliers multiplied together. |
| Payout | Stake times combined multiplier, paid only if every leg hits. |
Example: 1.9 x 2.4 x 3.1 x 5.2 x 5.6 = 411.6x, so a $10 ticket pays $4,116 if all five hit.
Leg types at launch
- Up or down. Price at the end of the window is above or below the price when the ticket filled.
- Above or below a level. Price is past a chosen level at a set time.
- Moves either way. Price moves at least X percent in any direction inside the window.
- Streak. Several consecutive periods all close the same direction.
All four settle from oracle prices with no human judgement involved.
Lifecycle
- Build. Add three to six legs. The app shows each multiplier and the combined payout live.
- Place. Pay the stake. Multipliers lock when the ticket fills on the next oracle update, not at the price you saw while building.
- Run. Legs settle one by one as their windows end. Each shows Hit, Live or Waiting.
- Dead. The first leg that misses kills the ticket. The stake goes to the treasury.
- Paid. If the last leg hits, the full payout is paid from the treasury immediately.
How multipliers are priced
Each leg has a probability p of hitting, estimated from the asset's recent volatility and the window length. The multiplier is (1 − edge) / p. The proposed launch edge is 5 percent per leg. A coin-flip leg pays 1.9x. A leg with a one in six chance pays about 5.7x.
Because the edge applies to every leg, it compounds. A five-leg ticket carries about 23 percent total house margin. This is how every sportsbook parlay works, and it is the reason the product can afford big headline payouts. Legs states this openly rather than hiding it.
The correlation problem
Multiplying leg multipliers assumes the legs are independent. They often are not. "SOL up" and "BTC up" in the same hour tend to hit together, so a ticket of correlated legs is much more likely to win than its combined multiplier implies. Left alone, this is the easiest way to drain the treasury.
Launch rules to handle it:
- One leg per asset per ticket.
- Assets are grouped into clusters (majors, memes, tech stocks and so on). A second leg from the same cluster in the same window gets a reduced multiplier.
- Opposite-direction legs on closely related assets are fine, since they cut against each other.
The treasury loop
- Every dead ticket's stake goes to the treasury.
- The treasury pays every winning ticket in full, on the spot.
- Max payout per ticket is the larger of 10 percent of available treasury and a floor. Proposed floor: $5,000.
- No IOUs. The total potential payout of all live tickets is capped at a fixed multiple of treasury equity. If a new ticket would break the limit, the app lowers the maximum stake it will accept.
Early on the max payout is small, which caps the headline multiplier. The plan is to seed the treasury, launch with modest caps and let them grow in public. A visible "max payout today" number that climbs over time is good marketing on its own.
Fees
| Fee | Proposed launch value |
|---|---|
| Ticket fee | None. The edge is inside the multipliers. |
| Payout fee | None at launch. |
| Cash-out spread | Applies only if cash-out ships. |
Keeping fees at zero outside the multiplier makes the pitch simple: the number on the ticket is the number you get.
Zero supply at launch
No presale, no team allocation, no airdrop. The first token exists when the first ticket dies.
Minted to players
Minted for every dollar of dead tickets, so losing a ticket still earns a stake in the venue.
Falling mint rate
The rate falls as the treasury grows and halves at lifetime volume milestones.
Buy and burn
A share of treasury growth above a threshold buys the token on the open market and burns it.
Not a refund
Rewards can be worth less than the ticket you lost. Often they will be.
Not a promise
The token has no claim on the treasury and no right to payouts. It is a record of participation.
Why mint from losses
Most tickets die. That is the honest shape of the product. Minting to the losing side means the people funding the treasury also accumulate the venue's token, and the venue's growth flows back to them through the burn.
What can go wrong
- If the mint rate is too generous early, the token inflates faster than the treasury grows and the burn cannot keep up.
- Wash tickets, placed to die on purpose for the mint, are a real attack. Per-address exposure limits and the falling rate are the first defence, and the mint rate has to be below the edge captured on the ticket.
- Token treatment varies by jurisdiction and is part of the legal review before mainnet. See Eligibility and regions.
Nothing on this page is financial, investment, legal or tax advice.
Overview
Legs is 1,000x without leverage. Stack simple price calls into one ticket. Every leg multiplies the payout. One miss and the ticket is dead.
Sports bettors love parlays because a small stake can pay enormously. Legs brings that to prices. You pick three to six yes-or-no calls about where prices go, each call has a multiplier based on how likely it is, and the multipliers compound. A $10 ticket with five legs can pay thousands. There is no margin, no leverage and nothing to liquidate. The most you can ever lose is the price of the ticket.
Tickets
| Term | Meaning |
|---|---|
| Stake | What you pay for the ticket. Your maximum loss. |
| Leg | One yes-or-no call on a price, settled by an oracle. |
| Leg multiplier | What that leg pays on its own. Less likely calls pay more. |
| Combined multiplier | All leg multipliers multiplied together. |
| Payout | Stake x combined multiplier, paid only if every leg hits. |
Example ticket:
| Leg | Call | Window | Multiplier |
|---|---|---|---|
| 1 | SOL up | Next hour | 1.9x |
| 2 | NVDA down | Today | 2.4x |
| 3 | BTC closes the week higher | By Friday | 3.1x |
| 4 | ETH moves 4% either way | Today | 5.2x |
| 5 | DOGE up three hours running | Tonight | 5.6x |
A $10 ticket pays $4,116 if all five hit.
Leg types at launch
- Up or down. Price at the end of the window is above or below the price when the ticket filled.
- Above or below a level. Price is past a chosen level at a set time.
- Moves either way. Price moves at least X percent in any direction inside the window.
- Streak. Several consecutive periods all close the same direction.
All four settle from oracle prices with no human judgement involved.
Lifecycle
- Build. Add three to six legs. The app shows each multiplier and the combined payout live.
- Place. Pay the stake. Multipliers lock when the ticket fills on the next oracle update, not at the price you saw while building.
- Run. Legs settle one by one as their windows end. Each shows Hit, Live or Waiting.
- Dead. The first leg that misses kills the ticket. The stake goes to the treasury.
- Paid. If the last leg hits, the full payout is paid from the treasury immediately.
A later version can add cash-out: selling a live ticket back to the treasury at a discount to its current value.
How multipliers are priced
Each leg has a probability p of hitting, estimated from the asset's recent volatility and the window length. The multiplier is:
Proposed launch edge is 5% per leg. A coin-flip leg (p = 0.5) pays 1.9x. A leg with a 1 in 6 chance pays about 5.7x.
Because the edge applies to every leg, it compounds. A five-leg ticket carries about 23% total house margin. This is how every sportsbook parlay works, and it is the reason the product can afford big headline payouts. Legs states this openly rather than hiding it.
| Legs | Total house margin | Coin-flip ticket pays |
|---|---|---|
| 3 | 14.3% | 6.9x |
| 4 | 18.5% | 13.0x |
| 5 | 22.6% | 24.8x |
| 6 | 26.5% | 47.0x |
The correlation problem
Multiplying leg multipliers assumes the legs are independent. They often are not. "SOL up" and "BTC up" in the same hour tend to hit together, so a ticket of correlated legs is much more likely to win than its combined multiplier implies. Left alone, this is the easiest way to drain the treasury.
Launch rules to handle it:
- One leg per asset per ticket.
- Assets are grouped into clusters (majors, memes, tech stocks and so on). A second leg from the same cluster in the same window gets a reduced multiplier.
- Opposite-direction legs on closely related assets are fine, since they cut against each other.
The treasury loop
↑ |
└──── bigger max payouts ◄─────┘
- Every dead ticket's stake goes to the treasury.
- The treasury pays every winning ticket in full, on the spot.
- Max payout per ticket is max(10% of available treasury, floor). Proposed floor 5,000.
- No IOUs. The total potential payout of all live tickets is capped at a fixed multiple of treasury equity. If a new ticket would break the limit, the app lowers the maximum stake it will accept. Legs never promises a payout it cannot cover.
Cold start
Early on the max payout is small, which caps the headline multiplier. Seed the treasury, launch with modest caps and let them grow in public, or both. A visible "max payout today" number that climbs over time is good marketing on its own.
Fees
| Fee | Proposed launch value |
|---|---|
| Ticket fee | None. The edge is inside the multipliers. |
| Payout fee | None at launch. |
| Cash-out spread | Applies only if cash-out ships. |
Keeping fees at zero outside the multiplier makes the pitch simple: the number on the ticket is the number you get.
The token
- Zero supply at launch. No presale.
- Minted to players for every dollar of dead tickets, so losing a ticket still earns a stake in the venue.
- The mint rate falls as the treasury grows and halves at lifetime volume milestones.
- A share of treasury growth above a threshold buys the token on the open market and burns it.
- Rewards can be worth less than the ticket you lost.
More on the Token page.
Oracle and settlement
- Every leg settles from oracle prices. No human judgement, no appeals on price.
- Multipliers lock on the first oracle update after the ticket is placed. The fill price is the reference for up-or-down legs.
- Short windows settle on a time-averaged price around the window close rather than a single tick, to blunt oracle delay and manipulation at the close.
- If the oracle fails to report for a leg's window, the leg is voided, removed from the combined multiplier, and the ticket continues with the remaining legs. If fewer than three legs remain, the ticket is refunded.
Limits and exposure
- Per ticket: max payout is max(10% of available treasury, floor).
- Per venue: total potential payout of live tickets is capped at a fixed multiple of treasury equity.
- Per leg: exposure limits on any single asset and window cap the damage from a mispriced leg.
- Per address: daily stake limits, set per region. Lowering a limit applies immediately; raising one takes effect after a cooling period.
- When a new ticket would break any limit, the app lowers the maximum stake it will accept rather than rejecting the ticket outright.
What can go wrong
- Correlation abuse. The biggest structural risk. The cluster rules need tuning against real data.
- Bad probability estimates. If volatility inputs lag reality, some legs are overpriced and sharp players will find them. Per-leg exposure limits cap the damage.
- Oracle timing. Legs settle at exact moments, so oracle delay or manipulation at the window close matters a lot. Time-averaged settlement prices for short windows.
- Variance. Big multipliers mean rare, large payouts. One winner can take 10% of the treasury in a single ticket. The exposure cap is what keeps that survivable.
- Contract risk. Unaudited code holding deposits is the fastest way to lose other people's money.
- Regulation. Each leg is a binary option. Retail binary options are banned or restricted in a lot of places, including the US and the EU. Jurisdiction gating is required from day one, and this one deserves real legal advice before mainnet.
What Legs is not
It is not an investment product and it is not an edge. Most tickets die. The product is honest entertainment with a known house margin, a fixed maximum loss and a payout that is already in the contract before you play.
Open questions before building
- Exact cluster definitions and correlation haircuts.
- Minimum and maximum leg counts, and whether two-leg tickets are allowed.
- Shortest window the oracle can settle fairly.
- Whether cash-out ships at launch or later.
- Treasury seed size and the first max-payout floor.
Glossary
| Ticket | A stake plus three to six legs, bought as one unit. |
| Leg | One yes-or-no call on a price with a window and a multiplier. |
| Window | The period a leg is judged over: next hour, today, tonight, by Friday. |
| Hit / Live / Waiting | A leg's state: settled yes, currently inside its window, or window not yet started. |
| Dead | A ticket with at least one missed leg. The stake is gone. |
| Paid | A ticket where every leg hit and the payout has been sent. |
| Edge | The house margin built into each leg's multiplier. Proposed 5%. |
| Cluster | A group of assets that tend to move together. Second legs from one cluster in one window get a haircut. |
| Treasury | The pool that receives dead stakes and pays winning tickets. |
| Exposure cap | The limit on total potential payout of live tickets, as a multiple of treasury equity. |
| Cash-out | Selling a live ticket back to the treasury at a discount. Not at launch. |
Changelog
- v0.1 First public ruleset: four leg types, 5% edge, cluster rules, treasury loop, zero-supply token, open questions.
Every ruleset change will be versioned and logged, and every ticket will record the ruleset it ran on.
The basics
What is Legs?
A way to stack three to six yes-or-no price calls into one ticket. Each call has a multiplier. They multiply together. If every call hits, the ticket pays the stake times the combined multiplier. If any call misses, the ticket is dead.
Is this leverage?
No. There is no margin, no borrowing and nothing to liquidate. You buy a ticket for a fixed price. The most you can lose is that price.
Is it gambling?
Each leg is a binary option with a house margin. Legs is entertainment with a known edge, not an investment product. Most tickets die. We say this on the front page on purpose.
What can I make calls on?
Crypto and stock prices with reliable oracle coverage. The launch list is short on purpose and grows with oracle quality. Four leg types: up or down, above or below a level, moves either way, and streaks.
How long does a ticket take?
As long as its longest window. A ticket of hourly legs can be dead or paid in an hour. A ticket with a "by Friday" leg runs until Friday.
Tickets and payout
How is the payout calculated?
Stake times the combined multiplier, which is every leg multiplier multiplied together. The number is shown while you build and locked when the ticket fills.
Why did my multiplier change when I placed the ticket?
Multipliers lock when the ticket fills on the next oracle update, not at the price you saw while building. If the market moved between those moments, the multiplier moved with it. You can see the locked value on the ticket before it runs.
What if one leg misses early?
The ticket is dead the moment any leg misses. The remaining legs stop mattering and the stake goes to the treasury.
Can I cash out a live ticket?
Not at launch. Cash-out, selling a live ticket back to the treasury at a discount to its current value, is a candidate for a later version. See the Roadmap.
Can I put two legs on the same asset?
No. One leg per asset per ticket. A second leg from the same cluster in the same window gets a reduced multiplier, because correlated legs are more likely to hit together than the maths assumes.
Is there a maximum payout?
Yes: the larger of 10 percent of available treasury and a floor, proposed at $5,000. If your ticket would exceed it, the app lowers the maximum stake it accepts. The current max is always visible.
What happens if the oracle doesn't report?
The leg is voided and removed from the combined multiplier. The ticket continues with the remaining legs. If fewer than three remain, the ticket is refunded.
Money and the token
What fees are there?
None outside the multiplier. No ticket fee, no payout fee. The house edge, proposed at 5 percent per leg, is inside every multiplier and it compounds across legs. A five-leg ticket carries about 23 percent total margin.
Where do payouts come from?
The treasury, which is funded by dead tickets. It pays every winning ticket in full, on the spot. The total potential payout of all live tickets is capped as a multiple of treasury equity, so there are never IOUs.
What is the token?
A zero-supply token minted to players for every dollar of dead tickets. No presale. The mint rate falls as the treasury grows, and a share of treasury growth buys and burns it. Rewards can be worth less than the ticket you lost. See the Token page.
Do I need the token to play?
No. Tickets are bought with the stake currency. The token is a by-product of losing, not an entry requirement.
Fairness
Can the house influence whether a leg hits?
No. Every leg settles from oracle prices with no human judgement. Short windows use time-averaged settlement prices so a single tick at the close can't decide a ticket.
Are the probabilities fair?
They're estimates from recent volatility and the window length, with a stated edge on top. If our estimates lag reality, sharp players will find the mispriced legs, which is why per-leg exposure limits exist. The pricing method is published in the Docs.
Is the contract audited?
It has to be before mainnet. Unaudited code holding deposits is the fastest way to lose other people's money, and that is written into our own risk list.
What stops someone gaming correlated legs?
One leg per asset, cluster haircuts for same-cluster legs in the same window, and exposure caps. The cluster definitions are tuned against real data and are an open question until they are.
Accounts and regions
Where is Legs available?
Only in regions where legal review has cleared it. Retail binary options are banned or restricted in many places, including the US and the EU, so Legs is geofenced from day one. See Eligibility and regions.
Is there an age limit?
18, or the higher age your region sets, with verification where the region requires it.
Will you ever ask for my seed phrase?
Never. Not in the app, not on this site, not by email or direct message. Anyone who does is not us.
Can I set limits on myself?
Yes. Daily, weekly and monthly stake caps, time-outs and self-exclusion are in settings. See Responsible play.
I found a bug or exploit. What do I do?
Report it privately through Support. Anything that could affect a payout is treated as a security report, and we credit reporters properly.
Ruleset v0.1
- Four leg types, 5 percent edge, cluster rules, treasury loop
- Zero-supply token design
- Legal review scoped by region
Simulation
- Backtest every leg type across assets and windows
- Tune cluster definitions and correlation haircuts
- Stress the treasury against worst-case variance
Testnet
- Ticket builder, live settlement, Hit / Live / Waiting states
- Contract audit
- Ruleset changelog goes live
Mainnet, gated
- Treasury seed and first max-payout floor
- Token mint begins with the first dead ticket
- Cash-out, if it earns its place
Open questions before building
- Exact cluster definitions and correlation haircuts.
- Minimum and maximum leg counts, and whether two-leg tickets are allowed.
- Shortest window the oracle can settle fairly.
- Whether cash-out ships at launch or later.
- Treasury seed size and the first max-payout floor.
Support and contact
Real people, real settlement records, no bots explaining rules at you.
Player support
Account problems, tickets, settings, general questions.
Response target: 2 business days.
Dispute a settlement
Every leg settles from a recorded oracle price. Send the ticket id and we'll show you the settlement record.
Response target: 5 business days.
Security and exploits
Found something that could affect a payout or the treasury? Tell us privately. Treated as a security report, credited properly.
Responsible play
Limits, time-outs and self-exclusion are in settings. If you need to talk to someone, regional help lines are listed inside the app.
Service status
All systems operational
Live status, incident history and the ruleset changelog are linked here when testnet opens.
Before you write in
Check the FAQ, it covers most ticket questions. Have your ticket id ready for settlement disputes. Never send seed phrases, private keys or passwords. We won't ask.
1. Who we are and what these terms cover
Legs is operated by Legs Labs Ltd. ("Legs", "we", "us"). These terms govern your use of the Legs app, website and any content we provide (together, the "Service"). By creating an account or placing a ticket, you agree to these terms, the Privacy policy, the Fair play policy, the Responsible play policy and the Eligibility and regions rules, all of which are part of this agreement.
2. Eligibility
You must be at least 18, or the higher age of majority or legal age for this kind of product where you live, to use the Service at all. Practice tickets and real tickets are both restricted to adults.
Real tickets are only available where we have enabled them for your region after legal review, and only after you complete any identity verification we require.
You may not use the Service if you are barred from doing so under the laws of your region, if you have been excluded from Legs, or if you have self-excluded and the exclusion period has not ended.
We use location and device signals to enforce regional rules. Circumventing those controls, including with a VPN or proxy, is a breach of these terms and voids any ticket placed while doing so.
3. Your account
You need an account to place tickets. Keep your login details secure. You are responsible for activity on your account. One account per person. Accounts are personal and cannot be sold, lent or shared.
We will never ask for your wallet seed phrase, private keys or password in the app, on this site, by email or by direct message. Anyone who does is not us.
4. Practice tickets
Practice tickets, testnet assets and non-withdrawable credits ("Practice Assets") have no monetary value, cannot be withdrawn, exchanged, sold or transferred outside the Service, and can be reset or adjusted by us at any time.
5. Real tickets
To place a real ticket you pay the stake shown in the builder in the supported currency for your region. The stake is final once the ticket fills. There are no refunds for a ticket that is live or dead, other than as described under Settlement.
Before you confirm, the builder shows each leg, its window, its multiplier, the combined multiplier, the stake, the payout if every leg hits, and the maximum payout currently allowed. Multipliers shown while building are indicative and lock at fill, on the next oracle update after you confirm.
The maximum payout per ticket and the maximum stake we accept are set by treasury rules described in the Docs and may change between tickets. We never accept a ticket whose potential payout we could not cover.
6. Settlement
Every leg settles from the designated oracle price for its window using the rules in the Docs, including time-averaged settlement for short windows. Settlement is automatic and final. We do not adjust settled legs for price disagreements with other venues.
If the oracle fails to report for a leg, that leg is voided and removed from the combined multiplier; if fewer than three legs remain, the ticket is refunded. If a ticket fails to fill, the stake is returned.
The first missed leg makes the ticket dead and the stake becomes treasury property. If every leg hits, the payout is sent to your account immediately from the treasury.
7. Fees and payouts
There is no ticket fee and no payout fee at launch. The house edge is built into each leg's multiplier and is disclosed in the Docs. If cash-out ships, its spread will be shown before you confirm a cash-out. Network transaction costs, where applicable, are yours.
8. The token
The Legs token is minted to players according to the rules in the Docs. It carries no claim on the treasury, no right to payouts, no voting rights and no promise of value. Its treatment varies by jurisdiction and it may be unavailable in your region.
9. Fair play
You agree to the Fair play policy. In short: no oracle manipulation, no exploiting settlement timing, no coordinated correlated tickets designed to drain the treasury, no wash tickets placed to farm the token, no automation that breaches rate limits, no account sharing and no interference with our systems. Confirmed breaches void the affected tickets and result in suspension or permanent exclusion.
10. Suspension and termination
We may suspend or close your account for breach of these terms, for legal or regulatory reasons, or to protect other players or the treasury. Live tickets on a suspended account settle normally unless they were placed in breach, in which case they are voided and the stake handled as the Fair play policy describes. You can close your account at any time from settings.
11. Disclaimers
Legs is entertainment with a known house margin. It is not an investment product, not financial advice and not an edge. Most tickets die. Nothing on the Service is an offer or recommendation to buy or sell any asset.
The Service is provided as is. We do not guarantee uninterrupted availability, and oracle or network outages can affect settlement as described above.
12. Liability
To the fullest extent the law allows, our total liability to you for any claim arising from the Service is limited to the stakes you paid for the tickets in dispute. We are not liable for indirect or consequential loss. Nothing in these terms limits liability that cannot be limited by law.
13. Disputes
Contact Support first with your ticket id. Settlement disputes are reviewed against the recorded oracle data with a second reviewer. Governing law and forum are set out in the regional terms for your jurisdiction.
14. Changes
We may update these terms and the ruleset. Ruleset changes are versioned in the Docs changelog, and every ticket records the ruleset it ran on. Material changes to these terms are announced in the app and by email before they take effect. Continued use after that date is acceptance.
1. What we collect
You give us
- Account details: email, display name, password (hashed).
- Waitlist sign-ups: email and, if you tick it, a changelog subscription.
- Support requests and settlement disputes: whatever you write, plus the ticket id.
- For real tickets in regions that require it: identity verification details collected by our verification provider, and a wallet address for stakes and payouts. We never collect seed phrases or private keys.
We collect automatically
- Ticket data: legs, windows, locked multipliers, stake, fill time, settlement prices, outcome, ruleset version. This is the ticket record and it is what makes auditable settlement possible.
- Device and connection data: device type, operating system, browser, IP address, approximate region derived from IP.
- Integrity signals: timing anomalies, rate patterns, client integrity checks.
- Site analytics on this website, only if you allow analytics cookies. See the Cookie policy.
2. How we use it
- To fill, run and settle tickets, and to show you results and history.
- To detect and prevent oracle manipulation, wash tickets, fraud and abuse.
- To enforce age, region and eligibility rules, including self-exclusion.
- To provide support and review settlement disputes against the recorded oracle data.
- To send account and service messages, and marketing you've opted into.
- To improve pricing, cluster rules and the product.
- To comply with law, including anti-money-laundering obligations where real tickets operate.
Where data-protection law requires a legal basis, we rely on performing our contract with you, our legitimate interests in running a fair and secure venue, your consent where we ask for it, and legal obligations.
3. Who we share it with
- Service providers who host our servers, deliver email, verify identity, and supply oracle data, under contracts that limit what they can do with the data.
- Blockchain networks: stakes, settlements and token mints are recorded on the relevant network and are public by nature of that network.
- Authorities and regulators where the law requires it.
- A buyer or successor if Legs is ever sold or merged, under the same commitments.
We do not sell personal data, and we do not show third-party ads inside the app.
4. How long we keep it
- Account data: while your account exists, then deleted within 30 days of deletion.
- Practice ticket records: 12 months, then aggregated.
- Real ticket records and settlement data: for the period the law requires where you live, then deleted or anonymised.
- Self-exclusion records: for the exclusion period plus any period the law requires.
5. Your choices
- Access, export, correct or delete your data from settings, or by contacting privacy@legs.fun.
- Opt out of marketing at any time with the link in every email.
- Turn analytics cookies off at any time. They are off by default.
- Some data cannot be deleted while a ticket is live, while a dispute is open, or while the law requires us to keep it.
6. Security
Passwords are hashed. Data in transit is encrypted. Access to production data is limited and logged. No system is perfectly secure, and if a breach affects you we will tell you as the law requires.
7. Contact
privacy@legs.fun.
Legs is entertainment with a known house margin. The maximum loss on any ticket is the stake, and these tools exist to keep the stake something you can afford.
Built-in limits
- Stake caps. Every ticket has a maximum stake, set per region and by treasury rules. There are no high-roller tiers.
- Spending limits. Set a daily, weekly or monthly cap on total stakes in settings. Lowering a limit applies immediately. Raising one takes effect after a 24-hour cooling period.
- Session reminders. A reminder after every hour in the app showing tickets placed and net result.
- Time-outs. Block yourself from real tickets for 24 hours, 7 days or 30 days. Practice tickets stay available.
- Self-exclusion. Exclude yourself for 6 months, 1 year or permanently. This cannot be reversed early and we may share it with regional exclusion schemes where they exist.
- Reality check. Your lifetime net result is always one tap away in settings.
How the product itself helps
- A ticket only ever costs the stake. Nothing can be added once it fills and there is no margin call.
- The house margin is printed in the Docs, not hidden in the odds.
- No one-tap re-buy. Every ticket is built and confirmed from scratch.
- The maximum payout is capped and visible, so the headline number is never a fantasy.
Signs to watch for
Placing tickets to win back losses, staking money you need for other things, hiding play from people close to you, or feeling anxious when you're not playing. If any of that sounds familiar, use a time-out and talk to someone.
Getting help
Free, confidential support services exist in most regions. We list the relevant ones for your region inside the app under Settings, Responsible play.
Minors
Legs is for adults only and is verified in regions that require it. If you're a parent or guardian and believe a minor has used the app, contact Support immediately. We remove the account and refund unsettled stakes.
Fair play and integrity
Settlement nobody can argue with, and a treasury nobody can drain.
What's not allowed
- Manipulating, or attempting to manipulate, any price feed the oracle relies on around a window close.
- Exploiting settlement timing, oracle delay or a pricing bug to place tickets with a known edge. Report it instead.
- Coordinated correlated tickets across accounts designed to bypass the one-leg-per-asset and cluster rules.
- Wash tickets placed to die on purpose to farm the token.
- Automation that breaches rate limits or places tickets on behalf of others.
- Account sharing, boosting or selling.
- Circumventing region, age or exclusion controls.
How we enforce it
- Oracle-only settlement. No human decides whether a leg hit. Short windows use time-averaged prices around the close.
- Locked multipliers. Multipliers lock at fill on the next oracle update, so nothing can be picked off between building and placing.
- Exposure caps. Per leg, per ticket, per address and per venue. A mispriced leg can only do so much damage.
- Anomaly detection. Statistical models flag unlikely patterns across tickets and accounts, including correlated-ticket signatures.
- Recorded settlement. Every real ticket keeps its oracle inputs and the ruleset version it ran on, so any dispute can be replayed.
What happens if you're caught
- Affected tickets are voided. Stakes on voided tickets are returned unless the ticket was placed to attack the treasury, in which case they are forfeited.
- First confirmed offence: 30-day suspension.
- Any confirmed attack on the treasury or oracle: permanent exclusion and, where the law requires it, a report to the relevant authority.
- You can appeal any enforcement action through Support. We review the settlement record with a second reviewer.
Reporting
Report a pricing or settlement problem from the ticket screen with the ticket id. Report an exploit privately through Support; it's handled as a security report and we credit reporters who help keep the treasury honest.
Age
| Activity | Minimum age | Verification |
|---|---|---|
| Practice tickets | 18, or the higher legal age in your region | Self-declared at sign-up |
| Real tickets | 18, or the higher legal age of majority or legal age for this kind of product in your region | Identity verification where the region requires it, before your first real ticket |
Region status
Each leg is a binary option. Retail binary options are banned or restricted in a lot of places. Real tickets open region by region after legal review, and are geofenced from day one. This table is updated as regions change. If your region isn't listed, real tickets are not available there.
| Region | Practice tickets | Real tickets | Notes |
|---|---|---|---|
| Everywhere the app is distributed | Available | Not yet | Practice tickets while the treasury seeds |
| United States | Available | Not available | Retail binary options are restricted |
| European Union | Available | Not available | Retail binary options are restricted |
| United Kingdom | Available | Not available | Retail binary options are restricted |
| Other regions | Available | Under review | Legal review in progress |
What "under review" means
Specialist counsel is determining, for that region: whether the product can operate; age rules; KYC and AML requirements; how binary options and the token are treated; custody structure; geofencing; and platform-store restrictions. Real tickets open only when all of those are settled and any required licences are held.
Location and circumvention
We use IP, device and, where you allow it, precise location to confirm you're in an enabled region. Using a VPN, proxy or spoofed location to place real tickets breaches the Terms, voids the affected tickets and may result in permanent exclusion.