Corrections Policy
Errors are fixed in place with a dated note, never silently, and a reader can report one through the editorial mailbox.
Fixed in place, with a date
An error is corrected in place and marked with a dated note so the change is visible to anyone who read the page before. The desk does not delete a wrong figure and replace it quietly, because a silent edit hides the fact that the site was once wrong. The note says what changed and when.
Corrections are kept short and factual. They describe the original claim, the corrected claim and the source document used to settle it, so a reader can check the same source.
How to report an error
Send the report to editor@riftcompareke.com with the page address and the sentence or figure in question. If you have the broker document that shows the correct position, include it, because that speeds up the check. The desk does not promise a response time in hours or days.
Reports are checked against the broker's own documents before anything is changed. If the report is right, the page is corrected and dated. If the desk cannot confirm the point from a source, the page is left as it is and the reader is told why.
A changed condition is a re-check, not an error
If a broker has simply changed its terms since the page was checked, that is a re-check, not an error. The original page was accurate on the date its source was read, and the fix is to update it to the new position with a fresh date. The corrections note records the re-check rather than treating the earlier figure as a mistake.
This distinction matters for costs and for eligibility, which move more often than platform facts. Readers should treat every figure as dated and confirm it with the broker before acting.
What earns a place in the correction log
An error worth logging is a factual statement on this site that is wrong, misleading, or unsupported by the source we cite, and that could change a reader's decision or calculation. A typo in prose does not qualify. A wrong pip value, a misstated margin figure, or a regulator caveat that names the wrong authority does. The test is whether a reasonable Kenyan trader acting on the page would be worse off because of the mistake. If the answer is yes, it goes in the log.
Errors that affect money calculations get priority. For gold (XAU/USD), one standard lot is 100 oz and one pip is 0.01, so a page that states the lot size or pip value incorrectly is a high-severity error even if the rest of the sentence reads well. A worked margin figure of about $85.50 for a 0.10-lot position at the applicable leverage cap is another example: if the number is wrong, the reader's funding plan is wrong. Those entries are logged first.
Errors that touch regulation and funding are also logged. Naming the wrong regulator for the entity serving Kenya, or implying that FxPro is licensed by the CMA of Kenya when the correct caveat is that FxPro is licensed by the FCA (UK), CySEC and FSCA but not by the CMA, is a correction-worthy error. So is naming a funding route that is not M-Pesa. The log records the wrong statement, the right one, and the date the fix went live.
How each correction is written down and dated
A correction is recorded as a dated entry that names the page, quotes the incorrect statement, states the corrected statement, and gives the date the corrected version was published. The date is the publication date of the fix, not the date someone first noticed the problem. Each entry is appended to the page's history, so the order of entries shows what changed and when. No entry is edited after publication; if the correction itself needs correcting, that becomes a new entry.
The entry also records the source used to settle the matter. For a margin figure, that means the leverage cap that applies to the entity serving Kenya and the contract size for gold (100 oz per standard lot). For a regulatory statement, it means the exact caveat text: FxPro is licensed by the FCA (UK), CySEC and FSCA, not by the CMA of Kenya. The source line lets a reader repeat the check without trusting us.
Dating is deliberately plain. We use the full date in the page history rather than a relative phrase like recently or last week, because relative dates decay. A reader returning months later can see exactly when a figure changed. If a correction affects a worked example, the entry states the old figure and the new figure side by side, so the difference is visible without opening an earlier version of the page.
Where a correction stops and an update begins
A correction fixes something that was wrong when it was published. An update changes something that was right when it was published but is no longer current. If we said a margin example needed about $85.50 at the applicable cap and that was correct on the day, but the cap later changes, the new figure is an update, not a correction. The distinction matters because it tells the reader whether to distrust the old page or simply to note that conditions moved.
The test is hindsight. Ask whether the statement was accurate against the sources available on its publication date. If yes, the change is an update and is marked as such. If no, it is a correction and carries the correction label. A page that mixed up pip size for gold, stating 0.01 as something else, was wrong on day one and is corrected. A page that listed M-Pesa as a funding route and later had to add a note about a change in how that route is handled is updated.
Updates still get dated entries, but they do not carry the same weight in the log. The page history shows both, labelled differently, so a reader can see the difference between us fixing our own mistake and the world moving under a statement that was once accurate. That labelling is the whole point: it keeps the record honest about which kind of change occurred.
Why the correction log is left open for anyone to read
The log stays public because a correction that only the publisher can see is not a correction, it is a private note. A reader in Kenya deciding whether to fund an account through M-Pesa and trade gold at the applicable leverage cap needs to know whether the page they are reading has a history of getting the margin example wrong. Hiding that history would make the site less useful precisely when the reader is checking whether to trust it.
Public logging also keeps us accurate. When every fix is visible and dated, there is no quiet edit that makes an old error disappear. The record shows the wrong statement next to the right one, which is uncomfortable but useful. It also gives readers a way to spot patterns: if the same class of error, such as a lot-size or pip-value mistake on XAU/USD, appears twice, the reader can weigh that when using the page.
The log is not a marketing page. It does not list only the corrections that make us look careful. It includes the ones that were embarrassing, such as a regulator caveat that named the CMA when the correct position is that FxPro is licensed by the FCA (UK), CySEC and FSCA and not by the CMA of Kenya. Keeping those entries visible is the cost of asking readers to rely on the rest of the page.
Three labels: error, update, clarification
Every change to a page carries one of three labels, and the label tells the reader what kind of change it is. Error means the page stated something false or unsupported and the statement has been replaced. Update means the page stated something that was accurate when published but is no longer current. Clarification means the original statement was accurate but ambiguous, and the wording has been tightened without changing the underlying fact. Each label has its own marker in the page history.
The labels are applied at the point of change, not afterwards. A correction to a margin figure, such as the worked example of about $85.50 for a 0.10-lot gold position at the applicable cap, is labelled error if the figure was wrong on publication and update if the cap itself moved. A clarification might add the words standard lot next to 100 oz so that a reader does not confuse it with a mini or micro lot. The label follows the reason, not the size of the edit.
Readers can filter the history by label. That matters because the three kinds of change carry different implications. An error label is a signal that the earlier page should not be trusted on that point. An update label is a signal that the earlier page was fine for its time but conditions have moved. A clarification label is a signal that nothing substantive changed. Mixing them would blur exactly the distinction the log exists to preserve.
Who signs off on a correction, and how long it takes
A correction is approved by the editor responsible for the page, and the approval is recorded with the entry. There is no committee and no anonymous fix. The person who signs off is the person accountable for the wording that replaces the wrong statement. For a regulatory caveat, that means the editor confirms the exact text: FxPro is licensed by the FCA (UK), CySEC and FSCA, not by the CMA of Kenya. For a margin example, the editor confirms the contract size and the applicable cap before the new figure goes live.
Timing depends on severity. A wrong number that affects money, such as a pip value or a margin figure, is treated as urgent and is fixed as soon as the correct figure is confirmed against the source. A wording problem that does not change the meaning waits for the next scheduled review. We do not publish a promised turnaround in hours because the real constraint is confirming the source, not writing the fix. The entry records the date the fix went live, not the date it was requested.
The editor also decides the label. That decision is recorded, so a reader can see whether a change was classed as an error, an update, or a clarification. If the editor is unsure whether the original statement was wrong on publication or merely became outdated, the safer label is error, because it warns the reader more strongly. The log shows the label and the date, and the reader can judge whether the call was reasonable.