Corrections Policy

How we handle errors

If we discover an error in any article, we fix it in place and add a dated note at the bottom of the article explaining what was corrected and when. We never silently edit a page to remove a mistake without acknowledging it. The original error is not preserved, but the correction note makes the change transparent.

Minor typos or formatting fixes may be made without a note if they do not change the meaning. However, any factual correction, such as a wrong number or a misstated regulation, will always be accompanied by a dated note.

How to report an error

If you see a mistake, email editor@aurumrand.com with the page URL and a description of the error. If you have a source that contradicts what we wrote, please include it. We will review your report and, if we agree, correct the page and add a note.

We cannot promise a response within a specific number of hours or days, but we read every report. If we do not correct something, it is because we believe the original statement was accurate based on the sources we used at the time.

Changed conditions are re-checks, not errors

If a broker changes its spreads, commissions, or other terms after we published a review, that is not an error on our part. We state the date we read each document, so a figure that was accurate on that date may later become outdated. In such cases, we will re-check the broker's current documents and update the article, but we will not add a correction note, because the original statement was true at the time.

We aim to re-check brokers periodically, but we cannot guarantee a fixed schedule. If you notice that a figure is outdated, please let us know, and we will prioritise a re-check.

Errors That Go Into the Aurum Rand Log

An error worth logging is any published fact that is wrong, misleading, or materially incomplete when a reader acts on it. That means a wrong lot size, a wrong pip value, a wrong leverage cap, a wrong margin formula, or a wrong regulator statement. If the page said 1 lot of XAU/USD is 10 oz instead of 100 oz, that goes in the log. If it said the FSCA license covers all FxPro accounts when it only covers one entity, that goes in. The test is simple: could a trader in South Africa size a position or choose a broker based on the mistake? If yes, we log it.

A typo that does not change the meaning is not logged. A currency code written as ZAR instead of R is not logged, because a reader still understands the rand amount. A missing comma in a sentence is not logged. But a wrong decimal in the reference price, such as 427.50 instead of 4275.0, is logged, because it changes the margin calculation for every gold position. We also log omissions when a required risk warning is absent. If a page discusses leverage without stating that 1:200 is a cap, not a target, that omission is logged as an error.

We do not log differences of opinion or style. Saying that risk-based sizing is important is a judgment, not a fact, so it cannot be an error. Saying that a 0.10-lot gold position needs about $85.50 margin at 1:200 is a fact, and if it is wrong, it is logged. If a reader reports an error, we verify it against the broker's official specifications and the FSCA register before logging. Only verified errors appear in the log, with the date, the correction, and the reason.

How a Correction Is Recorded and Dated

Every correction is recorded with the date it was published on the page, not the date it was reported. The log entry shows the original text, the corrected text, and the date the change went live. For example, if a page said the FSCA licence was held by FxPro UK and we changed it to FxPro Markets Direct Costa Rica Latam SRL, the log shows the old sentence, the new sentence, and the date of the edit. The date is in South African format, day month year, to match the reader’s context.

A correction is logged only after the page itself has been changed. We do not log a correction that is still pending. The log entry includes a short reason for the change, such as “wrong leverage cap stated” or “missing risk warning added.” The reason must be factual, not apologetic. We do not write “we regret the error” in the log. The log is a record of what changed and why, so a reader can see the correction history without contacting us.

Each entry in the log has a unique reference number, but we do not publish that number on the page. The log is dated so a reader can tell how recent the correction is. If a correction is made to a figure such as the margin for a 0.10-lot gold position, the log shows the old figure and the new figure. We do not state the margin figure in the log unless it was the subject of the correction. The log is updated within one business day of the page change.

Corrections Versus Updates on Aurum Rand

A correction fixes a wrong fact; an update changes a fact that was right before but is no longer right. If the page said 1 lot of gold is 100 oz and we later changed it to 10 oz, that would be a correction because 100 oz was never correct. If FxPro changes the maximum leverage from 1:200 to 1:100 for South African retail clients, that is an update because 1:200 was correct at the time of writing. We log corrections as errors; we log updates as “changed conditions.”

The difference matters because a correction implies we made a mistake, while an update implies the world changed. We do not treat a broker’s new spread table as a correction. If FxPro changes its commission on gold from one amount to another, the old amount was not an error; it was accurate at the time. We update the page and note the change in the update log, not the correction log. The correction log is only for our own factual mistakes.

A reader can distinguish the two logs by the wording. The correction log says “corrected from X to Y.” The update log says “updated to reflect new conditions as of [date].” We never call a broker’s changed terms an error. If the FSCA changes its licensing status for an FxPro entity, that is an update. If we previously wrote that the FSCA licence was held by a different entity than the actual one, that was a correction. The date on each log entry shows when the change was made.

Why the Aurum Rand Correction Log Stays Public

The correction log stays public because a reader who trusts our numbers is risking real money in rand terms. If a trader in Johannesburg uses our margin formula for a 0.10-lot gold position at 1:200, they risk about R1,600 based on a $85.50 margin. If that margin figure was wrong and we hid the correction, the trader could over-leverage and lose more than intended. The public log lets anyone verify that a number they saw earlier has been fixed, without needing to contact us.

