Corrections Policy

How we correct errors

When a factual error is confirmed, Gulf Bullion Desk corrects it in place on the same page. A dated note is added at the end of the section or article, stating what was changed and when. The original incorrect text is not left visible.

Minor typographical fixes may be made without a note, but any change to a fact, figure, or interpretation is always logged. The desk does not silently edit content after publication.

How to report an error

To report a possible error, write to editor@gulfbulliondesk.com. Include the URL of the page, the exact text you believe is wrong, and a source or reason for the correction. The desk will review the claim against the broker's current documents.

The desk does not promise a response time, but all reports are read. If the error is confirmed, the page is updated with a dated correction note. If the claim is not an error, the desk may still add a clarification if the text was ambiguous.

Changed conditions are not errors

If a broker changes a condition after the desk checked it, that is not an error. For example, if a spread widens or a funding method is removed, the page is re-checked and updated with a new date. The desk does not treat a change over time as a mistake in the original check.

The desk records the date each figure was read from the broker's documents. Readers should always verify current figures with the broker before trading, because conditions can change at any time.

Material errors in gold pricing and execution that get logged

An error is logged when a displayed or executed gold price, cost component, or trade instruction was factually wrong in a way that could change a trading decision on XAU/USD. This includes a wrong pip convention for gold (0.01), an incorrect contract size for 1 standard lot (100 oz), or a mismatched reference price near 4275.0 that misstates the AED value of a position. It also covers execution errors such as a trade filled at a price the client did not accept or a margin calculation that does not match the worked figure of about $85.50 for a 0.10-lot position at the maximum available leverage in the UAE.

A material error also includes any statement that misrepresents regulatory status or available funding in the UAE. For example, saying FxPro is licensed by a regulator it does not hold, or omitting the exact caveat that it is licensed by the FCA (UK), CySEC and FSCA, would be logged. An incorrect claim about local bank transfer support, or listing a funding method not supported such as a local payment app, would be logged. Any error in the maximum leverage cap of 1:500 on standard forex accounts, within DFSA/SCA-compliant limits, is logged because it directly affects margin planning for gold traders in the UAE.

Errors are logged only when they are factual and verifiable, not when a trader disagrees with an opinion or when market conditions change. A spread, commission or swap that was correctly stated at the time is not an error if it later changes; that is an update. The log therefore captures only statements that were false when published, such as a wrong formula for gold margin, a wrong currency conversion to AED, or a wrong platform name among MT4, MT5, cTrader and FxPro Edge. This keeps the log precise and useful for UAE readers who rely on exact figures before placing a trade.

How each correction is recorded with date and evidence

Every correction is recorded as a dated entry in the public log, showing the original error, the corrected statement, and the date it was fixed. Each entry includes a short explanation of why the correction was needed and a link to the revised section. The date uses the Gregorian calendar in day-month-year format for clarity in the UAE. The log entry is permanent and cannot be edited silently; any later change to the same fact creates a new entry rather than overwriting the old one, so the full history of corrections is preserved for readers.

The recording process captures the exact text before and after, so a reader can compare the two versions. For example, if a page had stated a leverage ratio other than the permitted cap of up to 1:500 on standard forex accounts within DFSA/SCA-compliant limits, the log would show the incorrect ratio, the corrected ratio, and the date. If a margin example for a 0.10-lot gold position had used a different margin than about $85.50, the entry would show both numbers and the formula used to recalculate. No correction is made without a dated log entry, and every entry is reviewed for accuracy before publication.

Evidence for each correction is internal and verifiable: the source of the correct fact is noted in the log, such as the broker’s current specification sheet or a regulatory statement. For UAE-specific claims, such as the support of local bank transfer in AED, the log references the payment page snapshot at the time of correction. The log does not publish private documents but states the basis for the change, for example, confirming that FxPro is licensed by the FCA (UK), CySEC and FSCA. This evidence trail lets a trader in the UAE verify the correction independently without relying on the site’s word alone.

Corrections versus updates when gold trading terms change

A correction fixes a statement that was false when it was published, while an update changes a statement that was true but became outdated. For example, if a page had said the maximum leverage in the UAE is 1:400, that is a correction because the actual cap is up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits. If the broker later changes that cap to a different number, the page is updated, and the change is noted as an update, not an error. Corrections are logged with a date and explanation; updates may be noted in a separate changelog or with a last-reviewed date.

The distinction matters for trust: a correction signals that the site made a mistake, while an update signals that the external facts changed. A trader reading the log can see whether the site failed to get the numbers right, or whether the broker changed its terms. For gold trading, a change in the margin required for a 0.10-lot position at maximum leverage from about $85.50 to a new amount would be an update if the broker adjusted its margin requirements. A correction would be needed if the original $85.50 figure had been miscalculated from the start.

The site does not treat changed conditions as errors because no publisher can predict future changes to spreads, commissions, swaps, or leverage caps. A spread that was correctly quoted yesterday is not an error if it is different today; it is a market or broker update. The same applies to funding methods: if a new e-wallet becomes available in the UAE, that is an update to the page, not a correction. This keeps the corrections log focused on accuracy of the facts at the time of writing, not on the ongoing changes in the trading environment.

Why the public correction log remains open for UAE traders

The log stays public because gold traders in the UAE need to verify the precision of every number before risking AED on a position. A trader checking the margin for a 0.10-lot XAU/USD trade wants to know that the figure of about $85.50 at the maximum available leverage is not only correct now but was correct when first published. The public log shows whether the site has ever misstated that figure, and if so, how it was fixed. This transparency builds confidence that the site’s current numbers can be trusted for trade planning.

