Corrections policy

How we fix errors

If we publish a factual error, we correct the text in place and add a dated note at the bottom of the page explaining what was changed and when. We do not silently edit an article and pretend it was always right. The original error stays visible in the note so readers can see what was wrong.

The correction note is short and factual: the date, the old wording, the new wording, and the reason. We do not use a strikethrough in the main text because that can confuse readers who arrive later. The note is enough.

How to report an error

To report an error, email editor@veldterminal.com with the page URL, the sentence you believe is wrong, and if possible a link to the broker's document that shows the correct figure. We do not require proof, but it helps us verify quickly. We will check the claim against the broker's own materials.

We treat every report seriously, but we do not promise a response time in hours or days. If the report is valid, we correct the page and add the dated note. If we disagree, we will reply and explain why, but we will not argue endlessly.

Changed conditions are not errors

A condition that has changed since we checked is not an error. For example, if a broker changes its leverage cap or adds a new funding method, our old article was accurate at the time of writing. We call that a re-check, not a correction, and we will update the page when we can.

We date every figure we quote, so you can see when we last read the broker's document. If that date is old, the figure may have changed, and you should verify it with the broker before trading. We do not guarantee that any number remains current.

Fixing a stale gold quote that is still live

A gold quote only gets logged as an error when the price shown on Veld Terminal is not the price the underlying liquidity provider was actually streaming at that moment. A one-tick lag during a fast XAU/USD move is normal and not logged; a quote that is frozen for several seconds while gold is trading actively is logged. We do not log an error because a trader disagrees with the level or because a stop was filled at a worse price than hoped. The test is whether the displayed bid or ask was a genuine executable stream at the time it appeared on your screen.

An error worth logging also includes any number that breaks the arithmetic on the trade ticket. If you size one standard lot of XAU/USD at 100 oz and the margin shown is not consistent with the leverage cap that applies to your account type, that is logged. The same applies when the pip value on the ticket does not match a 0.01 pip size for gold. We log a wrong instrument code, a wrong contract multiplier, or a wrong currency label on a funding instruction. These are errors because a trader can act on them in seconds and lose money before noticing the mistake.

A funding or account error is logged when a payment method shown as available cannot actually be used from South Africa. If local cards and bank transfers in ZAR are listed but the gateway rejects an EFT, that is a logged error. If a regulatory disclosure on the page names the wrong entity for your FxPro account, that is logged immediately. What we do not log: a spread that widens around news, a swap that changes with the rollover calendar, or a leverage cap that is lower than the maximum because the instrument or client classification restricts it. Those are live market or account conditions, not data errors.

How a logged error gets a date and a public record

A correction is recorded with the date the corrected information was published on Veld Terminal, not the date the error was first noticed. If a wrong gold contract multiplier was live for three days and we fix it on a Tuesday, the correction is dated Tuesday. The record shows what the old value was, what the new value is, and the date and time the change went live. We do not backdate a correction to make the error look shorter. The date is the moment the reader could first see the corrected content, because that is the only honest timestamp.

Each correction is logged in a single public entry that includes the exact text that changed. If a margin formula on the gold page said one standard lot needs $85.50 at a certain leverage and the correct figure was different, the entry shows the old sentence and the new sentence. For a price quote error, the entry shows the incorrect quote, the correct quote from the liquidity provider, and the timestamp of both. This lets a reader see not just that something changed, but exactly what changed and when it became visible.

The log entry also carries a short reason for the correction, written in plain English. The reason says what the error was, such as a stale XAU/USD quote or a wrong FSCA entity name, and what the correct information is. It does not include an apology, a promise, or a marketing sentence. The entry is signed with the date and time only; no author name is attached. This keeps the record factual and fast to scan, which matters when a trader is checking whether a price they acted on was corrected after the fact.

Correction versus update: when a change is not a mistake

A correction is a change that fixes something that was wrong at the time it was published. An update is a change that brings the page in line with a new fact that was not wrong before. If Veld Terminal showed a spread of 0.3 on gold and the actual spread was 0.5, fixing that is a correction. If the spread later changes to 0.4 because market conditions changed, showing 0.4 is an update. The difference is whether the old information was false when a trader saw it or simply became outdated later.

A correction always gets a public log entry. An update may not. When FxPro changes the maximum leverage available to South African retail clients from one cap to another, that is an update to the page and does not need a correction entry, because the old cap was correct when it was published. When we change a sentence to say that local funding includes e-wallets because a new e-wallet was added, that is an update. The log only records changes that fix a past falsehood, not changes that reflect a new reality.

The distinction matters for trust. If every change were called a correction, readers would not know whether they acted on a mistake or on information that was right at the time. A trader who sized a gold position at a margin that was correct on Monday and changed on Tuesday does not need a correction; they need the new margin. A trader who saw a wrong pip value on Monday does need a correction entry dated Monday. The log keeps these two kinds of change separate so a reader can see which one applies.

