Corrections Policy

Errors are fixed in place, with a date

An error on this site is corrected in place and marked with a dated note, never quietly edited away. The note says what was wrong and what it now says, so a reader who saw the earlier version can see that it changed and why.

Silent edits destroy the record that makes a desk worth reading. If a figure was misread from a broker document, the correction shows the earlier reading and the corrected one, and the date the document was re-checked.

What Counts as an Error Worth Logging on a Gold Trading Page

An error worth logging is a factual statement on the page that is wrong and could change how a reader acts. That means a wrong instrument specification such as stating that 1 standard lot of gold is 10 oz instead of 100 oz, a wrong pip value, a wrong formula, a regulator caveat that misnames which bodies license FxPro, or a margin figure that does not follow from the stated leverage cap. Style preferences, wording choices and opinions do not qualify. The test is simple: if a reader followed the page and made a different trading decision because of the mistake, it belongs in the log.

A number that is merely out of date is not automatically an error; it becomes one when the page still presents it as current and a reader could rely on it. The reference price of about 4275.0 for XAU/USD is a snapshot, and the page labels it as such, so a market move alone does not trigger a correction. What does trigger one is a page that still says the reference price applies when the market has moved and the label has been lost, or a leverage statement that no longer matches the cap for the entity serving Uganda. The distinction is whether the page has become misleading, not whether the world has changed.

Errors in the funding route also count, because Ugandan readers act on them. If a page named a funding method other than Mobile Money, or implied that a deposit route existed when it did not, that is a loggable error. The same applies to any statement that a cost is low, tight or competitive without a stated basis, since that is an unsupported claim rather than a fact. We log it because the reader cannot verify a vague adjective and may size a trade on it. Concrete, checkable and consequential: those three conditions decide whether an entry goes into the log.

Who Decides a Change and the Timeframe for Making It

The decision to change the page rests with the editor responsible for the page, who applies the three labels and records the date; no change goes live without that sign-off. The timeframe depends on severity. A wrong instrument specification, a wrong pip value, a wrong formula, a misstated regulator caveat or an unsupported claim about costs is treated as urgent and fixed as soon as it is confirmed, because a reader could act on it within minutes of reading. A change that is merely a refresh of a snapshot figure follows the normal schedule for updates. The severity, not the convenience of the writer, sets the clock.

Confirmation is the step that takes the time, because a report alone is not proof. The editor checks the claim against the stated facts, against the calculation that produced the figure, and against the source where one exists. For a margin figure, that means redoing the arithmetic from the stated leverage cap and the contract size of 100 oz per lot, which is how the about $85.50 figure for a 0.10-lot position is checked. Until that check is complete, the page is not changed and no entry is logged, because logging an unconfirmed change would make the log itself unreliable.

Once confirmed, the change and its log entry are published together, so there is never a window in which the page has changed but the record has not. If a report cannot be confirmed, the page is left as it is and the reader who reported it is told why, which is itself part of keeping the record honest. The editor also decides which of the three labels applies, and that decision is recorded with the entry so a later reader can see the reasoning rather than only the outcome. Responsibility sits with a named role rather than with the site as a whole, because a collective decision is a decision no one can be asked about.

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

If a broker changes a cost, a condition or a funding route after we read its documents, the earlier page was accurate on the date it was checked. That is a re-check, not an error, and it is handled by updating the page with a new date read rather than by logging a correction.

This distinction matters because the opposite would be dishonest in the other direction: we will not call a page wrong for having been right when it was written. What we will do is date every figure and tell you to verify it with the broker, because conditions move.

The Three Change Labels and the Exact Mark Each One Carries

Every change on this page carries one of three labels: error, update or clarification, and the label is shown in the log entry and beside the changed text. An error label means the page previously stated something false, and the entry shows the old statement and the corrected one. An update label means the page previously stated something true that has since become out of date, and the entry shows the old and new versions with the date the change took effect. A clarification label means the original statement was true but could be misread, and the entry shows the original wording and the clearer wording without implying the first was wrong.

The labels are not interchangeable, and the choice between them is recorded at the time of the change rather than assigned later. A change that fixes a wrong pip size for gold, where one pip is 0.01, is an error. A change to the reference price snapshot from one figure to a newer one is an update. A change that spells out that the leverage cap is a maximum rather than a target is a clarification, because the original statement was accurate but easy to misapply. Each label tells the reader what kind of attention the change deserves, which is why the distinction is maintained even when it would be simpler to call everything a correction.

