Corrections Policy

How we fix errors

When we find an error on a page, we correct it in place and add a dated note at the bottom of that page, such as 'Corrected on 15 June 2025: spread figure updated.' We never silently edit a page without acknowledging the change. This lets readers see what was wrong and when it was fixed.

If the error is significant, such as a wrong regulation claim or a misleading fee figure, we will also mention the correction on the relevant broker page or in our next update. We do not delete the page or pretend the error never existed.

How to report an error

If you spot an error, please email editor@randbullion.com with the page URL, the specific sentence or figure, and why you believe it is wrong. We do not require proof, but a link to the broker's official document helps us verify quickly. We will check the claim against the broker's current documents and our own records.

We cannot promise a response time, but we read every correction report. If we agree that an error exists, we will fix it as described above. If we disagree, we will explain why, and we may add a clarification to the page if the point is ambiguous.

Changed conditions are re-checks

A condition that has changed since our check is not an error; it is a re-check. For example, if a broker changes its minimum deposit or spread after we reviewed it, our original review was correct at the time. We will re-check the broker when we can and update the page with a new date and note.

We do not automatically update every page when a broker changes something, because we have limited resources. However, we try to revisit brokers regularly, especially if a reader tells us about a change. The date on each broker page tells you when we last verified the details.

What counts as an error worth logging

An error worth logging is any factual claim about gold trading that a reader could act on and that is wrong at the time of publication. That means a wrong pip value, a wrong contract size, a wrong margin formula, or a wrong regulatory statement. For Rand Bullion that includes mistakes about XAU/USD specifications: 1 standard lot is 100 oz, one pip is 0.01, and the reference price near 4275.0. If a page said one pip is 0.10 or that a 0.10-lot position needs $855 margin instead of about $85.50 at the stated leverage cap, that is logged as an error, not as a style choice.

A wrong number is logged, but so is a misleading one. If a page implied that 1:200 leverage is a setting to aim at rather than a cap, that is an error because it changes risk perception. If a page said FxPro is regulated by the FSCA without the caveat that the entity serving South Africa is FxPro Markets Direct Costa Rica Latam SRL, that is logged. Errors also include broken formulas: for example, saying margin = price × lots × 100 ÷ leverage when the correct formula for a 0.10 lot at 4275.0 and 1:200 gives about $85.50, not half or double that.

We do not log differences of opinion, writing style, or market commentary that was accurate when written. A spread or swap that changed because the market moved is not an error; it is an update, and it is recorded separately. An error is a statement that was false at the time it was published and that a trader could have relied on to size a position or judge a cost. Every correction in the public log meets that test: a concrete, verifiable, actionable fact that was wrong.

How a correction is recorded and dated

A correction is recorded as a new entry in the public correction log on the Rand Bullion page where the error appeared. The entry includes the original text as it stood, the corrected text, and the date the correction was made. The date is the day the change went live on the site, not the day the error was found. If an error was spotted on a Tuesday but the fix was published on Thursday, the log shows Thursday's date, so a reader can match the log to the page history without ambiguity.

Each correction entry carries a unique reference number and the exact section heading where the error appeared. That reference is permanent and never reused. If the same error was present on more than one page, each page gets its own entry, because the reader of a specific page should not have to search another page's log. The entry also states the nature of the error: for example, 'incorrect pip value stated as 0.10; corrected to 0.01 for XAU/USD.'

The original text is preserved in the log, not only the corrected version. That lets a reader see exactly what changed and judge whether it matters for their trading. The log is ordered newest first, with the date in ISO format (YYYY-MM-DD) followed by the time in South African Standard Time. For a Rand Bullion reader, that means no confusion about US or UK date formats. No correction is backdated, and no entry is ever removed from the log.

The difference between a correction and an update

A correction changes text that was false when it was published; an update changes text that was true when published but is no longer true because the underlying fact changed. For example, if a page said FxPro offers MT4 and MT5, and that was true at publication, then FxPro adds cTrader, that is an update, not a correction. The original statement was not an error. Rand Bullion logs corrections and updates in separate sections so a reader can tell whether we made a mistake or the market moved.

A correction is always our fault; an update is not necessarily anyone's fault. If the maximum leverage available in South Africa changes from 1:200 to 1:100, that is an update to the page, and it is logged with the date the change took effect, not the date we edited the page. The old leverage ratio was correct when written. We do not label an update as a correction, because that would falsely imply the original page was wrong and would erode trust in the log.

Some changes are neither corrections nor updates: they are clarifications. If a paragraph was grammatically ambiguous but factually correct, we may rewrite it for clarity and log it as a clarification, not a correction. A clarification does not change any number or claim; it only makes the sentence easier to parse. For example, changing 'margin is price times lots times 100 divided by leverage' to 'margin = price × lots × 100 ÷ leverage' with an example is a clarification, not a correction.

Why the log stays public

The correction log stays public because a trader who made a decision based on an old version of a page needs to know what changed and when. If a page said a 0.10-lot gold position needs $85.50 margin and later that number changed because the leverage cap changed, a reader who sized a position from the old number has a right to see that the page was edited. A private log would hide that history. Public logging is the only way to make the page trustworthy as a tool for real money decisions.

A public log disciplines the writing and editing process. When every factual error is recorded with the original text and the date, writers and reviewers know that mistakes will be visible to readers. That pressure reduces the chance of sloppy numbers, unsupported claims about spreads or swaps, or missing regulatory caveats. For a South African reader, that means the FSCA caveat about which FxPro entity holds their account is less likely to be omitted, because an omission would be logged as an error.

The log is also a record of our honesty over time. A site that hides its corrections cannot prove it corrects anything. By keeping the log public and never deleting entries, Rand Bullion lets a reader audit our accuracy. If a reader sees many corrections, they can judge whether the errors were material. If they see few, they can check the dates to be sure the log is not being quietly reset. Public logging is a structural commitment, not a marketing claim.