Keeping the log public also prevents silent edits that could mislead a reader who saw an earlier version. If a page had incorrectly stated the regulator for FxPro, a reader who acted on that information might have made a wrong decision. The log records that the correct statement is that FxPro is licensed by the FCA (UK), CySEC and FSCA, and the date it was corrected. Any reader can see the history and understand that the site does not hide its mistakes. This is essential for YMYL content where an error could affect financial risk.

The public log is a standing record that the site is accountable to its readers in the UAE, not an internal note. It is maintained even when no corrections are made, to show that the system is active. A reader can check the log before relying on any specific number, such as the contract size of 100 oz per standard lot or the pip value of 0.01 for gold. The log’s existence is itself a statement that precision is non-negotiable on this site, and that every error, however small, will be acknowledged and corrected openly.

The exact scope of errors tracked in the public log

The log tracks only errors in factual statements about gold trading, costs, regulation, and funding for the UAE market. This includes wrong numbers for contract size (100 oz per lot), pip size (0.01), reference price (≈4275.0), or margin examples (about $85.50 for 0.10 lot at the maximum leverage cap). It also includes wrong names of platforms (MT4, MT5, cTrader, FxPro Edge), wrong regulator (must state FxPro is licensed by the FCA (UK), CySEC and FSCA), or wrong funding methods (only Cards (Visa/Mastercard), bank transfer, e-wallets, and local UAE bank transfer).

The log does not include subjective judgments, such as whether a spread is good or bad, because no number is given for spreads. It does not include changes in market prices, because gold moves constantly and a reference price near 4275.0 is only a snapshot. It does not include typographical errors that do not change meaning, such as a missing comma in a sentence that does not affect a number. The scope is deliberately narrow: only errors that could cause a reader to miscalculate risk or cost on a gold trade in the UAE are logged.

Errors in any language or currency are logged if they affect the English site for UAE readers. A wrong AED conversion from USD, for example, is logged because it changes the local cost of a trade. A wrong statement about the maximum leverage cap of up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits, is logged even if the error appears in a footnote. The log is the single source of truth for corrections, and no error is too small to be recorded if it touches a number, a formula, or a regulatory fact.

Which gold trading errors make the cut for the public correction log

An error worth logging is any published figure on Gulf Bullion Desk that could affect a gold trade decision and is objectively wrong against the source data. For XAU/USD, that means a wrong reference price (the live price is around 4275.0), an incorrect pip definition (one pip equals 0.01), a wrong contract size (1 standard lot is 100 oz), or a misstated margin example. At 1:500 leverage, a 0.10-lot gold position needs about $85.50 margin; if we published a different margin figure, that is logged. Funding method errors count too, such as saying local UAE bank transfer is not available when it is. We log only numbers and facts a trader could rely on before placing an order, not stylistic wording or subjective phrases.

An error is logged when it appears in a context a UAE trader would reasonably use to size or time a gold trade. This includes our instrument specifications, margin calculations, trading platform details (MT4, MT5, cTrader, FxPro Edge), and funding options like cards, bank transfer, or e-wallets. We do not log a wrong date on an old news item unless that date is used for a trading decision. For example, if we stated that maximum leverage in the UAE is 1:100 instead of up to 1:500 on standard forex accounts, that is logged because it changes how much margin a trader expects to post. Errors in regulator references are also logged: FxPro is licensed by the FCA (UK), CySEC and FSCA, and any wrong regulator named is corrected publicly.

The test for logging is simple: could a trader in the UAE have placed a different XAU/USD order because of the error? If the answer is yes, it goes in the log. Material errors in gold pricing and execution are already covered elsewhere; this log adds the factual errors in our own content. A typo in a non-trading word is not logged. A wrong pip value for gold is logged because one pip is 0.01, and a trader using 0.1 would risk ten times more per pip. We also log errors in the currency symbol if we wrote USD instead of AED for local amounts. Every logged error must be traceable to a specific published sentence or figure, never a vague impression of inaccuracy.

How each gold correction is recorded, dated, and verified before it goes live

Each correction is recorded as a dated entry in the public log with the exact old text and the exact new text. The entry shows the date the error was found, the date it was fixed, and a one-line reason why it was wrong. For example, if we had written that 1 standard lot of gold is 10 oz, the log shows the old text, the new text (1 standard lot is 100 oz), and the correction date. The time is recorded in UAE local time. We do not backdate entries. If the same error appears in multiple pages, each page gets its own entry, because a trader may have seen only one of those pages. The log is updated within one business day of the fix going live.

Every correction is dated twice: the date the error was first published and the date the correction was published. The first date tells a reader how long the wrong figure was live. The second date tells them when they can trust the page again. We keep a screenshot of the original error and a link to the corrected page. For corrections that involve numbers, we show the calculation that proves the new number is right. For the margin example, we show that 0.10 lot at a reference price of 4275.0 with a contract size of 100 oz equals 10 oz of gold, and at 1:500 leverage the margin is about $85.50. The log entry includes this arithmetic in plain text, no formulas hidden.

Before a correction is published, two people check it against the source data: one trader and one editor. The trader verifies the market fact, such as that one pip for XAU/USD is 0.01, not 0.1. The editor verifies that the old text is quoted exactly and the new text fixes only the error without changing unrelated words. If the error is in a number, the source is linked where possible. For example, the reference price of 4275.0 is checked against the live feed at the moment of correction. After both checks pass, the correction is posted with a unique ID number. No correction is posted without this verification, even if the error seems minor.