PolyMiniWar Wallet Security

Our Security Commitment

PolyMiniWar (PMW) lets you take part in Polymarket's Bitcoin 5-minute Up/Down markets in a way that feels close to playing a game. Behind that lightweight experience, our approach to protecting your assets comes down to a single principle: we never hide your private key, your transaction signing, or your fund status inside an opaque black box.

In concrete terms, PMW's core commitment is this:

Your wallet's private key is never stored in the PMW desktop app, never stored in your computer's local cache, and never stored in PMW's database.

Your private key is held by Privy, a dedicated wallet infrastructure provider. Every transaction must pass through identity verification and rule checks on the PMW backend, as well as Polymarket's official trading flow, before it is actually submitted.

This means that even if someone obtains the files of the PMW desktop app, or reads the local cache on your computer, they cannot take your wallet's private key or your assets from those alone. Our security is built on layered permissions and backend verification — not on the unreliable assumption that "no one can see the frontend code."

Who Is Responsible for What

PMW's handling of assets is divided into several layers, each with a clear responsibility. You don't need to memorize these details, but understanding them helps make one thing clear: no single layer can move your assets on its own.

Every action — placing a bet, selling, winning or losing, claiming, depositing, withdrawing — leaves a traceable record.

How Your Assets and Private Key Are Protected

Where your assets are

The "available funds" and "total assets" you see in PMW are not a separate pot of money that PMW holds on its own. They are the combined result of several real states: the actual funds in your Polymarket trading wallet, the detailed record PMW keeps of each of your transactions, and the final outcome after syncing with Polymarket's on-chain status.

PMW never adds to or deducts from your assets out of nowhere. While Polymarket or the on-chain status is still syncing, the interface shows clear states such as "Processing," "Pending sync," or "Awaiting official confirmation" so you are never misled.

How your private key is protected

Your private key never enters the PMW desktop app. The desktop app only stores the login state used to prove "who is currently logged in" — and that information cannot, on its own, be used to sign any transaction.

The actual signing capability is obtained by the PMW backend through Privy in a controlled manner. The secret keys required to authorize signing are all kept server-side and are never bundled into the desktop app you download.

Signing is limited to the transactions PMW needs

Even when signing happens on the backend, we add an extra layer of restriction rules to ensure that signing capability can never be misused:

• Exporting the private key is forbidden — any attempt to export your private key is denied outright.
• Only Polymarket order signing is allowed — signing can only be used for Polymarket's official trades; it cannot be used to sign other unknown or unfamiliar content.
• Only necessary destinations are allowed — funds can only flow to the small set of designated addresses required for Polymarket trading, and cannot be sent to unfamiliar contracts or chains.

In other words, even if the signing layer is targeted, what it is able to do is firmly confined to the scope of "the transactions PMW needs." We will also continue to strengthen this layer of restriction, so that it controls not only "where funds can go" but increasingly "what operations can be performed."

How Betting and Trading Are Protected

When you tap BUY or SELL, the signing is not done by your computer.

Here's what actually happens: your desktop app only sends a request along the lines of "what I want to buy/sell, and the amount." The PMW backend then verifies your identity, confirms your subscription plan and balance, and checks whether Polymarket's trading status is healthy. Only then does it submit the order through controlled signing and Polymarket's official trading flow.

So transaction signing takes place in the integration between the backend and Polymarket — not on the desktop screen you see.

From login to placing a bet, the overall flow looks roughly like this:

flowchart TD
  A[Log in to PMW with Google] --> B[Activate your Privy wallet]
  B --> C[PMW backend verifies identity, balance, and trading status]
  C --> D[Wallet ready — you can place a bet]
  D --> E[You tap BUY UP / BUY DOWN]
  E --> F[Backend checks the rules and completes controlled signing]
  F --> G[Order submitted to Polymarket]
  G --> H{Polymarket response}
  H -- Filled --> I[Recorded in your ledger; shown instantly on screen]
  H -- Not filled --> J[No position created; reason explained]
  H -- Rejected --> K[Clear error reason returned]

How selling (SELL) is protected

Selling uses the same security mechanism as buying — the only difference is the data source: selling uses the positions you currently actually hold.

Before submitting a sell order, the backend first confirms that your trading wallet really does hold a sellable position. If it doesn't, PMW will not submit the sell order and will simply tell you that there is "no sellable position right now."

