Beta
    Responsible trading utility
    Facts file verified 2026-04-22

    How to Self-Exclude From Prediction Markets

    The fastest honest guide to creating friction, checking what protection exists now, and spotting the wrapper gaps that many users miss.

    Native tool available

    Kalshi has live responsible-trading tools today.

    Cross-platform coverage

    Real, but uneven. Integration status still matters venue by venue.

    Wrapper gap risk

    High confusion area. Exchange tools do not automatically cover every app or partner path.

    Best immediate action

    Use the strongest live friction path now, then verify coverage details before assuming you are fully blocked.

    Maintained coverage note

    This page tracks current exclusion coverage and source links. It is only as good as the latest verified platform documentation, so treat the tracker as a live map, not a blanket guarantee.

    SelfExclude official site

    If you landed here because you know you have a problem

    If you have landed on this page because you know your trading behavior is no longer under your control — not because a platform locked you out, not because a balance looks wrong, but because you recognize a pattern in yourself — you are in the right place. The rest of this page is the set of practical tools.

    The first call, if you need it right now, is the National Problem Gambling Helpline: 1-800-522-4700 (call or text, 24/7).

    Quick decision path

    Pick the path that matches the actual problem. The point is fast action with clear eyes, not more platform jargon.

    Need friction right now

    Use the strongest live tool available today, not the most comforting theory.

    • Start with a native platform tool if your venue offers one right now.
    • Use SelfExclude when you also need broader cross-platform friction.
    • Close unwanted positions first if the source warns that trading access may fully lock.

    Trying to block wrapper re-entry too

    This is where users get burned by assumptions. Wrapper coverage is not the same as native platform coverage.

    • Check the coverage tracker before assuming an exchange tool covers the app you actually use.
    • Look for explicit wrapper or partner language, not vague safety wording.
    • Treat unverified wrapper coverage as a live gap, not a maybe-it-is-fine detail.

    Not ready to exclude, just want a cooldown

    If you want friction without a full lockout, a trading break may be the right first move.

    • Cooldown tools are better than vague promises to yourself.
    • They are still platform-specific and may not follow you elsewhere.
    • Use them to interrupt behavior fast while you decide whether stronger protection is needed.

    Need help now

    If the issue is bigger than account settings, skip the jargon and get support.

    • Use support resources if trading is affecting sleep, money, work, or relationships.
    • The goal is friction, not perfection.
    • You do not need to wait until things look catastrophic to use help.

    Coverage tracker

    This is the main answer. Check native tools, network participation, wrapper gap risk, and the best immediate action before assuming one safety rail covers every route back into the market.

    Kalshi

    Integrated

    Native tool

    Trading break, Voluntary self-exclusion, Personal funding cap

    Native tools act on the platform flow immediately; SelfExclude says network enforcement propagates within 24 hours after verified submission.

    Network coverage

    SelfExclude integrated

    Wrapper gap risk

    Partial

    Native Kalshi tools do not automatically confirm that partner or wrapper routes are blocked.

    Best immediate action

    Use Kalshi's native responsible-trading tools immediately, then use SelfExclude if you also need broader network friction.

    Open positions

    Users should close positions they do not want to hold before self-excluding or starting a trading break.

    Source

    Last verified 2026-04-14

    Robinhood

    In progress

    Native tool

    No confirmed native tools yet

    Pending verification once integration is live.

    Network coverage

    SelfExclude in progress

    Wrapper gap risk

    Gap risk

    Wrapper exposure is the core unresolved risk until official integration and coverage terms are published.

    Best immediate action

    Do not assume Robinhood wrapper access is blocked yet. Use the strongest live exclusion path you already have and verify current support coverage directly.

    Open positions

    Pending verification once integration is live.

    Source

    Last verified 2026-04-14

    Polymarket

    In progress

    Native tool

    No confirmed native tools yet

    Pending verification once integration is live.

    Network coverage

    SelfExclude in progress

    Wrapper gap risk

    Gap risk

    Do not infer category-wide blocking from a roadmap mention or partner list alone.

    Best immediate action

    Treat network protection as directional, not complete, until integration details and enforcement terms are explicitly live.

    Open positions

    Pending verification once integration is live.

    Source

    Last verified 2026-04-14

    ProphetX

    In progress

    Native tool

    No confirmed native tools yet

    Pending verification once integration is live.

    Network coverage

    SelfExclude in progress

    Wrapper gap risk

    Unknown

    Partner and wrapper implications remain unclear until official documentation is published.

    Best immediate action

    Verify the live exclusion path before assuming support exists. Use available native or network tools only when current documentation confirms them.

    Open positions

    Pending verification once integration is live.

    Source

    Last verified 2026-04-14

    What this does not guarantee

    One pause path may not close every route back in

    A native platform break can leave wrapper or partner access untouched unless the source explicitly says otherwise.

    Cross-platform enforcement may not be instant

    Network exclusions can require identity verification and propagation time before every integrated venue reflects the change.

    Open positions are handled differently

    Some tools let you close risk, some may block all trading actions, and wrapper behavior can differ from the core exchange.

    Identity matching still matters

    Account-linking limits, partner structures, and partial integrations can create coverage gaps even when a protection rail exists.

    Wrapper gap reality check

    Native platform exclusion

    Best for locking a single platform quickly. Strong friction, but it does not automatically mean every partner or wrapper route is blocked.

    Cross-platform network exclusion

    Best for broader category friction when a platform is integrated. Coverage depends on which venues currently participate and how quickly enforcement propagates.

    Wrapper or partner access

    Highest confusion risk. A user can assume they are blocked because the exchange has a tool, while an app or FCM path may behave differently unless explicitly covered.

    Which protection path is best for what?

    A platform pause and a network pause are not the same thing. Use the smallest honest label for what you are actually activating.

    Trading break

    A short cooldown when you want friction fast but are not committing to a long exclusion window.

    Native self-exclusion

    A harder stop on a single platform when the venue offers it directly.

    Network exclusion

    Broader category friction when an active cross-platform partner actually participates.

    Open positions and enforcement timing still need attention

    The safest answer is the honest one: some protection exists, but coverage is still uneven. If you have live positions, check the source terms before you activate a break or exclusion.

    • Close positions you do not want to hold before starting, when the source allows it.
    • Do not assume a wrapper app will match the core platform's close-position policy.
    • Network enforcement can take time to propagate after verification.

    Help now

    If trading is messing with sleep, money, or relationships, skip the platform decoding and get support.

    Kindbridge

    Behavioral health support for people whose trading or gaming behavior is starting to feel out of control.

    Birches Health

    Treatment and guidance for gambling-related concerns if you need a more formal support path.

    National Problem Gambling Helpline

    Call or text 1-800-522-4700 if you need immediate human support.

    Frequently asked questions

    The page should help you act fast, not decode platform jargon.

    Related next steps

    Use the page that matches the real failure mode, not the one with the scariest headline.

    State checker

    See whether platform access is changing because of where you live, not because a trade or balance view looks weird.

    Kalshi or Polymarket chooser

    If you are not trying to stop completely, decide which platform structure fits your risk tolerance better.

    Is Kalshi safe?

    Review trust, regulation, and platform safeguards on the venue with the clearest native exclusion tools today.

    Prediction markets legitimacy guide

    Separate category legitimacy from the narrower question of whether real protection tools exist.

    Kalshi payout size-up explainer

    If the immediate issue is confusing fills and payout math, start there instead of assuming the platform is malfunctioning.

    Coinbase winnings visibility

    Use this if your concern is where the money shows up, not whether your account should be paused.

    Robinhood missing trade recovery

    Use this when the fear is that a trade vanished, not that you need to shut the door for a while.

    Prediction-market self-exclusion is real, but coverage is uneven. Platform-native tools, wrapper access, and cross-platform networks do not all block the same thing. The honest goal is friction, not perfection.