Errors that enter the correction log

A correction is logged when a stated fact about Rand Bullion’s gold offering is materially wrong or misleading to a reader in South Africa. This includes incorrect instrument details such as the 0.01 pip size for XAU/USD, the 100 oz contract size for one standard lot, or the reference price we use for worked examples. If we publish an inaccurate maximum leverage cap for retail clients in South Africa, that goes straight into the log because it changes risk and margin calculations. Any wrong number for local funding methods or the specific FxPro entity serving South African accounts also qualifies. The test is whether a reasonable trader would have made a different decision had the error not been there.

An error worth logging is one that survives a reader’s practical use of the page. If the correction changes how a trader sizes a position, calculates margin, or understands which regulator and entity they are dealing with, it is material. For example, stating a different pip value for gold than 0.01 would distort profit and loss per lot. Stating a different leverage cap than the correct one for South Africa would change the margin required on a 0.10 lot position, which we show as about $85.50 at the maximum retail cap. Errors in the names of local funding methods, such as leaving out EFT or e-wallets, are also logged because they affect how a trader deposits rand.

We do not log differences of opinion, style choices, or facts that are correct but could be worded differently. An error is a factual mismatch between what the page says and what our source data or the FxPro entity serving South Africa confirms. If a number is missing rather than wrong, that is an incompleteness we fix as an update, not a correction. Only when a specific, checkable statement is false does it enter the public log. That keeps the log short and meaningful for traders who want to know whether they can trust a particular figure, formula, or regulatory statement on the Rand Bullion page.

How a logged correction is dated and recorded

Every correction is recorded with the exact date it goes live on the page, using the South African date format day-month-year. The entry states what the text said before, what it says now, and why the change was made. If a number changed, both the incorrect and correct values are shown, such as a wrong leverage cap being replaced with the correct cap for South Africa. The record also names the section of the page where the error appeared, so a reader can locate the corrected text quickly. No correction is backdated or merged with another change; each error gets its own dated entry even if several are fixed on the same day.

The date on a correction is the publication date of the corrected text, not the date the error was first made or the date we learned about it. If a reader reports an error on a Tuesday and we fix it on Thursday, the log shows Thursday’s date. For South African traders, this matters because time-sensitive details such as funding methods or the FxPro entity serving South Africa can change, and a stale correction date could mislead. We do not use relative dates like 'last week'; the log shows a full date so there is no ambiguity about when the page became accurate. Each correction also carries a short unique reference so it can be cited in queries.

Recording a correction means updating the public log at the same moment the page text is fixed. There is no window where the page shows corrected information but the log still shows the old error. If the correction involves a worked example, such as the margin on a 0.10 lot gold position, the log shows the before and after calculation so a reader can check the arithmetic. For regulatory statements, the log records the exact wording change, for example from one entity name to FxPro Markets Direct Costa Rica Latam SRL. This level of detail allows a South African reader to verify that the correction matches what FSCA-related disclosures require.

Correction versus update: what separates them

A correction fixes a factual error, while an update changes content that was accurate but is no longer current. If we wrongly stated the pip size for XAU/USD as something other than 0.01, that is a correction. If the pip size never changes but we add a fresh worked example for a different position size, that is an update. Corrections go into the public log with a before and after; updates may be noted in a changelog but are not treated as errors. For Rand Bullion, an update might add a new local funding method to the list, while a correction would remove a method that was never actually available to South African clients.

The key test is whether the previous text was true at the time it was published. If it was true and later became false because conditions changed, that is an update. For example, if the maximum leverage available to retail clients in South Africa changes from the current cap to a lower cap, we would update the page and note the change, but the old number was not an error. Corrections are only for statements that were false from the moment they appeared. This distinction matters because a reader needs to know whether a past mistake affects their trust in other numbers on the page, or whether the page simply reflects a changing regulatory or broker environment.

We apply the correction label narrowly to avoid diluting the public log with routine maintenance. A typo in a non-numeric word might be fixed silently as an update, but a typo that changes a number, such as writing 0.1 instead of 0.01 for the pip, is a correction. Similarly, a change in the way we phrase the FSCA caveat is an update if the underlying facts are unchanged, but a change in which FxPro entity serves South Africa is a correction because the old entity name was wrong. South African traders can rely on the correction log to contain only genuine factual errors, not every improvement or refresh.

Why the correction log is public

The correction log is public because a trader in South Africa needs to know whether a page they used yesterday contained a wrong figure. If we quietly fixed an error in the margin calculation for gold, a reader who had already sized a position based on the wrong number would never know. By making the log public, we allow every reader to check whether any past advice or number they relied on has been corrected. This is especially important for high-risk instruments like XAU/USD, where a small error in pip value or leverage can change the rand risk on a trade.

A public log also creates a clear record for anyone comparing Rand Bullion’s information with other sources. If we stated a different maximum leverage cap for South Africa and later corrected it, the log shows the exact change and date. Without that public record, a reader might see the corrected page and assume the information was always correct, or might cache the old page and never know it was wrong. The log removes that uncertainty. For regulatory statements, such as which FxPro entity serves South Africa, the public log helps a trader verify that the disclosure matches what they see in their own account documents.

Keeping the log public is a discipline on our own publishing process. When every factual error is exposed with a date and a before-and-after, there is an incentive to check numbers before they go live. For a South African audience, this matters because local factors such as rand deposits, EFT funding, and the FSCA-related caveat must be stated precisely. A private correction log would serve only the publisher; a public one serves the trader. We treat the log as part of the toolkit, not a confession. It tells a reader that when a number appears on the page, it has been checked against the source data we hold for Rand Bullion.