Corrections Policy

How an error is handled

An error is corrected in place and a dated note is added to the page, so the change is visible rather than silent. The note says what was wrong and what it now says, and the page keeps its address so links to it still work.

We do not quietly rewrite a paragraph and hope nobody noticed. Where a figure was stated and later found to be wrong, the correction says so plainly, because a reader who relied on the earlier version deserves to know it changed.

Who Decides a Change Is Needed, and Within What Time

The decision sits with the person who maintains the page, not with whoever reports the issue, and it is taken after the claim has been checked against a source rather than on the strength of the report alone. A reader report starts the process; it does not conclude it. The time frame depends on severity: anything that could cause a reader to size a gold position wrongly, or to misunderstand which regulator supervises the entity serving India, is treated as urgent and handled before other work, while wording and clarity issues queue in normal order.

For a substantive factual dispute, the working target is to reach a decision within a small number of working days of the report, and to publish the entry once the source has been confirmed. We do not publish a correction while the question is still open, because a premature correction creates a second error. If the check takes longer than expected, the page is not left silently wrong: the disputed sentence is either removed until it is settled or flagged, and the log records that a check was opened on a given date even before it records the outcome.

No one here overrides a source to protect the page's appearance. If a source contradicts what we wrote, the page changes, and the entry says so plainly. The only case where we hold is when the source itself is unclear, and then the entry states what is unresolved rather than picking the reading that flatters us. That discipline is what makes the log worth reading: the decision rule is fixed in advance, so a reader can predict how a report will be handled rather than having to trust the mood of the day.

How a Correction Is Recorded and Dated in the Log

A correction is recorded as a dated line in a public log that names the page, the sentence as it originally stood, the sentence as it now reads, and the source that settled the question. The date attached is the date the correction went live, not the date the report arrived, so a reader can tell when the fixed version became the version everyone else saw. Where the page was wrong for a stretch of time, the entry also carries the date the faulty wording was first published, so the exposure window is visible rather than implied.

Each entry is written so it can be read without the original page open beside it. That means the old wording is quoted rather than summarised, because a summary of a mistake tends to soften it. If the error involved a number, both the wrong number and the right one appear side by side, and if the error involved a name, both names appear. An entry that reads only fixed a leverage error tells a reader nothing, while an entry that shows the old sentence and the new one lets them check whether anything they relied on has changed.

Dating is deliberately blunt: one date per entry, taken from the live publication, with no backdating and no rounding to the nearest week. If a correction is itself corrected, that becomes a second entry with its own date rather than an edit to the first, so the log accumulates rather than tidies itself. Readers in India comparing a page against a screenshot they saved earlier can therefore match the change to a specific day, in the same way they would reconcile a UPI payment against a bank statement, without needing to ask us when something moved.

What Counts as an Error Worth Logging on This Page

An error worth logging is a statement on this page that was wrong when it was published, or became wrong because we misread a source, and can be pointed to as wrong by a named source. A wrong lot size for gold, a pip value stated as 0.1 instead of 0.01, or a leverage figure attributed to the wrong entity all qualify, because each one changes the arithmetic a reader takes away. So does a mislabelled regulator: writing that FxPro is licensed by SEBI would be a loggable error, since the correct position is that FxPro is licensed by the FCA (UK), CySEC and FSCA, and not by SEBI.

A judgement call, a forecast, or a view on whether gold will rise is not an error worth logging, because nothing factual was asserted. Style, tone and the choice of which topics to cover are also outside the log, since a reader may disagree with them without anything being untrue. The test we apply is simple: can someone show a source that contradicts the sentence as written? If yes, it goes in the log. If the objection is that the explanation could be clearer, or that a risk warning should sit higher on the page, that belongs in a clarification rather than an error entry.

A figure that was correct when written but has since moved is not an error, and logging it as one would misrepresent the page's history. A reference gold price near 4275.0 is a snapshot, not a promise, and it will drift. The same holds for anything a broker controls, such as the margin requirement on a 0.10-lot gold position, which depends on the leverage tier applied to the account. We log those as updates with the date the condition changed, and we keep the error log reserved for cases where the page itself was at fault.

