Identity and prevention
of illicit use.

1. Purpose of this policy

Know-your-customer and anti-money-laundering measures seek to reduce the use of financial services to hide funds of illicit origin. They can also help prevent terrorism financing and other prohibited activities where the applicable framework requires it. This document explains the general process; the concrete obligations belong to each provider according to its activity and jurisdiction.

The site form collects contact details; it does not approve a financial account. The provider entity must state its requirements before requesting documents. A commercial enquiry is neither a complete verification nor an authorisation to trade.

2. What knowing the customer means

KYC is the verification of who uses a service and whether the details provided are consistent. The process can cross-check identity, address and ownership of a payment method. It is not limited to attaching a photograph: it must also make it possible to resolve discrepancies and update information when the user's circumstances change.

The documentation a provider requests must be related to its purpose. Before sending it, check the recipient, the channel and the handling policy. The fact that a person knows your name or phone number does not prove that they are authorised to carry out this verification.

3. Preventing money laundering

AML, or money-laundering prevention, covers risk assessment and, where appropriate, the monitoring of operations to detect patterns that require review. An unusual transaction does not by itself prove an offence: it may need an explanation, supporting documentation or the involvement of the provider's responsible team.

Controls cannot be bypassed by paying a fee or using several accounts. Splitting transfers to avoid limits can raise more questions and restrictions. The entity must apply its procedures in a way consistent with its obligations; the site does not promise that a review will be resolved in the user's favour.

4. Why identity is verified

Verifying ownership helps limit sign-ups with stolen data, third-party payments and fraudulent account recoveries. It also makes it possible to meet requirements that apply to the service you contract. An additional process may be necessary before sensitive functions are enabled, even when the contact email has already been confirmed.

The user should be able to tell which piece of data is requested and why. If a request does not explain its reason or demands that you share keys, do not complete it. Ask the provider for clarification on a channel independent of the message that raised the doubt.

5. Accepted documents and channels

No documentary list from the operating entity has been confirmed for this proposal. For that reason, this form does not request a national ID card, proof of address or biometric data. The provider must identify the accepted documents, their validity conditions and the secure mechanism for receiving them before the user hands them over.

If a document must be submitted, keep it legible and do not alter the details that need to be checked. Do not send full card numbers, banking keys or access secrets as a substitute for identification. A photograph or proof of presence should only be provided if the provider states its purpose and handling.

6. Stages of verification

The process begins with the entry of your details and continues, if you decide to contract, with the requirements stated by the entity. The entity may run automatic checks and refer cases with discrepancies for manual review. The result must be communicated through a recognised channel and must distinguish acceptance, a request for further information and rejection.

1. Review the provider's identity and its terms.
2. Complete the details required for sign-up.
3. Submit documentation only through the indicated channel.
4. Answer queries about inconsistencies without duplicating requests.
5. Wait for confirmation before using restricted functions.

Do not deposit to speed up a pending approval. A payment does not remove the obligation to verify details or guarantee that all services will be enabled.

7. Enhanced review

In higher-risk situations, the provider may need further information about activity, the origin of funds or the purpose of the relationship. Enhanced review should not be confused with an assessment of profitability. It may consider amounts, frequency, the complexity of the operation and relevant changes in the profile.

Ask for the necessary documentation to be identified and avoid supplying files that were not requested. Specific forms or tests that have not been confirmed are not described here. If you cannot gather the evidence, ask what alternatives the procedure accepts instead of altering a document.

8. Duration and follow-up

No fixed approval deadline is published because no operational timeframe has been confirmed for the provider entity. The duration can depend on the quality of the documents, the match between details, additional checks and the team's availability. An automatic acknowledgement of receipt is not the same as a completed review.

Keep the request number and ask for the status of the case if you hear nothing new. Submitting the same application several times can make its reconciliation harder. Before committing capital, check whether there are pending verifications that could affect withdrawals or the execution of operations.

9. Rejection or suspension

An expired, illegible, inconsistent or apparently altered document can prevent validation. The process can also stop if necessary details are missing or if the user does not meet the product's conditions. The decision should be understood within the provider's rules and not as a resolution issued by this site.

When an error can be corrected, ask which element needs updating and keep a record of the reply. Do not use another person's identity or open an alternative account to get around a restriction. Some reasons for review may not be detailed because of legal or security obligations.

10. Operations under review

Transaction monitoring belongs to the provider that executes, processes or holds custody. Where applicable, it may require explanations about a movement or limit certain functions while it analyses it. This information site does not carry out complete monitoring of balances and cannot confirm that a movement has passed a third party's internal controls.

Keep records of origin, ownership and destination to answer a query. Check the status of a transfer and the status of the account separately. A payment showing as credited does not prove that a later withdrawal is free of reviews.

11. User responsibilities

Your details must be genuine, accurate and kept up to date. Report changes to your contact details, address or relevant circumstances through the established channels. Do not present other people's documents as your own and do not allow another person to trade using your identity without an authorisation the provider accepts.

False information can lead to rejection, suspension or legal consequences depending on the case. Before sending a correction, check that it matches the rest of your details. Cooperating with a review does not mean giving up the right to ask how the information is used and protected.

12. Retention and protection

Verification documents must be handled with access and retention controls appropriate to their purpose. The entity's retention periods depend on its obligations and are not replaced by the period applicable to a commercial enquiry. Immediate deletion may not be possible when there is a duty to keep records.

The Privacy Policy explains how the data received by the site is handled. If the provider requests additional documents, read its policy too: the storage location and the parties responsible may differ. Ask for clarification before sharing sensitive data.

13. Possible recipients

When a verification service or a technical provider is involved, it should receive only the information necessary for its function. Communications to authorities depend on a valid obligation or request. It is not claimed here that a specific biometric provider or international transfer exists unless this has been confirmed.

The identity of the operational recipient must be stated before you contract. Completing a form does not authorise the open publication of your documents. If you are asked to send information to a different address, check its relationship to the service and request an explanation of the change.

14. Scope of local requirements

The specific activity determines which requirements of Bangladesh may apply. The use of a trade name does not prove a registration or amount to a licence to provide financial services. The regulatory details of this proposal remain pending confirmation and must be completed with the entity's actual identity and activity.

See the licences page to learn what information you should verify. A registration, where one exists, does not remove investment risk or represent a guarantee of the assets. This explanation does not replace legal advice for a particular situation.

15. Questions about identification

Write to [email protected] with the case number and a description of your query. Say whether you need to know a requirement, correct a detail or verify the legitimacy of a request. Do not attach identity documents to the first message.

The team can point you to the correct channel; the verification decision belongs to the responsible provider. If the problem is not resolved, you can use the complaints procedure, keeping the exchange and an explanation of the steps already taken.