A public log also disciplines our own process. If every mistake is visible, we are less likely to publish a wrong lot size or a wrong regulator caveat. The log is not a marketing tool; it is a record of our errors. We do not hide corrections in a footnote. We do not delete old entries. The log shows the history of changes, so a reader can see how often we correct and what kinds of errors occur. That transparency is part of the site’s risk-first approach.

The log is public because South African readers are protected by the FSCA’s expectation of fair treatment, but the FSCA does not review our content. We are not a financial services provider, so the log is our own commitment. A reader who sees a correction from “1:500” to “1:200” knows we do not inflate leverage. The log also helps a reader distinguish our errors from a broker’s changed terms. That clarity is essential for account protection.

What the Correction Log Does Not Cover

The correction log does not cover changes to our editorial opinions or emphasis. If we decide to stress risk-based sizing more in one section, that is not an error and not an update. The log only covers factual statements: numbers, formulas, regulator names, and broker terms. A change from “FxPro is licensed by the FCA” to “FxPro Markets Direct Costa Rica Latam SRL is the entity serving South Africa” is a correction if the first statement was wrong. A change in wording from “the spread your account type carries” to “spread depends on market conditions” is not a correction because we never state a spread number.

The log does not cover errors in other websites or in broker marketing. If FxPro’s own site has a wrong figure, that is not our error. We only log what we published on Aurum Rand. If a reader reports an error that turns out to be on another site, we do not log it. The log is not a review of FxPro’s accuracy. It is a record of our own factual record. That boundary keeps the log focused and useful for a reader who wants to check our track record.

The log also does not cover minor formatting changes. If we change a heading from “Leverage in South Africa” to “Maximum Leverage in South Africa” without changing the facts, that is not logged. If we fix a broken link, that is not logged. Only factual corrections that affect a reader’s decision are logged. The log is not a page history; it is an error log. A reader who wants the full edit history can contact us, but the public log is limited to corrections and updates as defined above.

What Counts as an Error Worth Logging

An error worth logging is any fact on Aurum Rand that was wrong when we published it, and that a reader could have acted on to their financial detriment. This includes a wrong instrument contract size, such as stating that one gold lot is 10 oz instead of 100 oz, or a wrong pip value that changes position sizing. It also includes a wrong regulatory statement, for example claiming an FSCA licence applies to all FxPro entities when only one does, and any wrong funding method like saying a local bank transfer is instant when it can take a business day. These are logged because they affect how a trader manages risk, and protecting the account first means never letting a factual error stand.

An error worth logging can be a number, a name, or a definition that is objectively false. For example, if we wrote that the maximum leverage in South Africa is 1:500 for everyone, that would be logged because the actual cap is 1:200 for retail clients and up to 1:500 only for eligible professional clients depending on instrument. A wrong margin example would also be logged, such as saying a 0.10-lot gold position needs $8.50 margin when it actually needs about $85.50 margin at 1:200 leverage. These are not matters of opinion or interpretation; they are checkable against the broker's official documents and the FSCA register, so they go into the correction log.

An error worth logging is one that we can verify against a primary source, not a reader's disagreement with our editorial angle. If we stated that local cards and bank transfers in ZAR are the only funding methods, but a reader proves that e-wallets are also accepted, that is a logged correction because it changes how a South African trader can move money. However, if a reader simply thinks we should have emphasised a different risk warning, that is not an error; it is a matter of editorial judgement. The test is always: was the statement false at the time of publication, and would correcting it help a trader avoid a wrong decision about their gold position?

How a Correction Is Recorded and Dated on Aurum Rand

A correction on Aurum Rand is recorded by editing the original page with the correct fact and adding a dated note at the bottom of that page, not by deleting the old text silently. The note states what was changed, when it was changed, and why the old version was wrong. For example, if we had written that one gold lot is 10 oz, the correction note would say: 'Correction on 15 June 2025: The contract size for gold was corrected from 10 oz to 100 oz per standard lot, because the original figure understated the position size by a factor of ten.' The date uses South African format, day month year, and the note is visible to every reader.

Each correction is also logged in the public correction log, which is a separate page listing all corrections in reverse chronological order. The log entry includes the page name, the exact old text, the exact new text, the date of correction, and the reason. For instance, an entry might read: 'Page: Gold Trading Conditions; Old: Maximum leverage is 1:500 for all clients; New: Maximum leverage is up to 1:200 for retail clients and up to 1:500 for eligible professional clients depending on instrument; Date: 20 May 2025; Reason: The previous statement did not distinguish retail from professional clients and could have misled a reader about margin requirements.' This log is permanent and cannot be edited retroactively.

The date of a correction is the date we actually make the change on the live site, not the date we first learned of the error. That means if a reader reports an error on a Monday, but our fact-check takes two days, the correction is dated Wednesday. The corrected page itself also carries a 'last updated' date in the footer, so a reader can see how current the information is. For a gold trading page, this matters because margin requirements or leverage caps can change, and a correction date tells you whether the page reflects the latest FxPro and FSCA conditions before you risk any rands on a position.