Corrections policy

How a correction is made

A confirmed error is corrected in the body of the page and a dated note is added at the foot saying what changed. The note stays there, so a reader can see that the page was amended and when.

Nothing is corrected silently. A quiet edit would leave earlier readers holding a wrong figure with no way to know it had moved, which is worse than the original mistake.

How to report one

Send the page address, the exact sentence and what you believe is wrong to [email protected]. A link to the broker document that shows the correct position helps, because the desk checks against source documents rather than against other websites.

Every report is read. If the desk agrees, the page is fixed and the note is dated. If it does not agree, the reason is kept on file, and a reader who asked a fair question is not left without an answer.

What Counts as an Error Worth Logging

An error worth logging is a factual statement on a published page that is demonstrably wrong against the source we relied on at the time of writing. This includes a misstated instrument specification, such as saying one bitcoin lot equals 10 BTC when it equals 1 BTC, or a wrong regulatory statement, such as claiming FxPro holds an ASIC licence when the correct caveat is that it is licensed by the FCA (UK) and CySEC and does not hold an ASIC licence. It also covers a worked example that does not compute, like a margin figure that contradicts the stated leverage cap of 1:200. A typo that changes meaning qualifies; a typo that does not change meaning does not.

An error worth logging is not a matter of taste, emphasis or tone. If a reader disagrees with our decision to lead with risk rather than opportunity, or thinks a paragraph could be clearer, that is feedback, not an error. The test is whether the page asserts something that can be checked against a primary source and found false. For Tasman Coin, primary sources include the broker's own legal and product documentation, the regulator's public register, and the arithmetic of the instrument itself: 1 standard lot equals 1 BTC, one pip equals 1.0, and the reference price used in examples is approximately 77000.0. Anything outside that is opinion.

An error worth logging is one that could mislead a reader into a financial decision. A wrong funding method, such as naming a method FxPro does not support for Australian clients when the supported methods are PayID and bank transfer, is loggable because a reader might attempt it. A wrong currency symbol, such as showing USD where the page should show A$, is loggable because it changes the meaning of an amount. A stale reference price in a worked example is loggable if the page presents it as current rather than illustrative. Cosmetic issues, broken formatting and spelling that does not alter meaning are fixed quietly and do not enter the log.

A changed condition is not an error

If a broker changes a term, a document or a regulator position after the date a page was checked, the page was not wrong when it was written. That is a re-check, and the page is updated with a new date for when the material was last read.

The distinction matters because it tells a reader whether the desk got something wrong or whether the world moved. The dated note says which of the two happened, and the check date on each figure is there for the same reason.

The Three Kinds of Change and How Each Is Marked

Every change to a published page is marked as one of three kinds: error, update or clarification. An error mark means the prior text was factually wrong against its source, and the entry quotes the wrong text and the corrected text with the source that settles it. An update mark means the prior text was accurate when published but the underlying fact has changed, and the entry names the source that changed. A clarification mark means the prior text was accurate but ambiguous, and the entry shows the old wording, the new wording, and what ambiguity was removed. The mark appears at the top of the page and in the log.

The three marks are not ranked by severity, but they are not interchangeable either. An error mark is used only when a factual assertion failed its source check. An update mark is used only when an external fact moved. A clarification mark is used when no fact was wrong and no external fact moved, but a reasonable reader could have taken the wrong meaning. For example, if a paragraph said a 0.10-lot bitcoin position needs about $385.00 margin at 1:200 without stating that this is an example and not a recommendation, a clarification mark would record the added framing. The mark tells the reader which kind of change to look for.

Each mark is recorded with the date, the page, the quoted before and after, and the source or reasoning. The mark is visible on the page itself for a period, and permanently in the log. We do not use an error mark to cover a clarification, because that would overstate the failure, and we do not use a clarification mark to cover an error, because that would understate it. The three-way split exists so that a reader can tell the difference between us being wrong, the world changing, and us being unclear. That distinction is the whole value of the log, and it depends on the marks being used honestly and consistently.

How a Correction Is Recorded and Dated

A correction is recorded as a dated entry in a public log that names the page, the specific statement changed, the old wording, the new wording, and the source that settles the matter. The date is the date the correction goes live, not the date it was reported or the date it was approved. Each entry carries a sequential identifier so a reader can cite it. The entry does not paraphrase the change; it quotes the before and after so the record is verifiable without relying on our summary. The log is append-only, so an entry, once published, is not edited later.