What We Do When a Source Changes Without Saying So

When a source changes silently, we treat the page as unverified rather than as correct until the new position is confirmed, and the log records that a re-check was triggered and when. A regulator rewriting a licence page, a broker quietly revising its contract specifications, or a platform note disappearing without a changelog all create the same problem: our citation still points somewhere, but it no longer supports the sentence. The first action is to compare the live source against the wording we relied on, and the second is to state in the log which of the two moved.

Silent source changes are logged as updates, not errors, unless the check shows we misread the source in the first place. The distinction is not cosmetic. If a broker alters the leverage cap it offers to Indian clients, our earlier sentence was accurate when written, and calling it an error would misrepresent both the page and the source. If, on the other hand, the source said one thing all along and we transcribed it wrongly, that is a correction with the old wording quoted, and the entry says the source did not change.

We do not silently adopt a new source position to keep a sentence alive. If the replacement source is weaker, or if the only available statement is the broker's own marketing rather than a specification document, the page says what is confirmed and what is not. Where a figure cannot be re-confirmed, the sentence is rewritten to describe what the number depends on instead of asserting a value. That is the same rule we apply to costs: we describe what a charge consists of and what it varies with, rather than presenting an unverified figure as settled.

How to report a correction

Send the report to [email protected] with the page address, the sentence in question and, where possible, the broker document that shows the correct position. A link or a quoted line from the broker's own page is the fastest way to get a correction verified.

We do not promise a response time in hours or days. Each report is read, checked against the broker's own documents, and either corrected with a note or answered with the reason it was not treated as an error.

How a Reader Can Check the History of a Page

A reader can check a page's history by opening the correction log, finding the section that carries the figure in question, and reading the entries in date order from the oldest to the newest. Each entry names the sentence as it originally stood and the sentence as it now reads, so the comparison can be made without any tooling. If a reader wants to know whether the margin example for a 0.10-lot gold position changed, they look for entries tagged to that passage and read the dates, rather than relying on memory of what the page said last month.

For anyone who wants to verify independently, the practical method is to keep a copy: save the page or a screenshot with the date visible, then compare it against the live text and the log later. The log tells you what we say changed; the saved copy tells you what you actually saw. Where the two disagree, the saved copy wins as evidence of your experience, and a report quoting it is the fastest way to get the discrepancy examined and, if warranted, entered in the log with the date you captured it.

The log is organised so that a single figure can be traced without reading everything. Entries carry the section they touch and the kind of change, so a reader checking one number can filter to corrections and updates for that passage and see the full sequence. The log does not replace the broker's own documentation, which remains authoritative on margin, costs and platform behaviour, and it does not replace the regulator caveat that FxPro is licensed by the FCA (UK), CySEC and FSCA, and not by SEBI. It records how this page has changed, nothing more.

The Difference Between a Correction and an Update

A correction fixes something that was wrong; an update changes something that was right and has since stopped being current. The distinction matters because the two carry different implications for a reader who acted on the page. If we wrote a wrong pip value for gold, that is a correction, and anyone who used the figure was misled by us. If a broker changes the leverage cap available to Indian clients, and we revise the page to match, that is an update, and anyone who used the older figure was working from a condition that has genuinely moved rather than from an error on our part.

The two are marked differently so the difference is visible at a glance. Corrections carry the old wording and the new wording plus the source that resolved the conflict. Updates carry the date the underlying condition changed and a plain statement of what it changed from and to, without the language of fault. A page can carry both kinds of entry about the same sentence over time, and that is normal: a figure can be updated when a broker changes a condition and later corrected if we transcribe the new figure wrongly.

One practical consequence is that an update never implies the earlier version was careless. When we note that the maximum leverage available in India is up to 1:200, with up to 1:500 for eligible traders after an experience and financial assessment, and later revise the wording, we are tracking a cap that brokers set, not confessing a mistake. Treating every revision as an error would make the log noisy and would train readers to distrust figures that were accurate on the day they were written, which is the opposite of what a log is for.

