Corrections Policy
Errors are fixed in place with a dated note, never silently.
How we fix errors
When we find an error in a published page, we correct the text at the same URL. We do not delete the page or hide the mistake. We add a note at the bottom of the page stating what was corrected and the date.
The note is plain text, not a pop-up or a separate page. It reads something like: Correction (15 June 2025): The leverage figure was changed from 1:500 to 1:200 to match the broker’s current terms.
How to report an error
If you see an error, email editor@kolargolddesk.com with the page URL, the incorrect text, and the correct information if you have it. We will check the source documents and update the page if needed.
We do not promise a response time, but we read all correction reports. If we decide a change is not needed, we may not reply. If we do reply, we will explain our reasoning.
Re-check vs. error
If a broker changes its terms after our check, that is not an error on our part. We note the date we read the documents. When we re-check, we update the numbers and the date.
An error is when we misread a document, typed a wrong number, or made a false claim. A change since the check is a re-check, not an error. We distinguish these in our notes.
What Qualifies as a Logged Error
An error is logged only when a stated fact about Kolar Gold Desk is demonstrably false, such as a wrong leverage cap, an incorrect lot size for gold, or a misnamed regulator. For example, if a page said maximum leverage is 1:100 when it is actually up to 1:200, that would be logged as an error. A wrong pip value for XAU/USD, like 0.1 instead of 0.01, also qualifies. The key test is verifiability against the facts we publish, not whether a reader dislikes the tone or disagrees with an opinion.
We do not log subjective wording changes as errors. Saying spreads 'may widen during news' is not an error if we never quoted a specific spread; it is a cautious statement. An error requires a concrete, checkable detail that contradicts the source data. For instance, if we wrote that 1 lot of gold is 10 ounces instead of 100 ounces, that is a clear error. Typos that change meaning, like ₹ instead of $ in a cost example, also count if they mislead about a number.
The bar for logging is high to keep the correction log useful. A logged error must have a material impact on a trader's understanding of cost or risk. If a page said a 0.10-lot gold position needs $855 margin instead of about $85.50 at 1:200, that is logged because it could cause a trader to misjudge capital requirements. Minor style issues, such as using 'e-wallet' instead of 'digital wallet', are not logged unless they obscure a fact.
How a Correction Is Dated and Recorded
Every correction is stamped with the date the change was made, using the format YYYY-MM-DD, and the time of the edit is not required because the log entry itself is immutable once published. The original erroneous text is preserved in the log alongside the corrected version, so a reader can see exactly what changed. For example, if we corrected a leverage figure from 1:100 to 1:200 on 2025-04-01, the log shows both the old and new value with that date.
The log entry includes a brief reason for the correction, such as 'wrong leverage cap corrected' or 'regulator name fixed'. We do not include the name of the person who made the error or the editor who fixed it, because accountability is to the text, not individuals. The correction is applied to the live page immediately, and the log is updated at the same time, so there is no window where the corrected page lacks a corresponding log entry.
If the same error appears on multiple pages, each page is corrected individually, but the log may reference a single root cause. For instance, if a wrong pip value was copied across three gold articles, the log states that the correction was applied to all affected pages, and each page shows its own correction date. The log never deletes an old entry; corrections are additive, so the history of the page's accuracy is transparent.
Correction Versus Update: How We Tell Them Apart
A correction changes a fact that was wrong at the time of publication, while an update adds new information that was not previously stated or changes a fact because the underlying reality changed. For example, if we wrote that FxPro is licensed by FCA, CySEC and FSCA, and that was true when written, adding a new regulator later would be an update, not a correction. A correction is for mistakes like saying the leverage cap is 1:500 when it is 1:200 for most traders.
Updates do not go into the correction log because they are not corrections of errors. If Kolar Gold Desk introduces a new funding method, such as a new e-wallet, we would update the deposit page and note it as an update, not a correction. The correction log only contains entries where the previous text was false. This distinction is important because it prevents the log from being cluttered with routine additions, which would make it harder to find genuine errors.
The test is simple: would a reasonable reader have been misled by the old text? If yes, it is a correction. If the old text was accurate but incomplete, it is an update. For example, if we originally wrote 'local INR bank transfers are supported' and later add 'UPI is also supported', that is an update because the original statement was not false. We never convert an update into a correction to inflate the log's size; the log is for accountability, not volume.
Why the Correction Log Remains Public
The correction log stays public because trust in a cost-analysis site depends on showing that we fix mistakes openly. A trader who sees that we corrected a wrong pip value for gold can verify that the current page is reliable. Hiding corrections would create doubt about whether other numbers, like the $85.50 margin example, are accurate. Public logging is a signal that we treat every figure about spreads, swaps and lot sizes as a claim that must be true.
A public log also provides a record for readers who may have acted on old information. If a trader used a wrong leverage cap to size a position and lost money, the log shows when the correction was made and what the correct value is. This is not a legal disclaimer; it is a practical aid. For example, if we corrected the margin requirement for a 0.10-lot gold trade from $855 to $85.50, a reader can see that the old number was wrong and recalculate their risk.
We do not delete or hide correction entries because that would erase the evidence of our own reliability. The log is not a marketing tool; it is a working record. A reader who checks the log and finds few entries should not assume perfection; it may mean errors were not caught. By keeping the log public and immutable, we accept that our mistakes are part of the record, and we invite scrutiny of every number we publish about gold trading costs.
What Goes Into the Public Error Log
A pricing, margin, or execution figure that we published and later found to be wrong is the core error we log. This includes any stated number for gold (XAU/USD) such as a spread, swap, overnight fee, margin requirement, or contract specification that was incorrect at the time of publication. It also covers wrong regulatory statements, such as naming the wrong regulator or omitting the SEBI caveat for FxPro Markets Ltd in India.
An error worth logging also includes a misstated funding method or a wrong leverage cap for Indian traders. For example, if we wrote that the maximum leverage in India is 1:100 when the facts allow up to 1:200 (or up to 1:500 after assessment), that is a logged error because it affects risk and margin decisions. We do not log subjective wording or style preferences unless a factual claim is false.
We also log errors in worked examples, such as an incorrect margin calculation for a 0.10-lot gold position. The correct figure at the maximum leverage of 1:200 is about $85.50 margin based on a reference price of 4275.0; any different figure is a logged error. If we state a cost as a fixed number without support, that is logged and corrected to what the cost depends on.
Correction Versus Update: The Dividing Line
A correction fixes a statement that was false at the time we published it, while an update changes a statement because the underlying facts changed later. For example, if we wrote that the maximum leverage in India is 1:200 and later the broker changes it to 1:500 for all clients, that is an update, not a correction. If we wrote 1:100 when the cap was already 1:200, that is a correction.
A correction applies retroactively: the original text was wrong on its publication date. An update applies only from the date of the change onward. We do not label an update as a correction, and we do not backdate an update. For gold (XAU/USD) costs, if a swap rate changes, we update the page with the new rate and a note that it changed on a specific date; we do not say the old rate was an error.
The difference matters because corrections affect trust and liability, while updates are routine maintenance. Our correction log only contains corrections, not updates. Updates are shown on the page with a 'last updated' date and a brief note about what changed. This separation ensures that readers can see exactly what was wrong and what simply became outdated.
Why the Public Correction Log Stays Open
The correction log stays public because transparency about errors is the only way to prove that our published trading costs and rules for gold (XAU/USD) are accurate today. Without a public log, a reader could never know if a spread or margin figure we published in the past was wrong. The log shows that we do not hide mistakes, and it allows anyone to audit our track record.
A public log also protects Indian traders who rely on our stated figures for risk decisions. For example, if we once published a wrong margin requirement for a 0.10-lot gold position, a reader who placed a trade based on that figure could have faced unexpected margin calls. By keeping the log public, we give traders the ability to check whether any past error could have affected their decisions.
Finally, an open log creates accountability. It forces us to be careful before publishing any number, because we know it will be permanently recorded if wrong. This is especially important for high-risk trading content involving leverage, swaps, and the SEBI regulatory caveat for FxPro Markets Ltd. The public log is our commitment to getting the numbers right.