Contact the Desk

The one mailbox

The editorial mailbox is editor@zabeeltokenae.com and it is the only address the desk uses. Messages sent anywhere else will not reach it, and there is no phone line or live chat attached to this site.

Write in English and say plainly what the message is about, including the page or broker it refers to. The desk reads everything, but it does not promise a response time, and it cannot take on every message that arrives.

What we can and cannot answer, and the response time to expect

We can answer factual questions about Zabeel Token's content, the BTC/USD instrument specification (1 lot = 1 BTC, pip = 1.0), platform features on MT4, MT5, cTrader and FxPro Edge, and the regulatory status of the entity that serves the UAE, FxPro Global Markets MENA Ltd., which is licensed by the FCA (UK), CySEC and FSCA. We can also explain how margin is calculated at the maximum leverage available in the UAE (up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits; varies by instrument). We cannot give personal trading advice, recommend a position, or predict bitcoin prices.

We cannot answer questions that require access to your account, such as changing your password, verifying your identity, or releasing a withdrawal. We cannot recover funds, reverse a trade, or intervene in a dispute with the broker. We cannot provide personal advice on whether to buy, sell, or hold bitcoin, or on how much leverage to use. For account access, fund recovery, or personal advice, contact FxPro directly through its official support channels; the contact details are on the FxPro website. This desk is editorial and cannot act on your account.

Expect a response within two business days for most messages, and within five business days for correction requests that need checking against source records. Messages that arrive on a UAE public holiday are treated as received on the next business day. We answer in the order received, but correction requests about factual errors are prioritised over general queries. If your message lacks the details needed to investigate, we will reply asking for them, which restarts the response window. We do not send automated acknowledgements, so if you do not hear back within the window, resend with the original message attached.

The response time to expect

Plan for a response within two business days. The desk aims to reply sooner for simple factual questions, but two business days is the window you should allow before following up. Messages sent on a Friday or public holiday in the UAE will be handled on the next business day.

Response time depends on the complexity of the question and the volume of messages. A platform fault with a clear screenshot is usually quicker to answer than a data discrepancy that needs checking against the feed. If your message lacks the details listed above, the desk will have to ask for them, which adds a round trip.

You will receive a reply to the email address you wrote from. If you do not hear back within two business days, check your spam folder before resending. Do not send the same message multiple times, as that can slow down handling for everyone.

What to send for each kind of question

For a platform or chart problem, send the platform name (MT4, MT5, cTrader or FxPro Edge), the instrument code BTC/USD, the timeframe, the exact time in UAE time, and a screenshot showing the issue. Include your account type and whether the problem occurs on demo or live. This lets the desk reproduce the fault instead of guessing.

For a data or price discrepancy, send the timestamp, the price you saw, the price on another source, and the chart screenshot. State whether the price was a bid, ask or last, and the lot size if relevant. The desk can then check the feed against the reference price of approximately 77000.0 and tell you whether the difference is expected or a fault.

For a funding or withdrawal question, send the method used (card, bank transfer or e-wallet), the amount in AED, the date and the reference number. Do not send full card numbers or passwords. The desk can trace the status but cannot access your account or move funds; those actions sit with the broker's client services team.

Requests the desk must redirect and where they actually go

The desk cannot open, close, fund or unfund an account, reset a password, lift a verification hold or recover money sent to the wrong place. Those are account and payment operations handled by the broker's own support, because they require identity checks the desk cannot perform. If you write here about a missing deposit, a locked login or a withdrawal delay, you will be redirected to the broker's support channel. Sending account details here does not speed up an account case.

The desk cannot give personal trading advice, cannot recommend a position size for your savings, and cannot tell you whether bitcoin will rise or fall. It also cannot act as an intermediary in a dispute or promise an outcome. Trading with leverage is high-risk and losses can exceed deposits; the published risk warning is the extent of what the desk can say about your exposure. For advice on your own finances, use a licensed adviser who can assess your full position.

The desk cannot confirm tax treatment or legal rights, and it cannot verify a payment method outside the published list of cards, bank transfer and e-wallets, including local UAE bank transfer. It cannot change a regulator statement beyond the permitted wording that FxPro is licensed by the FCA (UK), CySEC and FSCA. Knowing these limits saves a round trip: account and money questions go to the broker, advice questions go to a licensed adviser, and factual questions about the published pages stay here.

No guest posts and no paid placement

