Contact the Desk

The one mailbox

All editorial messages go to editor@bokchainzza.com. It is the only address the desk publishes, and it is read by the people who write and check the pages.

Please write in plain language and include the page or section you are asking about. A clear subject line helps the message reach the right person on the desk.

No guest posts and no paid placement

The desk does not accept guest posts, sponsored reviews or paid placement at any price. Links are not sold and rankings are not for sale.

If you are a broker or an agency offering payment for coverage, the answer is no, and it stays no regardless of the amount. Editorial independence is the only thing that makes these pages worth reading.

What a useful message contains so that an answer is actually possible

A useful message states the page or section, the specific point at issue, and what you want to happen. For example: 'On the margin example page, the sentence says a 0.10-lot bitcoin position needs about $385.00 margin at 1:200; I believe the arithmetic should be different because...' That gives us a location, a quote, and a reason. Without those three elements, we can only guess what you are referring to, and guessing wastes your time and ours.

Include the instrument code and any numbers exactly as they appear on the page, using Latin characters. If you are referring to a rand amount, write it as R followed by the figure. If you are referring to leverage, state the ratio as given, such as 1:200 for retail or up to 1:500 for eligible/professional clients depending on instrument. Do not paraphrase these details, because small changes in wording can alter the meaning and make your query harder to verify.

Tell us what you have already checked. If you have looked at the regulator caveat and you are still unsure which entity serves South Africa, say so. If you have compared two pages and found an inconsistency, name both pages. A message that shows your working is easier to answer than one that simply asserts something is wrong. We are not looking for perfect prose, but we do need enough context to reproduce your concern and check it against the site.

The response time to expect and what affects it

We aim to reply to most messages within a few working days, but the exact time depends on the volume of mail and the complexity of the question. A simple correction with a clear source is usually quicker to handle than a broad query that needs cross-checking against several pages. We do not promise a same-day reply, and we do not operate a live chat or a phone line. If you need an immediate answer for a live trade, this mailbox is not the right channel.

Response times are longer over weekends and public holidays in South Africa, and they can stretch when a single issue generates a large number of similar messages. We read every message, but we prioritise corrections that affect factual accuracy over general feedback. If your message is about a possible error in a rand amount, a regulator reference, or a calculation, say so in the subject line so it can be routed correctly. That does not guarantee a faster reply, but it helps us triage.

We do not send automated acknowledgements for every message. If you have not heard back within a reasonable period, you are welcome to resend once, but please include the original message below so we do not duplicate work. We cannot give an exact hour or day for any individual reply, because the queue changes daily. What we can say is that messages that are specific, sourced, and clearly scoped are handled more efficiently than vague ones.

What we can answer and what we cannot: no personal trading advice

We can answer factual and educational questions about how the site's content is put together, what a term means, how a calculation works, and where a particular figure comes from. We can explain, for instance, that a 0.10-lot bitcoin position at 1:200 leverage needs about $385.00 margin, and show the arithmetic behind it. We can also clarify the regulator caveat: FxPro is licensed by the FCA (UK) and CySEC, and an FxPro entity holds an FSCA licence in South Africa — check which entity your own account is opened with.

We cannot tell you whether to buy or sell bitcoin, how much of your portfolio to allocate, or what leverage setting to use. We cannot comment on your personal financial situation, your tax position, or whether a specific trade is suitable for you. Trading is high-risk, and any decision about a live position depends on facts about you that we do not have and should not collect. If your question is 'should I enter now?', the honest answer is that we do not answer it, and no reputable educational site should.

We also cannot confirm the current price of bitcoin, the spread on your account, or the exact fees you will pay, because those depend on your broker, your account type, and the market at the moment you trade. We can describe what a cost consists of and what it depends on, but we cannot quote a live number we were not given. For account-specific figures, you need to check your platform or your broker's documentation directly.

What we cannot do and where those requests actually go

We cannot access your trading account, reset your password, release a withdrawal, or recover funds. Those actions belong to your broker, and for FxPro the relevant entity for South Africa is FxPro Markets Direct Costa Rica Latam SRL. If your account is with a different entity, check your statements and the regulator caveat: FxPro is licensed by the FCA (UK) and CySEC, and an FxPro entity holds an FSCA licence in South Africa — check which entity your own account is opened with. Contact that entity's support, not this mailbox.

We cannot give personal trading advice, recommend a position size, or tell you whether to use the maximum leverage available. Leverage is a cap, not a setting to aim at, and the right level depends on your circumstances. We also cannot help with fund recovery from a third party, mediate a dispute with a broker, or provide legal or tax advice. For those matters, you need a qualified professional in South Africa or the relevant jurisdiction, and possibly the Financial Sector Conduct Authority if you have a regulatory complaint.

We cannot confirm live prices, spreads, swaps, or minimum deposits as numbers, because we were not given those figures and they change. We can explain what a cost consists of and what it depends on, but we cannot quote a specific spread or fee. If you need those numbers for a decision, use your platform's contract specifications or ask your broker directly. This site is an educational toolkit, not a substitute for your broker's disclosure documents or your own due diligence.

What we will and will not help with

We will help with questions about what a page says, where a figure came from and when it was last checked. We will also take a correction or a pointer to a broker document we may have missed.

We will not help with account problems, deposits, withdrawals, frozen balances or fund recovery, and we do not give personal advice on whether to trade or what to trade. Those matters belong with your broker and, where relevant, with the regulator named in your account documents.

How a correction request is handled from receipt to resolution

A correction request is logged, checked against the facts we hold, and either accepted, rejected with a reason, or sent back for more information. We compare the quoted text with the source you provide and with the internal reference for that page. If the correction is straightforward, such as a wrong rand symbol or a misstated lot size, we fix it and note the change. If it challenges a figure we were given, we check whether the original fact still stands before altering anything.

We do not publish a public changelog for every correction, but we do update the page when a change is made. If your request concerns a regulator caveat or a leverage cap, we treat it with particular care because those statements affect how readers understand risk. We will not change a factual statement simply because a reader prefers a different wording; the test is whether the current text is accurate against the facts we are allowed to state. Opinion is not a correction.

If we accept a correction, we do not usually reply with a detailed explanation of every edit, but we may confirm that the page has been updated. If we reject it, we aim to tell you why in one or two sentences, often because the source does not support the change or because the original fact was correct. We do not enter into long debates about style. The purpose of the process is accuracy, not consensus, and it is not a route to having your own preferred claims published.

What to send with each type of question: corrections, data queries, and general feedback

For a correction request, send the exact page URL, the quoted sentence or figure you believe is wrong, and the source that shows the correct version. Without the URL and the quote, we cannot locate the text quickly, and without a source we cannot verify the claim. If the issue concerns a rand amount or a regulatory reference, include the relevant document or link so we can check it against the facts we hold. A screenshot is helpful but not a substitute for a working link or a clear citation.

For a data query about bitcoin (BTC/USD) pricing, lot sizes, or margin, tell us the instrument code, the lot size you are working with, and the platform or context you are asking about. For example, state whether you mean 0.10 lots or 1 standard lot, and whether you are looking at MT4, MT5, cTrader, or FxPro Edge. Include the reference price you are using if your question depends on a specific level, such as the ≈77000.0 reference. That lets us point you to the right explanation rather than guess.

For general feedback about the site, say which page or section you are commenting on and what you expected to find. If you are suggesting an addition, describe the gap in one or two sentences and, if possible, the type of reader it affects. We do not need your life story or your trading history. A short, specific note is easier to act on than a long account of a general frustration, and it helps us decide whether the issue is a one-off or a pattern across the site.