The mark is visible wherever the change appears, not only in the log, so a reader who lands on a single passage sees the label without having to find the log first. That matters for readers arriving from a search result or a shared link, who may never see the rest of the page. The label is short and plain, with no symbol that could be mistaken for decoration. Where a passage has been changed more than once, each change keeps its own label and date, so a reader can see a clarification followed later by an update, or an update followed by an error correction, in the order they happened.

How a Correction Is Recorded and Dated on the Page Itself

A correction is recorded by adding a dated note beside the corrected text and a matching entry in the page log, with the date the fix went live rather than the date the report arrived. The note says what the page said before, what it says now, and which source or calculation showed the original was wrong. The date is the publication date of the corrected version, so a reader can tell whether the version they are reading is the one that was fixed. Nothing is backdated to make the page look as if it was always right, because that would defeat the purpose of keeping a record.

The correction note stays attached to the passage it fixes for as long as that passage exists on the page. If the passage is later rewritten for an unrelated reason, the note moves with it or is carried into the log entry for that rewrite, so the trail is never broken. Dates are written in full, with day, month and year, to avoid the ambiguity between Ugandan and other date conventions. Where a correction affects a figure, the note shows the old figure and the new figure side by side, because a reader comparing two versions needs to see exactly what moved and by how much.

Every correction also records what triggered it: a reader report, an internal re-check, or a source change. That trigger is part of the record because it tells later readers how the mistake was caught and whether the same kind of mistake is likely elsewhere on the site. The date and trigger together form a minimal audit trail that a reader can follow without needing to contact us. If a correction is itself corrected, the second note is dated separately and the first note is left in place, so the history shows the sequence rather than a single flattened statement that hides the earlier mistake.

Why the Correction Log Stays Public and Visible to Any Reader

The log stays public because a reader cannot judge a page's reliability without seeing how often it has been wrong and how quickly it was fixed. A page that hides its corrections asks to be trusted on faith, which is the wrong basis for anything involving real money and leverage. Making the log visible means a Ugandan reader deciding whether to fund an account through Mobile Money can see whether the margin figures and instrument specifications they are relying on have a history of being corrected. The log is part of the page, not an internal document, because the reader is the person the record is for.

A public log also changes how the page is written. When every correction will be visible, vague claims and unsupported adjectives become obviously costly, so the writing tends toward statements that can be checked. That is the editorial reason the log exists: it is a constraint that improves the text. It also removes the temptation to quietly edit a wrong figure and pretend the page was always right, which is common and which leaves readers who acted on the old version with no way to know they were misled. Visibility is the mechanism that prevents the quiet edit.

The log does not expose reader identities. When a correction is triggered by a report, the entry records that a reader report triggered it, not who sent it, unless the reader asks to be named. The public part is the fact of the error, the fix and the date, not the correspondence. That balance lets the log serve its purpose without turning error reporting into something a reader might avoid for fear of being identified. The log is public because the record belongs to the reader; the reporter's privacy is kept because the report is a private act of help.

The Difference Between a Correction and an Update on This Page

A correction fixes something that was wrong; an update changes something that was right but is no longer current. If the page said one standard lot of gold equals 100 oz and that was always correct, changing it would be a correction only if the original figure had been wrong, which it was not, so it would instead be an update to a specification that had changed. If the page said the margin on a 0.10-lot gold position at the applicable cap was a different figure from about $85.50, fixing that is a correction. The two labels are kept separate because they tell the reader different things about the page's reliability.

An update is dated and marked as an update, not folded silently into the text, so a reader who memorised an earlier version knows the page has moved on. Updates are expected for things that change with the market or with a broker's arrangements, such as the reference price snapshot or the set of platforms listed. Corrections are expected when the page got a fixed fact wrong, such as the pip size for XAU/USD or the regulator caveat. Mixing the two would let a genuine mistake hide inside a routine refresh, which is why every entry carries one label and one only.

The practical difference for a reader is what they should do next. After a correction, the reader should re-read the corrected passage because their earlier understanding may have been based on an error. After an update, the reader should check whether the change affects their own position or plan, but they do not need to distrust what they read before. Both are logged with a date and both remain visible, but only the correction carries an acknowledgement that the page was wrong. That acknowledgement is the part that keeps the record honest rather than merely tidy.

How to report an error

To report an error, write to editor@kampalacounterug.com with the page address, the exact sentence, and what you believe is correct. If you have the broker document that shows it, mention where in that document the point appears.

We do not promise a response within a set number of hours or days, but every report is read. A report that quotes the page and the source is the easiest to verify, and verification is what decides whether a change is made.