The desk does not accept guest posts, sponsored reviews or paid placement at any price. There is no rate card, no sponsored slot and no arrangement under which a broker can pay to appear, to be described differently or to have a page removed.

This is a deliberate limit rather than a negotiating position. The only commercial relationship on the site is the affiliate link, and it does not buy influence over what a page says. Messages offering payment for coverage will not be answered.

How a correction request is logged, checked and answered

A correction request is logged with the page URL, the quoted sentence and the source you supply, then checked against the facts the page is allowed to state. If the page has misstated a figure or a regulator name, the correction is made and you are told what changed. If the page is accurate but unclear, the wording may be tightened without changing the fact. You will receive a reply either way, so you know the request was read rather than filed silently.

The check is against the published facts, not against opinion. A claim that a spread or fee is too high is not a correction unless a stated number is wrong; costs consist of components that depend on the instrument, the platform and market conditions, and the page does not publish a spread number to correct. A claim that the regulator caveat is incomplete is checked against the exact wording the site is permitted to use, which is that FxPro is licensed by the FCA (UK), CySEC and FSCA.

Corrections that affect a number, a regulator name or a risk statement are treated as higher priority than style preferences. If your request concerns a margin example, quote the position size and the leverage cap you are checking; the published example is a 0.10-lot bitcoin position at 1:500 within DFSA/SCA-compliant limits needing about $385.00 margin. The reply will confirm whether the example stands or has been amended, and the page will show the corrected text rather than a note hiding the change.

What we can and cannot answer (no personal trading advice)

We can answer factual questions about how the platform works, what a field means, how margin is calculated, and where to find a setting. For example, we can confirm that at 1:500 on standard forex accounts, within DFSA/SCA-compliant limits, a 0.10-lot bitcoin position needs about $385.00 margin. We can explain the formula, but we cannot tell you whether to take that position.

We cannot give personal trading advice. That means no recommendations on whether to buy or sell BTC/USD, no suggested lot sizes for your account, no stop-loss or take-profit levels, and no view on where the price will go. Those decisions depend on your circumstances, and we are not authorised to make them for you.

We also cannot answer questions that require access to your account, such as checking your balance, resetting a password, or confirming a withdrawal. Those requests must go to the broker's client services. We can explain the process and what to expect, but we cannot act on your account or recover funds.

What the desk will and will not help with

The desk will help with editorial matters: a fact that looks wrong, a broker document that has changed, a page that is unclear, or a correction you want to report. Those messages are the reason the mailbox exists and they are read with care.

The desk will not help with account problems, will not chase a broker on your behalf and will not attempt fund recovery. It cannot give personal advice on whether to trade, how much to risk or which account to open, and it is not a broker, bank or licensed adviser. For anything involving your money at a broker, contact that broker directly and, where needed, the relevant regulator.

Questions the desk can answer and the personal advice it cannot give

The desk can explain how the published material works: what a pip is on BTC/USD, how 1 standard lot equals 1 BTC, how margin is calculated at a stated leverage cap, and which platforms FxPro offers. It can clarify the regulator caveat that FxPro is licensed by the FCA (UK), CySEC and FSCA, and explain that the entity serving the UAE is FxPro Global Markets MENA Ltd. It can also confirm what a page says and whether a correction has been made. These are factual, checkable answers.

The desk cannot tell you whether to buy or sell bitcoin, where to place a stop, how much of your savings to risk, or whether a position suits your circumstances. That is personal trading advice, and it is outside what a contact desk can provide. Trading bitcoin with leverage is high-risk and you can lose more than you deposit in fast markets; no message from the desk changes that. If you need advice on your own situation, speak to a licensed adviser who can see your full financial position.

The desk also cannot confirm tax treatment, legal outcomes or whether a past price will repeat. It can point to the published risk warning and the platform documentation, but it cannot interpret rules for your case. Questions about account opening, identity checks or a specific deposit are account matters and go to the broker's support channel, not to this desk. Keeping the boundary clear means factual questions get answered faster and personal advice is not given by someone who cannot know your circumstances.

What to send for a Bitcoin (BTC/USD) chart or data query

Send the exact BTC/USD chart or data query with the platform name, instrument code, timeframe, and the bar timestamp in UAE time. Include what you expected to see and what appeared instead, plus a screenshot or screen recording if the issue is visual. For example, state that on MT5 the BTC/USD 1-hour candle at 14:00 UAE time showed a high of 77100.0 when the reference price was near 77000.0. Without the platform, timeframe, and timestamp, the desk cannot reproduce the issue and your message will be redirected.