A correction is dated to the day, in Australian Eastern time, because the audience is Australian and the page may be read before or after the change in other time zones. If a correction is made in stages, each stage gets its own dated entry rather than one entry updated over time. The date is not backdated to when the error was first introduced, because that would obscure when readers were actually misinformed. Instead, the entry notes the date the erroneous text was first published if that date is known, and the date it was corrected. Both dates appear in the log.

A correction is recorded even when the fix is small, provided it meets the error test. The record includes who approved it by role, not by name, so the log does not depend on staff turnover. It also includes the source consulted, such as the FxPro legal documentation for the regulatory caveat or the arithmetic for a margin example. Where the source is a regulator, the entry names the regulator and the document. Where the source is internal arithmetic, the entry shows the calculation. This makes the dated entry a standalone artefact that a reader can check without needing to trust the narrative around it.

Who Decides, and in What Time

The decision to log a change rests with the editor responsible for the page, who must classify it as error, update or clarification before any text is altered. That editor does not act alone on an error: a second reviewer checks the source and the proposed wording before the entry is published. The reviewer's role is recorded in the log, not their name. For a clarification, the editor may act with one review. For an update, the editor must cite the changed source. The point of the split is that an error claim is a claim about our own fallibility, and it should not be made by one person alone.

The time to decide is bounded by the nature of the claim. A reported error that affects a number, a currency, a regulator statement or a funding method is checked and, if confirmed, corrected and logged within two business days. A reported error that affects framing or emphasis is checked within five business days. An update is logged when the changed source is verified, not before. A clarification is logged at the next scheduled review of the page. These are internal targets, not guarantees, and the log records the date the report was received alongside the date the entry was published so a reader can see the elapsed time.

The decision to reject a report is also recorded, in a separate rejected-reports log, with the reason and the date. A rejection is not a silent outcome: if a reader reports an error and we conclude the text was accurate, the reader is told why and the rejection is dated. This matters because a site that only logs accepted corrections can look more accurate than it is. The rejected-reports log is public for the same reason the corrections log is public. Neither log names the reader who reported the issue. The editor and reviewer roles are named by function, and the dates are Australian dates.

The Difference Between a Correction and an Update

A correction fixes something that was wrong when it was published; an update changes something that was right when it was published but is no longer current. If we wrote that the maximum leverage available to Australian clients is up to 1:200 and that remains the cap, no update is needed. If the cap itself changed, the page would be updated, not corrected, because the original statement was accurate at the time. The distinction matters because a correction implies a failure of accuracy, while an update implies the passage of time or a change in the underlying facts. Readers deserve to know which one they are looking at.

A correction is triggered by evidence that the published statement did not match its source at the time of publication. An update is triggered by a change in the source itself, such as a regulator altering a licence status or a broker changing its platform lineup. For Tasman Coin, an update would be required if FxPro added or removed a platform from the set of MT4, MT5, cTrader and the FxPro app, or if the entity serving Australia changed from FxPro UK Limited. The original page would have been correct when written, so calling it an error would be false. The log marks the two differently.

A correction and an update are recorded in the same public log but with different labels, and the label is not interchangeable. A correction entry states that the prior text was inaccurate and shows the source that proves it. An update entry states that the prior text was accurate at the time and shows the source that has changed. Neither label is used to soften the other: we do not call a correction an update to make the original error look less serious, and we do not call an update a correction to look more diligent. The label is a factual claim about what happened, and it is dated accordingly.

Why the Log Stays Public

The log stays public because a correction that is not visible is indistinguishable from a cover-up, and readers of financial material need to know what has changed and when. Tasman Coin publishes the log at a stable address so that any reader, including one who arrives months later, can see the full history of a page rather than only its current state. The log is not behind a login, not summarised away, and not pruned. This is a deliberate cost: a public log exposes our mistakes permanently, which is the point. It also gives readers a way to judge whether the site corrects promptly and accurately.

The log stays public because Australian readers dealing with an offshore entity need to be able to verify the regulatory caveat for themselves. The statement that FxPro is licensed by the FCA (UK) and CySEC and does not hold an ASIC licence is the kind of claim that should be checkable against a dated record if it ever changes. A public log lets a reader see whether that caveat has been corrected or updated, and when. Without a public log, a reader would have to take our current word for it, with no way to tell whether the wording had been quietly altered after a complaint or a regulatory change.

The log stays public because it disciplines the writing. Knowing that every correction will be dated and quoted in public makes the original drafting more careful, and it makes the approval step more than a formality. The log also serves as a shared reference for readers who want to cite the page: they can point to a specific dated entry rather than a vague memory of what the page said. Nothing in the log is deleted, so the record remains complete even when a page is substantially rewritten. The public log is the audit trail, and an audit trail that can be edited is not an audit trail.