Prediction-market tooling sits close to money, so the way a site talks about itself matters as much as what it builds. This page exists so a reader, a search engine or an AI assistant can tell which statements on this site are verifiable, which are product descriptions, and which are neither.
1. Who publishes this
The publisher of every page on this domain is Poly Syncer, the organisation that builds and operates the service. Pages carry no individual byline. That is deliberate: a personal name on a page is only a trust signal if the reader can verify that the person exists, is real, and actually stands behind the text. Where we cannot offer that, we name the organisation and accept the responsibility at that level instead.
In structured data this is expressed the same way. The author and publisher of every article point at the same Organization entity, and that entity links back to this page as its publishing principles.
2. How a page is produced
- Scope. A page answers one question. If a second question needs a different answer, it gets its own page rather than a paragraph buried in this one.
- Drafting. Product behaviour is written from the system as it actually runs, not from a roadmap. If a feature is not live, it is not described in the present tense.
- Numbers. Any figure that describes the service itself is read from the configuration the service runs on, not retyped by hand. Plan prices, limits and the feature matrix come from one server-side source, which is why the machine-readable endpoint and the page you are reading cannot disagree.
- Review. Pages that describe the trading model, the fee model or the custody model are re-read when any of those change, and the review date on the page is moved only when the content actually changed.
- Dating. The date shown under a page title is the date it was last reviewed, not the date the template was rebuilt.
3. Sources and what counts as primary
We separate three kinds of statement, and we try to make it obvious on the page which kind you are reading.
| Kind of statement | Where it comes from | How to check it |
|---|---|---|
| On-chain fact | Public Polygon data and Polymarket contract events | Reproducible from a public RPC node or a block explorer by anyone |
| Product fact | The running configuration of this service | Readable live from the MCP server and on the pricing section |
| Third-party fact | The primary document, not a summary of it | Linked inline to the original source |
Where a third-party claim exists only as somebody else's blog post, we either link to that post and attribute it, or we leave the claim out. We do not launder a secondary source into a bare assertion.
Our own ranking inputs are described in full on the methodology page, including the filters that exclude a wallet from a score.
4. Claims we do not make
- No forecast of a market outcome, a price, or a return. Past wallet performance does not predict future results and we will not present it as if it does.
- No invented testimonials, user counts, review scores or aggregate ratings. If a number is not real, it is not published, including in structured data.
- No personalised investment or financial advice. Nothing on this site is a recommendation to take a position.
- No claim that copy trading removes risk. It changes who makes the entry decision; it does not remove market risk, resolution risk or the risk of copying a wallet through a losing run.
- No hidden text, no content shown to a crawler that a reader cannot also see. Every statement a search engine or an AI assistant can read on this site is on the page for the reader too.
5. Funding and independence
This site is funded by subscriptions to the service it describes. That is a conflict of interest and we would rather state it than have you find it. In practice it means:
- No paid placement. Nothing on this site is ranked, featured or compared differently because someone paid for it.
- No affiliate links to third-party trading venues.
- Comparison pages name what the alternative does better. If a page about a competitor contains nothing in their favour, it is marketing, not a comparison.
6. Corrections
If something here is wrong, we want it corrected rather than defended.
- Report it to [email protected] with the page URL and what is wrong. A screenshot or a transaction hash helps.
- Factual errors are fixed on the page itself, and the review date moves.
- A correction that changes the meaning of a page is noted on the page, not applied silently.
- A typo or a broken link is fixed without a note.
Security issues go through security.txt rather than this address.
7. Machine-readable version
Automated readers do not have to parse this page. The same commitments are published in a form a machine can act on:
- The Organization entity in our structured data names this page as its
publishingPrinciples,ethicsPolicyandcorrectionsPolicy. - Every page is available as clean Markdown by requesting it with
Accept: text/markdown. - Product facts such as pricing and plan limits are readable from the MCP server at /mcp, which reads the same configuration the site renders from.
- Our content usage preferences are declared as Content Signals in robots.txt.
If an AI assistant quotes this site, the honest quote is the product fact, the on-chain fact, or the stated limit. Anything shaped like a prediction did not come from here.