Why the correction log is left public

The correction log is public because a trader who acted on a stale gold price has a right to check whether that price was later corrected. If the log were hidden, a trader who lost money on a bad XAU/USD quote could not verify that the error was acknowledged. The log is not there to prove Veld Terminal never makes mistakes; it is there to prove that when a mistake is found, it is fixed and dated. That proof is only useful if it can be read by anyone, at any time, without asking permission.

A public log also forces discipline on the correction process. Every entry has to show the old value, the new value, and the date. If a correction were made quietly, the temptation would be to fix a number without recording what it was before. That would leave traders unable to reconstruct their own trade history. The public log makes it possible to go back to a specific day and see what the page said on that day and what changed later. Without that, a correction is just a silent edit that helps nobody.

Finally, the public log is part of how Veld Terminal handles the FSCA regulatory caveat for South African readers. The page states that FxPro is licensed by the FCA and CySEC and that an FxPro entity holds an FSCA licence, and readers are told to check which entity their account is with. If we ever get that entity name wrong, the correction is public so that a reader can see exactly when the wrong entity was shown and when it was fixed. That is not a legal requirement; it is a practical safeguard for anyone trading gold with leverage in rand.

Gold margin arithmetic that gets fixed without a request

Some errors are fixed before a reader reports them because our own checks catch the arithmetic. If the gold trade ticket shows a margin for one standard lot that does not match the formula, the error is logged and corrected the same day. The worked figure we reference is that at a certain leverage, a 0.10-lot gold position needs about $85.50 margin. If a page shows a different margin for the same 0.10 lot and the same leverage, that is a logged error. We do not wait for a reader to point it out; the correction appears in the log with the date it was fixed.

The same applies to the pip value on the gold ticket. One pip for XAU/USD is 0.01, and one standard lot is 100 oz. If the ticket shows a pip value that does not match those two numbers, it is corrected without a request. A trader who sizes a trade in seconds from one screen is relying on that pip value to know their risk in rand. If the pip value is wrong, the trader might size a position much larger than intended. That is why the correction is logged publicly, so the trader can see the exact time the wrong pip value was live.

We do not proactively correct spreads, swaps, or commissions because those are not fixed numbers. The spread on gold depends on the liquidity provider and the time of day. A swap depends on the rollover calendar and the direction of the trade. A commission, if any, depends on the account type and the platform. None of these are errors when they change. They are market or account conditions. The only proactive corrections are for numbers that should be constant for a given instrument and leverage, like the margin and the pip value.

What qualifies as a logged error on Veld Terminal

An error is worth logging only when a displayed figure or instruction was factually wrong at the time of publication and could have led a reader to size a gold trade incorrectly. This covers a wrong XAU/USD price, an incorrect pip value for 1 standard lot (100 oz, where one pip is 0.01), a stale margin calculation, or a broken funding instruction that would make a ZAR deposit fail. Typos in commentary, style changes, or wording that is awkward but not misleading do not meet the bar for a public correction.

A logged error must be verifiable against the source data shown on the page, such as a specific gold quote near 4275.0 or a stated leverage cap of up to 1:200 for retail clients in South Africa. If the page said a 0.10-lot position needs about $85.50 margin and the arithmetic was wrong, that is logged. If market conditions changed and the number became outdated later, that is an update, not an error. The distinction is set at the moment of publication, not retroactively.

The test is whether a reader acting on the information in seconds, from one screen, could have entered a wrong order size or used an unsupported funding route. For example, listing a deposit method that is not one of the local cards, ZAR bank transfers or e-wallets would be logged, because a South African reader could waste time trying it. An error that only affects a footnote or a non-trading explanation is corrected silently if it cannot change a trade decision, but anything touching numbers, formulas or instructions goes into the public log.

How Veld Terminal records and dates a correction

Every correction is recorded as a dated entry in the public log the same day the error is confirmed, and the original text is updated with a visible correction marker. The log entry states what was wrong, what it was changed to, and the date the fix went live. There is no backdating: if a wrong gold margin figure was published on a Monday and corrected on Tuesday, the log shows the Tuesday date, and the page itself carries a note that the figure was corrected from the earlier version.

The recording process uses the page’s own timestamps as the source of truth. When an error is confirmed, the correction is assigned the date and time of the fix in South African Standard Time, not the date the error was first noticed. A reader can compare the log entry against the page’s edit history to see exactly when the change happened. For a number like a 0.10-lot gold margin at 1:200 leverage, the corrected value is shown next to the old value, with no ambiguity about which one is current.

The dated record is not an internal note: it is visible on the same page as the corrected content, so a trader who saw the wrong figure earlier can see that it was fixed and when. If the error involved a regulatory detail, such as the FSCA licence caveat for FxPro, the correction entry repeats the exact wording that was changed. Every correction entry is permanent and is never removed or edited after publication, even if the original error was minor.