flowchart TD
  A[You tap SELL] --> B[Backend confirms you actually hold a sellable position]
  B --> C{Sellable position exists?}
  C -- No --> D[Tells you there's no sellable position; no order sent]
  C -- Yes --> E[Completes controlled signing and submits to Polymarket]
  E --> F{Polymarket response}
  F -- Filled --> G[Sell recorded in your ledger]
  F -- Not filled --> H[Tells you it was not filled]
  F -- Rejected --> I[Clear error reason returned]

How We Keep Every Step Understandable

PMW is not designed to make you trust a black box. It is designed so that you can understand exactly what is happening at every step.

Every one of your activities — buy, sell, win, lose, claim, deposit, withdraw — is saved as a separate record that does not overwrite the others. This means a buy is never overwritten by a later sell, funds recovered from a mid-round sell are never mixed up with the final win or loss, and an order that didn't fill is never mistaken for one that did. Even Polymarket's official settlement can only be used to correct status — it cannot overwrite your real transaction records.

Behind these records, the system also keeps complete technical data for tracing. Its purpose is not to make your actions more complicated, but to quickly answer the most important questions if something ever goes wrong — for example: Did this transaction actually reach Polymarket? Was it not filled, rejected, short on balance, or blocked by a security rule? Where exactly is a withdrawal stuck, and has it been sent?

In short: PMW will never leave you guessing whether "the money disappeared." Every asset status should come with a clear on-screen explanation and a traceable record.

When Polymarket or the Network Has Issues

PMW has a built-in guard for Polymarket's status. When Polymarket's order matching or price feed becomes unstable, PMW will proactively pause betting, so you don't submit high-risk actions while the official pipeline is shaky.

In those moments you'll see a clear notice, rather than a button that quietly fails when you press it. Once things stabilize, PMW automatically reopens trading.

We also apply traffic protection to fund-related actions (such as claiming, withdrawing, and subscription charges), to reduce the impact of buggy loops, a single account spamming taps, or simple script abuse on the fund flow. Larger-scale network attacks are handled by Cloudflare at the outermost layer — every connection between you and PMW passes through Cloudflare's protection first, before reaching the PMW backend.

Protecting Your Account Data

If different accounts are switched on the same computer, PMW clears the wallet-state cache that does not belong to the currently logged-in user, ensuring that account A never sees account B's wallet data.

In addition, for ordinary outbound responses, we have removed unnecessary backend configuration information as much as possible to avoid exposing too much internal detail — while still keeping, on the backend, the records needed to investigate fund-flow issues.

Even If the Desktop App Is Cracked, Your Assets Stay Protected

We honestly assume that someday, someone may try to take the PMW desktop app apart. Even so, the most they could see is things like the app's operating logic and the format of the local cache — but they cannot directly obtain your wallet's private key, nor any of the backend's secret keys.

Even if they obtained some short-lived login credential, moving any assets would still require passing through, one after another: identity verification on the PMW backend, the account-binding check, the trading-rule and subscription-plan checks, Polymarket's status and balance checks, and the signing restriction rules described earlier.

These layered defenses mean no one can carry off your assets using frontend information alone.

The Trust Foundations We Rely On

PMW does not claim to be a one-hundred-percent invulnerable system. We believe that being honest about "which infrastructure we depend on" is more trustworthy than pretending to be infallible. The following layers are the key foundations of PMW's security:

• The PMW backend — handles identity verification, submits transactions, and carries out claims and withdrawals. It holds the secrets required for signing, and is the layer that needs the strictest protection.
• Privy — holds custody of your wallet and signing capability.
• The database — stores product data such as accounts, transaction records, and notifications, but does not store your private key.
• Polymarket — the place where market matching and settlement actually happen. PMW can display status and pause trading, but it cannot replace Polymarket's market settlement.
• Cloudflare and the deployment platform — Cloudflare is PMW's outermost line of defense, and every outbound connection passes through it first; the deployment platform keeps the service running steadily. This layer maintains service availability and basic traffic protection — it does not directly give anyone access to your private key.

As long as these core layers stay secure, your assets will not be directly exposed just because the interface, the chat system, the frontend cache, or local files are read.

Our Promise to You

PMW is a product built for small, frequent, 5-minute-paced trading. We won't slow down your experience with cumbersome steps — such as making you manually sign again for every single bet. The burden of security should be carried by the backend and the rule layer, not pushed onto you with every action you take.

We promise that, at any moment, you will be able to clearly know:

• Whether you're logged in, and whether your wallet is activated;
• How much you can currently bet;
• Whether a buy or sell was filled — and if not, why;
• Whether this round's outcome has been confirmed by Polymarket;
• Whether your gains are claimable, and whether they've returned to your available funds;
• Whether a withdrawal has been sent;
• Whether the Polymarket pipeline is healthy.

In this architecture — built around "layering" and "least privilege" — you don't need to hand your private key to the desktop app, and you don't need to deal with complex trading details yourself, in order to take part with peace of mind. That is PMW's commitment to the security of your assets.