Acceptable use policy
What ScanZX may and may not be used for. This policy forms part of the terms of service, and breaking it can cost you your account. Last updated 9 August 2026.
In plain English
- Use ScanZX to inform decisions, not to manufacture confidence in a token.
- Sharing a report is fine. Editing one, or presenting it as an endorsement, audit or approval, is not.
- No market manipulation, pump-and-dump coordination, wash trading or sanctions evasion — with reports, alerts or the API.
- Automate through the documented API, within your plan’s allowances. Do not scrape the interface or split usage across accounts.
- Breaking this policy can cost you API keys, shared report links, or the account itself.
This summary is for orientation and is not the binding text. The numbered clauses below govern.
The principle
ScanZX exists to help people understand the risk signals attached to a token before they act. Everything in this policy follows from one idea: use it to inform decisions, not to manufacture confidence. If a use would make someone more likely to lose money because they trusted something you presented as more settled than it is, it is not acceptable use here.
Market conduct
You must not use ScanZX, its reports, its alerts or its API in connection with:
- Market manipulation of any kind, including spoofing, layering and ramping.
- Pump-and-dump coordination, whether you are organising it or supplying material for it.
- Wash trading or any activity designed to fabricate volume, liquidity or holder counts.
- Insider or front-running activity, including acting on a monitoring alert about a token you control ahead of holders who cannot see it.
- Evading sanctions, anti-money-laundering obligations or law enforcement, including using reports to screen for assets you intend to move for that purpose.
ScanZX provides no trading execution, token launching, presale, sniping or wash-trading capability, and none is planned. Do not build one on top of it.
How you may present a report
Reports are yours to share. What you may not do is change what they mean. Specifically, you must not:
- present a report as an endorsement, certification, audit or approval of a token — it is none of those, and describing it as one misleads whoever you show it to;
- edit a score, label, evidence item or confidence figure and continue to attribute the result to ScanZX;
- strip the limitations and context from a report and circulate the score alone, when doing so would give a materially different impression;
- present an old report as current where conditions have since changed, or re-run a scan repeatedly and publish only the most favourable result;
- imply that ScanZX has assessed something it has not, or that a low observed-risk result means a token has been checked and found sound;
- use our name, marks or report styling to suggest a partnership, sponsorship or review that does not exist.
If you publish or forward a report, keep it identifiable as a point-in-time observation. The risk disclosure explains why that framing matters.
Automated access and fair use
Plan allowances — scans, monitored tokens, monitoring frequency, exports, seats and API calls — are enforced by our servers and represent what we are able to supply. You must not:
- circumvent or attempt to circumvent allowances, rate limits or usage meters, including by creating multiple accounts or workspaces to obtain more free capacity than one user is offered;
- scrape or automate the web interface. Programmatic access is through the documented API, on a plan that includes it;
- share API keys outside your workspace, or use them on behalf of a third party as a disguised reseller;
- resell or redistribute bulk report data as a competing or derivative product;
- use our output to train a model that substitutes for the service.
Automation that stays within your allowances and the documented API is fine — that is what the API is for.
Security and other people’s data
- Do not probe, scan or test the security of ScanZX without our written permission, and do not attempt to access a workspace, report or account that is not yours.
- Do not interfere with the service or the infrastructure it runs on, including denial-of-service attempts and deliberately abusive request patterns.
- Do not upload malware, or content that is unlawful, defamatory, harassing, or infringes someone else’s rights.
- Do not use ScanZX to compile profiles of individuals, or to target, dox or harass the people behind a project. Reports concern contracts and market behaviour, not private lives.
- Do not impersonate ScanZX or anyone else, in the product or elsewhere. We will never ask for a seed phrase, a private key or a wallet connection — anything doing so in our name is not us.
If you believe you have found a security vulnerability, tell us before telling anyone else. Good-faith reports are welcome and we will not pursue you for making one.
Law
You are responsible for using ScanZX lawfully where you are. Cryptoasset rules vary by country and change. Do not use the service where doing so would breach sanctions, financial-promotion rules or any other law that applies to you, and do not use it to help someone else do so.
What happens if this policy is broken
Depending on what has happened and how serious it is, we may:
- contact you and ask you to stop;
- rate-limit, restrict or revoke API keys;
- revoke shared report links that are being used to mislead;
- suspend or close the account and workspace;
- report the matter to the relevant authority where we are required or entitled to.
We will normally warn you first. We will not where the breach is serious, unlawful, ongoing, or where warning you would let the harm continue. Closure for a breach does not entitle you to a refund of the current period, and the liability and termination provisions in the terms of service continue to apply.
Reporting misuse
If you have seen a ScanZX report being used to mislead people, or any other breach of this policy, tell us through the support screen in your account. Include the report link or account if you have it. We would much rather hear about it early.