Who publishes this site, where every figure comes from, what a deployment actually produces, the claims we refuse to make, and how an error gets fixed.
Reviewed: October 2026Every page on this domain is published by CreateTronToken as an organisation, not under a personal byline. The same people write the pages, maintain the contract template and answer the contact form, so there is one party to hold to everything below.
CreateTronToken is an independent service. It is not affiliated with the TRON Foundation, TronLink, Tronscan or SunSwap, and it does not speak for them.
The deployment fee on every page is the fee the form charges. It is one number held in one place, which is why the pages, the FAQ and the machine-readable endpoints cannot disagree with each other.
Anything describing Tron itself, such as transaction speed or fee levels relative to other networks, is a description of public network behaviour rather than a measurement we are publishing as our own.
A TRC-20 contract on Tron mainnet, owned by the address that signed the deployment transaction, with the parameters entered on the form and the optional features selected there. That is the whole deliverable.
Mint and pause authority are genuine centralisation risks. If they are enabled, the owner can create supply or halt transfers, and anyone can read that from the contract on Tronscan. We describe those switches rather than hide them.
No promise of demand, liquidity, holders or trading volume. A deployment writes a contract; it does not create a market.
No promise of a listing on any exchange, wallet list or screener.
No claim that a token is safe or legitimate because it was deployed here.
No price prediction, no valuation and no financial, investment or legal advice.
No invented statistics, testimonials, review scores or aggregate ratings. If a number is not real it is not published, including in structured data.
No hidden text, and nothing shown to a crawler that a reader cannot also see.
A page answers one question, and a second question gets its own page. Contract behaviour is described from the template as it is actually deployed, and a feature that is not implemented is not written in the present tense.
Pages describing the fee, the custody model or the contract features are re-read whenever any of those change, and the date on a page moves only when the content actually changed.
This site is funded by the deployment fee it charges. That is a conflict of interest and we would rather state it than have you find it. There is no paid placement anywhere on the site, and the comparison page names what each alternative does better, including where this service is not the right choice.
If something here is wrong we want it corrected rather than defended. Report it through the contact form with the page URL and what is wrong; a transaction hash or a contract address 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 rather than applied silently. A typo or a broken link is fixed without a note.
Every published page is available as clean Markdown by requesting it with an Accept: text/markdown header.
The MCP server at /mcp reads the same configuration the pages render from. Its get_limits tool exists so that an assistant can state what this service does not do without guessing, and get_contract_features describes the authorities a deployed token carries.
Content usage preferences are declared as Content Signals in robots.txt, and the agent entry points are listed in llms.txt and in the catalogue at /.well-known/ai-catalog.json.