Send the order or position details for any BTC/USD execution query: ticket number, lot size (1 lot = 1 BTC), open and close times, and the price you received versus the price you expected. Note the pip value (1 pip = 1.0) and whether the position was opened or closed manually or by a pending order. If the query concerns margin, include the leverage cap that applied (up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits; varies by instrument) and the margin amount you saw, such as about $385.00 for a 0.10-lot position. These details let the desk check the record rather than guess.

Send funding or withdrawal queries with the method used (card, bank transfer, or e-wallet), the amount in AED or the currency you sent, and the date and time of the transaction. For local UAE bank transfers, include the bank name and the reference number shown on your statement. Do not send full card numbers, passwords, or one-time codes. If the query is about a declined card payment, state the card type (Visa or Mastercard) and the error message you saw. The desk can then check the payment status and tell you what the next step depends on.

The details that make a message answerable on the first pass

A useful message states one question, the page or platform it concerns, and the exact figures involved. For a BTC/USD question, include the lot size, because 1 standard lot equals 1 BTC and one pip is 1.0, so the cash value of a move depends on both. For a margin question, include the leverage cap you are applying; the published example uses 1:500 within DFSA/SCA-compliant limits, where a 0.10-lot position needs about $385.00 margin. These details let the desk check the arithmetic instead of guessing.

For a platform issue, name MT4, MT5, cTrader or FxPro Edge and give the time with the time zone, plus the ticket number and a screenshot. For a funding question, name the method (card, bank transfer or e-wallet) and, for a local UAE bank transfer, the sending bank and reference. Do not include passwords or full card numbers. A message that names the thing, the time and the reference can be traced; a message that describes a feeling cannot.

For a correction, the useful message quotes the sentence, gives the URL and supplies the source. For a general question, say what you already understand and where the confusion starts, so the reply can be specific rather than a repeat of the page. Keep the message to the point and avoid attaching large files; a screenshot and a receipt image are enough. If you are unsure which category your question falls into, say what you are trying to check and the desk will route it.

What to include when you write about a platform, chart or data problem

Send the exact instrument code, the platform name (MT4, MT5, cTrader or FxPro Edge), the time and time zone of the issue, the order or ticket number if one exists, and a screenshot showing the chart or error. For bitcoin, state BTC/USD and the lot size, because 1 lot equals 1 BTC and a pip is 1.0, so a small price move can look large in cash terms. Without the ticket number and timestamp the desk cannot match your report to a server log.

For a funding question, send the payment method used (card, bank transfer or e-wallet), the amount and currency, and the reference shown on your receipt. If you used a local UAE bank transfer, include the sending bank name and the transfer reference so the payment can be traced. Do not send full card numbers, passwords or one-time codes; the desk does not need them and they create a security risk. A masked receipt image is enough to start a trace.

For a correction request, send the page URL, the exact sentence you believe is wrong, and the source or fact that supports your correction. If the issue is a number, quote the figure as published and the figure you believe is correct, with the date you checked it. For a general question about how a cost or margin figure is calculated, name the instrument and the position size; for bitcoin at 1 lot = 1 BTC, a 0.10-lot position at 1:500 within DFSA/SCA-compliant limits needs about $385.00 margin, which helps the desk check your arithmetic.

The response window you should plan around

Expect a reply within two to three business days for most messages, counted from the next UAE business day after receipt. Messages sent on a Friday or over a public holiday start the clock on the next working day. The desk is small and reads every message in order, so a same-day reply is not promised. If your question is about a live platform fault, say so in the subject line; it is read earlier but still answered in the queue.

Correction requests with a specific URL and a supporting source are usually answered before general questions because they affect what other readers see. A message that asks for personal trading advice will receive a short reply pointing to the risk warning and will not receive a market view. A message missing the ticket number, timestamp or page URL may receive a request for those details, which restarts the response window once they arrive.

The response time depends on the volume of messages and on whether your first message contains everything needed. A complete message about a BTC/USD order with the platform name, ticket number, time and screenshot can be checked in one pass; a message that says only that something went wrong cannot. Plan around the two-to-three business day window rather than an instant reply, and do not send the same question twice, because duplicates slow the queue for everyone.