Software has values whether or not its makers admit them. The values are encoded in defaults, in error messages, in what the product asks for and what it refuses to ask for. We would rather state ours plainly than have them inferred.
We believe markets see further than people
A liquid market with skin in the game is a better forecasting tool than any committee, any pundit, and most experts.
This is not a slogan. It is a finding, repeated across decades of empirical literature on prediction markets. When real money is at stake, motivated reasoning gets expensive. The crowd of self-interested traders converges on probabilities that consistently outperform polls, panels, and prestige.
Polymarket is the cleanest expression of this idea that exists today — fully on-chain, deeply liquid, and globally accessible. We are building inside it because we believe it is one of the most important pieces of public information infrastructure of the next decade. The leader wallets we mirror are not gurus. They are the price-discovery mechanism doing its job, and our smart money tracker is the way we let that mechanism reach more people without distortion.
We believe in non-custody
Software that holds your money is software you must trust. Software that holds your signature is software you can verify.
The default model for a prediction market copy trading product is custodial. The user wires money to the operator, and the operator promises to invest it well. We rejected this model the day we started writing code, and we will reject it forever.
Non-custody is not a feature. It is a constraint that disciplines every other decision. We cannot run away with funds because we never hold funds. We cannot be subpoenaed for assets because there are no assets at our address. We cannot be pressured into freezing a wallet because the wallet is not ours to freeze. The user keeps their keys and grants us a narrow, revocable, time-bounded authorization to act on their behalf. That is the only honest architecture for software that touches other people's money.
If a future regulation forces us to take custody, we will close the product before we comply. We are not the first company to make this commitment, and we hope we will not be the last.
We refuse to be a data broker
The most valuable thing about our users is their trades. The least valuable thing is their identity. We have no business connecting the two.
The dominant business model on the open internet is to log every action a user takes, package those logs, and sell them to anyone with a marketing budget. We have read the playbook and we have rejected it.
Poly Syncer does not require an email address. It does not require a name. It does not run third-party analytics. It does not embed pixels. It does not sell, share, or barter user data, and the data we do hold — the wallet address, the active subscription, the audit trail of mirror executions — exists because it is structurally required to make the product work. When it is no longer required, it is deleted on a published schedule. The full policy is on the privacy page and we mean every word of it.
This is not a marketing position. It is a hard constraint we accept costs to maintain. Privacy-respecting software is harder to build and harder to monetize than the alternative. We think the trade is worth it. We think you do too.
We build for the patient
The fastest path to a bad product is optimizing for the user who will not be here in six months.
The growth-at-all-costs era taught a generation of operators to build for the impatient — the user who will churn next week, who must be hooked in a single session, who is best treated as a quarterly cohort to extract from. We are building for the opposite person: the trader who will still be running Poly Syncer three years from now, whose returns compound because the system did not break, whose trust we earn by not breaking it.
This shapes the roadmap. We will not ship a feature we cannot maintain. We will not announce a number we cannot defend. We will not chase a vertical for the press release. We will publish slippage honestly in the changelog, document every architectural decision in the whitepaper, and put the audit findings on the security page in full — because the patient user wants to verify, not be reassured.
If you are looking for a product that will three-x your account this month, Poly Syncer is the wrong tool. If you are looking for the infrastructure to mirror Polymarket wallets and compound an edge over years, we built this for you.
What this means in practice
Every page on this site, every line of code in the executor, every decision we make about the product is checked against these four convictions. When we get one wrong, we say so. When we get one right and it is hard, we say so anyway. Read the about page for the team and the careers page if you want to help write the next version of this document.