A changed condition is a re-check, not an error

A condition that has merely changed since we checked is a re-check, not an error. If a broker alters its leverage terms, its funding routes or its platform list after our dated read, the original page was accurate on the date shown and is updated as a re-check.

The distinction matters because it keeps the record honest in both directions. We do not label a broker wrong for a later change, and we do not use that distinction to excuse a figure that was wrong when it was published.

Why Nothing Is Deleted From the Record

Nothing is deleted because a correction log that can be pruned is not a record, it is a claim about a record. If an entry disappears when it becomes inconvenient, a reader has no way to tell whether the page improved or the evidence was tidied. Keeping every entry, including the ones that reflect badly on us, is what lets someone reconstruct what the page said on any given date. A reader who saved a screenshot before a change can match it against the log, and the log will still contain the version they saw.

Deletion also destroys the pattern. A single correction says little, but four corrections to the same kind of figure, such as leverage or pip values, says something about where errors enter our process, and that pattern is only visible if the earlier entries survive. Retaining them is therefore a quality signal pointed inward as well as outward: it shows which sections need a second check before publication. Removing the old entries would erase exactly the information that helps us stop repeating the mistake.

The record is append-only in practice. Superseded wording stays in the log with its date, marked as superseded rather than struck out, and a new entry sits above it. The only thing we will remove is content that is unlawful or that exposes a named individual to harm, and when that happens the log says an entry was removed and why, so the gap is explained rather than hidden. Everything else, including an error that stood for months, remains visible for as long as the page exists.

Why the Correction Log Stays Public Rather Than Internal

The log stays public because a reader cannot judge a page's reliability from its current text alone; they need to see how it has behaved over time. A page that has never been corrected and a page that has been corrected four times and shows all four look identical if the log is internal. Publishing the log lets someone weigh the record rather than take our word for the standard, which matters on a page where a misread lot size or pip value changes the arithmetic a reader carries into a live gold position.

Public logging also keeps the correction honest. An entry written for an audience is harder to fudge than an internal note, because the reader can compare it with what they remember seeing. That constraint improves the wording: we quote the old sentence rather than paraphrase it, we name the source, and we resist the temptation to fold two separate mistakes into one tidy entry. The log therefore functions less as an apology and more as a change record, in the way a bank statement records movements rather than describing them.

There is a risk dimension too. Gold trading at leverage carries the possibility of losing more than intended, and a reader sizing a position needs the page's numbers to be traceable. If a figure was wrong for a period, a public log tells them whether the period overlaps the day they read it. The log does not remove the risk and is not a substitute for the broker's own contract specifications, which remain the authoritative source for margin, costs and platform behaviour on MT4, MT5, cTrader or FxPro Edge.

Marking an Error, an Update and a Clarification Differently

The three kinds of change are marked by label, by what they carry, and by where they sit. An error is labelled as a correction, carries the old and new wording with the source, and sits at the top of the log because a reader who relied on the wrong version needs to see it first. An update is labelled as an update, carries the date the condition changed and what it moved from and to, and sits in date order among other updates. A clarification is labelled as a clarification and carries only the revised wording, because nothing was false before, only ambiguous.

A clarification is the category people underestimate. It covers a sentence that was true but could reasonably be read two ways, such as a margin example that did not say which leverage tier it assumed. Nothing was wrong, so it is not an error, and nothing external changed, so it is not an update, yet the page still needed fixing. Marking it separately keeps the error count meaningful: if every clarification counted as an error, the log would overstate how often the page was actually wrong, and readers would discount the label that matters most.

The labels are applied at the point of change and are not revised afterwards. If a clarification later turns out to have been hiding a genuine error, we add a correction entry rather than relabel the earlier one, so the sequence of what we knew and when stays intact. Each entry also names the section of the page it touches, so a reader checking one figure, such as the margin on a 0.10-lot gold position at about $85.50, can find every change made to that passage without reading the whole log.