Privacy Policy

Flowbit Privacy Policy Flowbit Finance L.L.C-FZ Version dated 17 October 2026 This Policy explains what personal data is processed when the Flowbit service (the “Service”) is used, why it is needed, with whom it is shared, how it is stored and how the user can exercise their rights. 1. General provisions 1.1. This Policy applies alongside the Flowbit Terms of Use. The Terms govern the provision of services, while this Policy governs the processing of personal data. Reading this Policy does not, by itself, constitute consent to every possible use of data. 1.2. We process data only to the extent necessary for the specific purpose and on an applicable lawful basis. Where separate consent is required for particular processing, it is requested before that processing begins. 1.3. Mandatory rules on the protection of personal data take precedence over this Policy and contractual limitations of liability. The applicability of those rules depends on where the parties operate, the category of data, the circumstances of the processing and the connection with the relevant jurisdiction. 2. Who processes the data 2.1. Flowbit Finance L.L.C-FZ (the “Company”, “Flowbit”, “we” or “us”) is registered in Meydan Free Zone, Dubai, U.A.E. Registration number: 2541754. Registered address: Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, U.A.E. Contact for data-related enquiries: company@flowbitfinance.com. 2.2. Flowbit determines the purposes and means of processing data for the account, its own service functions, support, the arrangement of transactions, identity verification and security. In this respect, Flowbit acts as a controller of personal data or performs the corresponding role under applicable law. 2.3. Partners may process data on Flowbit’s documented instructions or independently for their own services and legal obligations. Their role is determined by the processing actually carried out, the law and the contract. Sharing data with a partner does not discharge Flowbit’s own obligations. 3. Services covered by this Policy 3.1. This Policy covers the Flowbit website, app and Telegram interfaces, registration and login, the issuance and servicing of available cards, top-ups, the display of card balances and transactions, identity verification, support, refunds and transaction disputes. 3.2. User balances are recorded against specific cards. This Policy does not provide for a standalone user wallet or a separate Flowbit balance. Processing balance information does not determine who is obliged to return the corresponding funds: those obligations are governed by the Terms, the product documents and the law. 3.3. Where a new feature requires additional data, purposes or recipients, the user is provided with the necessary information before the relevant processing begins, and consent is requested where required. 4. What data is processed 4.1. Account and contact data: user identifier, first and last name, Telegram ID and username, language, profile image and other available Telegram profile information; email address, telephone number and country, if provided or required for the selected feature. 4.2. Usage data: settings, registration and login dates, available features, information on navigation and interaction with the interface, acquisition source and referral information, the history of notifications provided through the service and communication preferences. 4.3. Card and transaction data: card identifiers and statuses, card balances, amounts, currencies, exchange rates, fees, limits, information on merchants and transaction categories, dates, statuses, identifiers and references to transactions with partners, refunds and disputes. The data involved depends on the selected card programme and transaction. 4.4. Cryptocurrency payment data: asset, network, wallet address, transaction hash, amount, network confirmations, necessary payment identifiers and payment verification results. 4.5. Identity verification data: the selected document, the information it contains, images of the document and materials used to check the presence of a live person in front of the camera — Liveness. Flowbit also processes necessary extracted identification information, session identifiers, statuses, attempt history and the reasons for the verification result. Section 12 describes Neurovision’s involvement. 4.6. Support data: the text of conversations with the bot and a support agent, information about the enquiry and related transactions, and explanations and attachments submitted by the user. Images and screenshots relevant to the enquiry may be processed to investigate errors. 4.7. Technical and security data: IP address, browser, operating system, app version, device and session information, login logs, errors, failures, security events, activity check results and indicators of possible fraud. 4.8. Data relating to requests to exercise legal rights: the content of a personal data request, information necessary to verify the requester, responses provided, and records of specific consents and their withdrawal where consent is used. 4.9. Listing a category does not mean that all data in that category is collected from every user. Additional documents relating to a payment, ownership of a payment instrument or source of funds are requested only where there is a specific need and a lawful basis. 5. Sources of data 5.1. The user provides data through the service interfaces, the verification form, support messages and necessary documents. Technical events are generated when the service is used and transactions are carried out. 5.2. Telegram provides the information associated with the selected login method and interaction with the bot. Using Telegram to log in does not, by itself, give Flowbit access to all of the user’s private correspondence or contacts. Flowbit processes messages sent to its own service and support channels. 5.3. Card and payment partners, Neurovision and other engaged service providers supply necessary verification results, transaction information and technical statuses. Publicly available sources, including the blockchain and applicable restriction lists, are used within lawful limits to assess specific transactions and risks. 6. Why data is needed 6.1. To provide the service: registration and login, processing card issuance and top-up requests, displaying transactions and balances, calculating fees, operating enabled features and communicating about them. 6.2. To verify identity and transactions: confirming user information, preventing the use of other people’s documents or funds, checking eligibility for the selected product and fulfilling applicable obligations. 6.3. To provide support: handling enquiries, investigating errors, restoring access, preparing responses and processing refunds or disputes. Automated analysis of conversations and images is described in section 10. 6.4. For security: protecting the account and infrastructure, detecting unauthorised access, fraud, abuse and technical failures, investigating incidents and restoring operations. 6.5. To comply with the law and protect rights: fulfilling specific record-keeping and retention obligations, responding to lawful requests, handling claims and defending Flowbit’s position in disputes. 6.6. For necessary technical analytics: monitoring availability, errors, performance and the correct operation of features. Such processing is limited to necessary data; anonymised or aggregated information is used for summary statistics where the purpose allows. 6.7. Data is not used for an incompatible new purpose without a separate lawful basis and the necessary information being provided to the user. Processing for advertising purposes is governed by section 17. 7. Lawful bases for processing data 7.1. Flowbit processes personal data on the following bases where permitted by applicable law: ●     entering into and performing a contract with the user — for registration, providing the selected services, processing transactions and support; ●     fulfilling obligations imposed by law — including necessary checks, reporting and record retention; ●     bringing, handling or defending legal claims; ●     the user’s consent — where required for the relevant processing. For each purpose, Flowbit determines the applicable basis and the data required. 7.2. Identity verification and the sharing of information with card, payment and other partners are carried out only to the extent necessary and where a lawful basis exists. A partner’s requirements do not, by themselves, replace such a basis or the user’s consent where consent is mandatory. 7.3. Where processing requires consent, Flowbit requests it before processing begins and explains what data will be used, for what purposes, with whom it will be shared and how consent can be withdrawn. This also applies to the processing of facial images and Liveness materials where consent is required. Simply reading this Policy does not replace separate consent. 7.4. The user may withdraw consent at any time through support or another available method specified when consent was obtained. Flowbit stops processing based on the withdrawn consent. Withdrawal does not affect the lawfulness of processing already carried out. Data may be retained and processed further only where an independent lawful basis exists, such as a retention obligation or the need to defend a specific legal claim. 7.5. If the selected service cannot be provided without certain data or its lawful processing, Flowbit informs the user and may restrict the relevant feature, subject to legal requirements. Refusal of processing that is not necessary for the core service does not, by itself, prevent use of that service.   8. Security and automated checks 8.1. Transaction history, the frequency of attempts, technical indicators, identity verification results, enquiries and information about related payments may be analysed to check transactions and prevent abuse. This assessment may include automated data matching and risk profiling. 8.2. A check may result in a request for clarification, further verification or a restriction on a feature within the authority of Flowbit or the relevant participant. Restrictions on the service and transactions are also governed by the Terms of Use. 8.3. The user may report an error, provide explanations and request a review. Where required by law, human involvement is provided in the review of a decision based solely on automated processing. A Neurovision check or an automated support response does not prevent such a request. 8.4. Information may be withheld where its disclosure is prohibited by law or would enable security measures to be bypassed. This does not constitute a general refusal to explain a status, correct inaccurate data or consider a lawful request from the user. 9. Card and cryptocurrency transactions 9.1. Flowbit and the relevant participants process information about the request, payment, authorisation, crediting of funds, settlement and refund as separate stages of a transaction. This is necessary for accurate record-keeping, status display, reconciliation and investigation of errors. 9.2. A wallet address, transaction hash and other public blockchain information may be linked to a specific user. A public blockchain record is not deleted as a result of account closure or the deletion of data from Flowbit’s systems. Information managed by Flowbit is handled under sections 14 and 16. 9.3. Do not send private keys, seed phrases, passwords, PINs or one-time login or payment confirmation codes to support. Such information is not required for the ordinary handling of an enquiry. Payment details and information unrelated to the reported issue should be obscured in screenshots. 10. Support and automated analysis of enquiries 10.1. Flowbit processes conversations with the bot and a support agent to identify the subject of the enquiry, locate the related transaction, prepare a response, investigate an error and arrange further handling. Access is granted to employees and service providers who need it for these tasks. 10.2. OpenAI models accessed through the OpenRouter technical platform are used for automated analysis and the preparation of responses. The text of the enquiry and the necessary context from conversations with the bot and a support agent are submitted for processing. Relevant images and screenshots sent by the user may be submitted to investigate a reported error. 10.3. Data shared with these services is limited to what is necessary for the enquiry. Original documents provided for KYC are not part of the ordinary support context and must not be automatically included in requests to a language model. The user should not send excessive personal data or confidential credentials through support. 10.4. An automated response may contain an error. The user may request review by a support agent, correction of information or verification of a decision. Automated analysis of conversations does not, by itself, constitute a final decision on the user’s rights, the return of funds or blocking. 10.5. Providers of automated processing receive data for the relevant support task. Using private correspondence to train publicly available models is not among Flowbit’s processing purposes under this Policy. The terms on which providers are engaged and the processing settings must be consistent with those purposes; this Policy does not guarantee immediate deletion or the absence of all technical logs. 11. Technical tools and necessary analytics 11.1. Cookies, local storage, technical logs and similar tools may be used for authentication, maintaining sessions and user settings, security, diagnosing failures and operating the interface. 11.2. Necessary technical analytics is used to support the availability and correct operation of the service. Describing a tool as an analytics tool does not, by itself, make every one of its functions necessary: recording user behaviour, advertising tracking and building advertising audiences are considered separately. 11.3. Under this version of the Policy, the service does not use advertising pixels, user session recording for marketing or other optional analytics. Any subsequent introduction of these features requires prior disclosure of information, an appropriate lawful basis and, where required, separate consent with the option to refuse. 11.4. The user can manage cookies and local data through their browser or device. Disabling tools that are essential to maintaining login, security or the selected feature may affect its operation. The arrangements for processing necessary technical information must not be used for concealed advertising tracking. 12. Who may receive personal data 12.1. Data is shared to the extent necessary and on a lawful basis with: card programme participants for issuing and servicing cards and processing transactions; payment and cryptocurrency processors for receiving, checking and refunding payments; identity verification and security service providers; and hosting, communications and support providers. 12.2. Neurovision is used for identity verification. The contracted provider is NEUROVISION GLOBAL INTELLIGENCE - FZCO, registration number 72252, UAE. When carrying out KYC checks, the provider processes data in accordance with Flowbit’s documented instructions. Flowbit determines the purposes of this processing and handles user requests relating to it. 12.3. The user submits their selected identity document and completes a Liveness check through the Neurovision interface. The original images and materials from this check are stored by Neurovision. Flowbit receives the necessary identification details, verification results and technical statuses and uses them to provide the service and for security purposes. 12.4. Regular support staff do not have access to original documents or Liveness materials. Access to these materials held by the provider may be granted to a specifically authorised Flowbit representative where required for their duties, within the scope of their authority and applicable requirements. Flowbit does not maintain a separate permanent repository of original KYC documents in its own systems. 12.5. OpenRouter and the provider of the OpenAI model used participate in the automated processing of support requests described in section 10. Telegram provides the relevant sign-in and messaging channel. Their independent processing of data for their own services must be distinguished from processing commissioned by Flowbit for its own service functions. 12.6. Data may be disclosed to professional advisers, courts, regulators and other competent authorities where there is a lawful basis. In a reorganisation or transfer of the business, access is limited to necessary data and is subject to confidentiality safeguards; a change in business ownership does not, in itself, permit incompatible use of data. 12.7. When engaging processors, Flowbit specifies the permitted purposes and instructions, together with requirements for security, confidentiality, assistance with user requests, incident notification, and the return or deletion of data. An independent controller is responsible for its own processing under applicable law; Flowbit’s own obligations remain in place. 12.8. The user may request the information required by law about the recipients of their data and their roles. Commercial confidentiality of contracts does not replace mandatory disclosures about personal data. Details that must be disclosed before particular processing begins are provided before it begins. 13. Processing data outside the user’s country 13.1. The operation of Flowbit and international card, payment, verification and technology services may involve transferring data to the UAE and other countries where the relevant service providers, servers, backups or persons with authorised remote access are located. A provider’s place of incorporation does not, in itself, determine where data is stored. 13.2. Each transfer must have an applicable legal basis and the necessary safeguards: recognition of an adequate level of protection under the law, contractual safeguards, an applicable exception or another permitted basis. A statement of agreement with this Policy alone does not satisfy these requirements. 13.3. Information about cross-border transfers required by applicable law is provided before processing begins. The user may request information about the relevant countries, categories of recipients and safeguards. If the processing route changes, Flowbit assesses the implications and meets the applicable information and consent requirements. 14. How long data is retained 14.1. The retention period is determined separately for each category and purpose. Data is retained for the period necessary for that purpose and for any additional period required by law. No uniform minimum retention period of five years is established for all user data. 14.2. Account data and contact details are retained for the duration of the service relationship and, after closure, to the extent and for the period necessary to complete transactions, resolve outstanding requests and fulfil specific legal obligations. 14.3. Information about transactions, fees, refunds and disputes is retained for the periods applicable to record-keeping, mandatory retention, and bringing or defending claims. The period and its starting point depend on the category of record and the specific obligation. Any extension due to a dispute applies to information relevant to that dispute, rather than all of the user’s data. 14.4. Identity verification results and necessary identification details are retained for the period needed to confirm eligibility for the service and carry out applicable checks, and thereafter only where an independent lawful basis exists. Original documents and Liveness materials held by Neurovision are subject to a separate retention period and to deletion procedures in response to lawful requests and Flowbit’s documented instructions. 14.5. Support correspondence and attachments are retained until the request is resolved and for a justified period for follow-up enquiries or the defence of claims. Technical logs and diagnostic data are retained for the period necessary for the relevant check or investigation of a failure or incident. Unnecessary attachments and excessive information are deleted or anonymised. 14.6. A record of separate consent, its withdrawal or a legal request that has been handled may be retained to demonstrate compliance with obligations. After an opt-out from particular communications, a minimal record necessary to honour that opt-out may be retained. 14.7. Backups have a limited retention cycle. Data deleted from operational systems may remain in a protected backup until its next update; it is not used for routine operations. Previously implemented deletion and processing restriction requests are applied when data is restored. 14.8. If there is no lawful basis for continued retention, data is deleted or irreversibly anonymised. Technical difficulties do not create an independent basis for indefinite retention. The user may request the retention periods applicable to their data or the criteria used to determine them. 15. Data security and incidents 15.1. Flowbit applies technical and organisational measures proportionate to the risk, including access controls, confidentiality requirements, protection of data in transit and storage, logging of significant actions, security checks and incident response. The specific measures depend on the system and the nature of the data. 15.2. When an incident is identified, Flowbit determines its scope, limits its consequences, works with the responsible service provider and fulfils its obligations to notify users and competent authorities in the circumstances and within the time limits prescribed by law. 15.3. Absolute security of any system is not guaranteed. This qualification does not remove Flowbit’s obligations to protect data, remedy its own breaches and respond to incidents. The user must also protect their device, Telegram account and access credentials and report suspicious access. 16. User rights and how to submit a request 16.1. To the extent provided by applicable law, the user may obtain information about processing and access to their data, request rectification, deletion or restriction of processing, object to processing, receive their data in a portable form, withdraw consent and contact a competent supervisory authority or court. 16.2. A request may be sent to company@flowbitfinance.com or through official support. This channel remains available for handling legal requests even if ordinary account access is restricted. To protect data, Flowbit may request proportionate proof of identity and necessary clarification. 16.3. Requests are handled within the time limits set by applicable law. Flowbit communicates the outcome, any action required from the requester, or the lawful grounds for a restriction or extension, together with the available procedure for pursuing the matter further. Whether a request is free of charge and whether a fee is permitted are determined by mandatory rules; a financial service fee does not automatically apply to a personal data request. 16.4. The right to deletion or information may be subject to statutory restrictions, for example where retention is mandatory or necessary to defend a specific claim. A partner’s requirement, operational convenience or a general reference to risk does not, in itself, justify rejecting any request. 16.5. If a request concerns processing carried out on Flowbit’s behalf, Flowbit handles it and involves the relevant processor. If an independent controller is responsible for particular processing, Flowbit explains the available procedure for contacting that controller and fulfils its own obligations. 17. Marketing messages and optional processing 17.1. This version provides for service-related messages and necessary technical analytics. Marketing communications, advertising pixels and the sharing of contact details to build advertising or lookalike audiences are not included in the processing covered by this version. 17.2. If Flowbit decides to enable such features, the necessary information will be provided and the separate consent required by law and the Terms of Use will be obtained before they are enabled. Refusing or withdrawing such consent does not prevent access to the core service or receipt of necessary service-related notifications. 17.3. Providing contact details for KYC, starting the Telegram bot, granting technical permission to send direct messages or accepting the Terms does not, in itself, constitute separate marketing consent. 18. Service-related messages 18.1. Flowbit may send messages in its own name about the account, card issuance and status, transactions, security, checks, support requests, necessary changes to terms and the operation of activated services. 18.2. These messages are sent through the application, the linked official Telegram bot, a verified email address or another agreed channel. Message content and the data used are limited to the relevant purpose. Advertising is not included in service-related messages merely to circumvent consent requirements. 18.3. Certain necessary notifications cannot be opted out of while retaining the feature for which they are mandatory. The user keeps their contact details up to date. Delivery of a message does not mean it has been read and does not, in itself, confirm separate consent to processing. 19. User age 19.1. The service is intended for adult users who meet the age requirements of the selected product and applicable law. Flowbit does not offer the service to children. 19.2. If processing of data relating to a person who does not meet the age requirements is identified, Flowbit checks the circumstances, restricts the relevant processing and deletes data for which there is no lawful basis for continued retention. 20. Third-party services and liability 20.1. A third-party website or independent service may process data under its own policy. Flowbit provides the necessary information about processing it arranges itself. A link to another party’s policy does not replace that information. 20.2. Flowbit does not guarantee that independent participants will be free from all incidents. However, the liability exclusions in the Terms do not remove Flowbit’s mandatory obligations concerning lawful transfers, the selection and engagement of processors, data protection and the handling of requests. 21. Changes to this Policy 21.1. Updates specify the version, publication date and effective date. Flowbit notifies users of material changes through the service’s designated channels in the manner and within the time limits required by law and the Terms. 21.2. A new purpose, category of recipients or method of processing is assessed before it is introduced. If new consent is required, Flowbit obtains it separately. Continued use of the service or publication of the text alone does not replace that consent. 21.3. Mandatory rights relating to processing already carried out, and records necessary to demonstrate the terms and consents that applied, are preserved to the extent provided by law. 22. How to contact Flowbit 22.1. For personal data enquiries: company@flowbitfinance.com. A request need only describe the matter and provide the details necessary to contact the user and identify the account. Do not attach a complete document or confidential credentials unless there is a justified request through an appropriate secure channel. 22.2. The company’s postal address is: Flowbit Finance L.L.C-FZ, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, U.A.E. Registration number: 2541754. 23. Key definitions 23.1. Personal data means information relating to an identified or identifiable individual. Data may remain personal data after a name is replaced with an identifier if the link to the individual remains. 23.2. Controller means a person who determines the purposes and means of processing. Processor means a person who processes data on behalf of the controller. Equivalent terms under applicable law are used with their corresponding meanings. 23.3. Anonymisation means transforming data so that an individual can no longer be identified by reasonably available means. Merely replacing a name with a code does not always constitute irreversible anonymisation. 23.4. Liveness means a check that a live person is present in front of the camera. Images and other materials relating to a person’s face that are used to establish or verify identity may constitute biometric or other specially protected data under applicable law; the requirements applicable to them are assessed separately. 23.5. Applicable law means the legislation and other mandatory legal requirements applicable to the relevant processing. Partners’ commercial rules are not automatically treated as law.