1. Who we are
This Privacy Policy explains how Axa Trading Ltd. handles personal data. Axa Trading Ltd. is the data controller.
| Controller | Axa Trading Ltd. |
| Company number | 2026-00472 (Saint Lucia) |
| Registered office | Ground Floor, Rodney Court Building, Rodney Bay, Gros Islet, Saint Lucia |
| Privacy contact | privacy@axatrading.com |
| General contact | support@axatrading.com |
It applies to axatrading.com, app.axatrading.com, our mobile applications, and any other service we operate that links to it, and to the "axatrading" brand generally.
2. What we do, in one paragraph
We operate a leveraged derivative trading platform. To open an account for you we must verify who you are, because we are required to prevent money laundering, terrorist financing and sanctions evasion, and because we must be able to establish that we are not dealing with someone in a country where we do not offer services. That verification is the single largest reason we hold personal data about you, and it is the reason we cannot simply delete everything on request.
3. What personal data we collect
3.1 Data you give us
| Category | What it is | When |
|---|---|---|
| Registration data | E-mail address or telephone number — whichever you register with; the other if you add it later. There are no passwords | Sign-up |
| Identity data | Name, date of birth, place and country of birth, nationality, country of residence; a government-issued identity document (passport or national identity card) including the document image, document number, issuing country and expiry date | Verification |
| Biometric data | A facial image and the "liveness" capture used to confirm that you are a real, present person, and the facial-similarity comparison between that capture and your identity document | Verification |
| Address data | Residential address and a document evidencing it, no older than the AML and KYC Policy Summary, section 4, allows | Verification or review |
| Financial-crime data | Your answers to our due-diligence questions — the purpose of the account, employment status, source of funds, expected monthly activity, whether you are a politically exposed person — and, where we ask for it, your source of wealth and supporting evidence | Verification and periodic review |
| Investor profile | Your answers to the optional questionnaire about your trading goals, the markets you are interested in and your budget | Onboarding |
| Wallet data | The cryptocurrency addresses you save for withdrawals | Funding |
| Correspondence | Support tickets, messages in the platform, e-mails and any call recordings | Any time |
3.2 Data generated by your use of the platform
Trading activity (orders, positions, leverage, profit and loss, balances, transactions), account settings, responsible-trading controls, security events (sign-ins, devices, IP addresses, passkeys, two-factor events, saved withdrawal addresses), the audit log of changes made to your account, and product and security telemetry: which pages of the platform you open and which actions you take — an order placed, a deposit or withdrawal started, a verification step completed — recorded by our own systems so that we can operate, secure and improve the platform. This telemetry is first-party; no advertising or analytics company receives it. For each e-mail we send you we also record whether it was delivered, the first time it was opened and the first time a link in it was clicked — see section 8.
3.3 Data collected automatically
IP address, approximate location derived from it, device and browser characteristics, operating system, language, referring page, pages viewed and actions taken on the website, and the identifiers set by cookies and similar technologies. See the Cookie Policy.
3.4 Data from third parties
- Your identity provider, if you sign in with Google or Facebook. See section 4.
- The AI document-reading service that reads the data on your identity document for us, where we use one. See section 6.
- Sanctions and politically-exposed-person screening, run on our own systems against published lists, which returns matches against your name and details. Adverse-media checks are research done by our reviewers, not an automated feed.
- Blockchain analytics, performed by our payment provider on incoming deposits to assess their provenance.
- Our payment provider, which confirms deposits and withdrawals.
3.5 What we do not collect
We do not ask for, and do not want, information about your health, your religion, your political opinions, your sexual orientation or your trade union membership. Please do not send it to us. The only special-category data we handle is the biometric data described in 3.1, and we handle it solely to verify your identity.
4. Signing in with Google or Facebook
You sign in with a one-time code sent to your e-mail address or telephone number, with a passkey, or with a Google or Facebook account. Sign in with Facebook is offered on the web platform; the mobile app offers a one-time code, a passkey and Google. If you use Google or Facebook, that provider tells us a limited set of information and confirms that it has authenticated you.
| Provider | What we receive |
|---|---|
| Name, e-mail address, and the identifier of your Google account for our app | |
| Name, e-mail address, and your Facebook user ID for our app |
We request the minimum permissions necessary — openid, email and profile from Google, and public_profile and email from Facebook — and nothing more; we do not store a profile picture or an account language. We do not receive your password for either service. We cannot access your Gmail, Drive, Contacts or Calendar, and we cannot access your Facebook posts, friends, photos or messages, or post anything on your behalf.
Confirming the e-mail address. We accept from Google only an e-mail address that Google has verified; if it has not, you cannot sign in with Google. Facebook does not confirm to us that the e-mail address it reports belongs to you, so before we create or connect your axatrading account through Facebook, we send a one-time code to that address and act only once you enter that code; until then nothing is created or connected.
We use this data only to create and authenticate your axatrading account and to contact you about it. We do not use it for advertising, we do not sell it, we do not share it with anyone except the processors listed in section 8, and we do not use it to build a profile of you or to make any decision about your eligibility, your trading terms or your limits.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting. You can disconnect Google or Facebook from your axatrading account in your account settings — on the web platform and in the mobile app — once you confirm it with a code we send you, or ask our support team to do it. Disconnecting removes the link between the two accounts: you can still sign in with a one-time code, and we tell you by e-mail that the sign-in has been disconnected. Signing in with Google again connects it again where the e-mail address Google gives us is your account's e-mail address (if you have not yet verified that address with us, sign in with a one-time code first), and Facebook once you also enter the one-time code we send to that address; a sign-in with any other e-mail address is not connected to your account. You can also remove axatrading's access at the provider — for Google at myaccount.google.com/permissions, and for Facebook under Settings → Apps and Websites: that stops the provider sharing your data with us, but it does not stop that sign-in method, because the provider asks for your consent again the next time you choose it. Neither closes your axatrading account or deletes your data; to do either, see section 11 and Account Closure and Data Deletion, which is also the page Facebook users are directed to for data-deletion requests.
5. Why we use your data, and on what basis
| Purpose | Data used | Basis |
|---|---|---|
| Opening your account and providing the service | Registration, identity, trading, wallet | Performance of our contract with you |
| Verifying your identity and age, and screening you against sanctions and PEP lists | Identity, biometric, address, financial-crime | Legal and contractual obligation; our legitimate interest in preventing financial crime; your explicit consent for the biometric element |
| Confirming that you are not in a Restricted Territory | Country of residence and address, nationality, IP address, document country, telephone country code | Performance of contract; legitimate interest in lawful operation |
| Processing deposits and withdrawals, including the identity details our payment provider must receive | Wallet, transaction, identity | Performance of contract; legal obligation of the provider |
| Detecting and preventing fraud, abusive trading and unauthorised access | Security, device, trading, IP | Legitimate interest in protecting the platform and other clients |
| Operating, securing and improving the platform | Product and security telemetry (3.2) | Legitimate interest in running a reliable and secure service |
| Support and complaints | Correspondence, account | Performance of contract; legitimate interest |
| Service messages about your account, positions, verification, deposits, withdrawals and security | Registration, trading, account activity | Performance of contract |
| Choosing which service and marketing messages to send you, and when | Account activity, verification status, deposits, balances, trading activity, your answers to the investor-profile questionnaire — your goals, the markets you are interested in and your budget — language, country and time zone | Legitimate interest for service messages; consent for marketing messages: withdrawing it stops the selection of marketing messages, while service messages continue |
| Marketing messages about our products | Registration, and the selection above | Consent, withdrawable at any time |
| Knowing whether the e-mails we send you arrive and are read | Delivery, the first opening and the first click on a link, for each e-mail (section 8) | Legitimate interest in knowing whether our messages reach you and in measuring our campaigns; for marketing e-mails, within your consent to marketing |
| Measuring and improving the website, when we use analytics | Analytics data | Consent, given through the cookie banner; no analytics is in use at the date of this version (Cookie Policy) |
| Meeting record-keeping, tax and legal obligations, and responding to lawful requests | All of the above | Legal obligation |
6. Identity verification — what we do with your document and your face
We use your facial image for one purpose: to confirm that the person opening the account is the person shown on the identity document, and that they are physically present rather than a photograph, a mask or a synthetic image.
- The facial check runs on our own systems. The facial comparison and the liveness scoring are done by our own software, not by an outside service.
- The comparison produces a similarity score and a liveness result. We retain the captured images and the results as part of our verification record. We do not store a biometric template.
- Review by our staff with an AI assistant. Our staff may review your verification with the help of the AI assistant described in section 8, and may have the assistant prepare the decision on your verification or take it for them. The assistant may then process your identity document and proof of address, what was captured in your liveness check — the selfie, still images and a short video — and the face crops used in the facial comparison. It is a third-party service, provided by Anthropic in the United States: it processes this data under its own terms and may also use it to improve its services. We remain responsible for a decision the assistant takes for our staff, and you can ask for it to be reviewed by a person (section 7).
- We do not use your face to identify you anywhere else, we do not add it to any searchable database beyond your own client record, and we do not share it for any purpose other than those in section 8.
- Reading your document. The data on your identity document — name, date of birth, document number, expiry date, nationality, issuing country — is read either by our own software from the document's machine-readable zone or, where we use it, by an AI document-reading service provided by OpenAI or Anthropic. In that case the image of your document, including the photograph on it, is sent to the service, which reads the data and returns it to us. It is a third-party service: it processes the image under its own terms and may also use it to improve its services. The decision on your verification is made by us. Your selfie and the liveness capture are never sent to that service.
- You cannot deposit, trade or withdraw without completing this check. If you do not wish to provide biometric data, please do not complete verification.
7. Automated decision-making
Parts of our verification are automated: reading of the document's machine-readable zone and comparison of its data with what you entered, facial comparison, liveness scoring, sanctions-list matching, age and geographic screening, and monitoring of document expiry.
Some automated checks decide on their own. If your declared country of residence is one where we do not offer services, your nationality or document country is one whose nationals we decline, or you are under 18, the platform refuses the account itself; a nationality, document country or telephone country code for which we apply enhanced due diligence raises your risk rating; a sign-up from an IP address in a restricted territory, or with a telephone number whose country code is used only by countries whose nationals we decline, is refused, and a session opened from such an IP address is limited to viewing (Restricted Territories Policy, sections 1, 2 and 4); a match against a sanctions list holds your funds until our staff have decided; an expired document limits you to closing positions, and stops deposits and withdrawals, until you replace it. Our automated checks never reject a verification application: where an automated step fails or is unsure, the case goes to our staff. Our staff may have the AI assistant described in section 8 prepare such a decision or take it for them (section 6).
Where an automated check refuses or restricts you, or where the AI assistant has taken a decision about you for our staff, you can ask for it to be reviewed by a person. Write to privacy@axatrading.com or support@axatrading.com. We use your account activity to choose which messages to send you (section 5); we do not use automated profiling to set your trading terms, your leverage or your pricing.
8. Who we share your data with
We do not sell your personal data. We never have and we will not.
We share it with two kinds of recipient. Service providers process it for us under a written contract that requires them to protect it to at least the standard set out in this policy and to use it only on our instructions. Other recipients handle what they receive under their own terms and their own legal duties, not on our instructions: our payment provider, which is itself regulated and must keep the identity details it receives; Google and Meta, when you sign in with them or use Google Maps; Telegram; the AI services; our professional advisers; and the banks and counterparties that check us. The table says which is which.
| Recipient | Role | What they receive |
|---|---|---|
| Confirmo Limited (Ireland) — crypto payment gateway, authorised and supervised as a crypto-asset service provider by the Central Bank of Ireland, reference C570624 | Own terms and duties. Receiving deposits, converting them into US dollars, holding the US-dollar balance for us and paying out withdrawals; blockchain analytics on incoming deposits. As a regulated provider it keeps the identity details it receives under its own legal duties | Transaction and wallet data and, with every deposit and withdrawal, the identity details the provider must hold under the "travel rule": name, date and place of birth, address and e-mail address |
| Atol solutions s.r.o. (Czech Republic, company number 29610923, registered office Osvobození 1329, Lutyně, 735 14 Orlová) — infrastructure and hosting | Service provider under contract. Running the website, the platform and its databases on its own infrastructure in Prague, Czech Republic — inside the European Economic Area. It is a technology company affiliated with our Managing Director, and it acts only on our documented instructions under a written data processing agreement | All data held on the platform |
| Twilio (Verify, with e-mail delivered by Twilio SendGrid) | Service provider under contract. Sending the one-time codes you sign in with, by SMS and by e-mail, and the codes that confirm a withdrawal, a new withdrawal address, a new passkey, the disconnection of Google or Facebook, or an e-mail address reported by Facebook (section 4) | Telephone number or e-mail address |
| Resend (United States) | Service provider under contract. Sending our service and marketing e-mails, receiving delivery reports, and measuring whether an e-mail is opened and whether a link in it is clicked — see "E-mail measurement" below | E-mail address, name and the content of each e-mail we send you; when you open an e-mail or click a link in it, your IP address and browser details reach Resend, which reports the opening or the click to us without them |
| Google — Identity Services and Maps Platform | Own terms. Sign in with Google, which contacts Google when the sign-in or sign-up page opens; address suggestions and a map preview on the address form, which your browser requests from Google directly. Google Analytics and Tag Manager are not in use at the date of this version; if we switch them on, they load only with your consent (Cookie Policy) | Sign-in identifiers; the address you type and your IP address |
| Meta (Facebook Login) | Own terms. Sign in with Facebook on the web platform; the Facebook software loads only when you choose that button | Sign-in identifiers and, at that moment, your IP address |
| Cloudflare | Service provider under contract. DNS, security and content delivery at the network edge. All traffic between you and the platform passes through Cloudflare's network, where it is decrypted and re-encrypted in transit at the location nearest to you, so your requests are processed outside the European Economic Area, while the platform itself and its databases stay in Prague | IP address, request metadata, and the content of requests and responses in transit |
| Telegram | Own terms. Our internal operations channel. Our team receives notifications about events on the platform — a sign-up, a deposit, a withdrawal, a compliance alert, a new support ticket — through a Telegram group | Your account identifier, amounts and event type: limited metadata — never your name, contact details, documents, messages or wallet addresses |
| Dampia — provider of our e-mail server | Service provider under contract. Hosting the mailboxes (hello@, support@, complaints@, privacy@, compliance@) that our support team reads and writes from | The e-mails you send us and our replies |
| DigitalOcean (Frankfurt, Germany) | Service provider under contract. Backup storage | Encrypted backups of platform data |
| Google (Apps Script and Sheets) | Own terms. The waiting-list form on our website sends the contact details you submit to a script of ours hosted by Google, which stores them in a Google spreadsheet of ours | The e-mail address or telephone number you enter |
| Professional advisers — lawyers, auditors, our registered agent | Own professional duties. Advice and corporate administration | As required |
| Banks, payment providers and counterparties performing their own due diligence on us | Own legal duties. Their compliance obligations | Aggregate and, where required, specific data |
The images, logo and country flags shown in the platform are served from our own domain; no image host receives your data.
E-mail measurement. Our service and marketing e-mails go out through Resend; one-time codes go out through Twilio and are not measured. Resend inserts a transparent one-pixel image into each e-mail and routes each link in it through an address of its own, so that it can tell us that the e-mail was opened and that a link was clicked. We record only the first opening and the first click of each e-mail, with the time: we do not store the IP address, the browser or the link that Resend reports. We use this to know whether our messages reach you and to measure our campaigns. Our security warnings — a new withdrawal address, a new passkey, two-factor authentication switched off, Google or Facebook disconnected — contain no links, so nothing in them is redirected. If you do not want to be measured, set your e-mail program not to load images and do not click links in our e-mails; unsubscribing from marketing stops marketing e-mails altogether, while service e-mails about your account continue and are measured in the same way.
The AI document-reading service. Where we use an AI document-reading service (section 6), OpenAI or Anthropic (United States) receives the image of your identity document and returns the data read from it. It is a third-party service: it processes that image under its own terms — which also set how long it keeps it — and may also use it to improve its services.
Support messages, and the AI assistant our staff use. The support conversation in the platform is our own system: your support messages and tickets are stored on our platform, and our internal notifications carry only a ticket's identifier and type. Our staff use an AI assistant provided by Anthropic, PBC (United States) in our back office, to help them handle support requests and carry out operational and compliance tasks, including the review of your verification. For each task it receives the support messages and the account data that the task needs; for a verification review, that includes your documents and what was captured in your liveness check and facial comparison (section 6). The assistant is a third-party service: Anthropic processes the data it receives under its own terms — which also set how long it keeps that data — and may also use it to improve its services.
We also disclose personal data where we are required or permitted by law — to a court, a regulator, a financial intelligence unit, a tax authority or a law-enforcement agency — and where necessary to establish, exercise or defend legal claims. Where we file a suspicious-activity report we are generally prohibited by law from telling you.
If the business is sold or reorganised, personal data may transfer to the acquirer, subject to this policy.
9. Where your data goes, and the law that applies
We are established in Saint Lucia, but that is not where your data lives.
The platform, its databases and your verification records are held in Prague, Czech Republic — inside the European Economic Area, and our backups are stored in Frankfurt, Germany. Several of our service providers are also in the EEA; others — our e-mail delivery service, the one-time-code service, the sign-in providers, Google Maps and the Google spreadsheet of our waiting list, the AI document-reading service where we use it, the AI assistant our staff use, and our internal notification channel — are in the United States or elsewhere outside the EEA. All traffic between you and the platform passes through Cloudflare's network, where it is decrypted and re-encrypted in transit at the location nearest to you, so your requests — your IP address, what you asked for and the content of the request and our answer — are processed at edge locations around the world. Cloudflare does not store the content of your account, and the platform and its databases stay in Prague. Your personal data is therefore transferred outside Saint Lucia, and in the ordinary course it is never stored there.
What Saint Lucian law currently requires. The Data Protection Act, Cap. 8.18 is in force in part. The data protection principles and the substantive processing duties — lawful basis, collection limitation, accuracy, use limitation, security and the duty to destroy — took effect on 31 January 2023, and we comply with them. The parts of the Act that would establish a Data Protection Commissioner, a register of data controllers and statutory restrictions on transferring data abroad have not been brought into operation. So, plainly:
- There is no register of data controllers in Saint Lucia at present, and we are not registered in one. We will register if and when that part of the Act is commenced. Anyone who tells you a Saint Lucian company is "registered with the Data Protection Commissioner" is describing something that does not currently exist.
- Saint Lucian law does not presently restrict transfers of personal data out of the jurisdiction, so we make no claim to hold a transfer authorisation.
What we do instead, because it is what actually protects you. Every international transfer to a service provider listed in section 8 is made under a written contract with the provider imposing protections comparable to those in this policy, limiting it to our documented instructions, and requiring the security measures in section 12. That is a commitment we make to you directly, and it does not depend on which parts of which statute are in force. The other recipients in section 8 — our payment provider, Google, Meta, Telegram, the AI document-reading service and the AI assistant our staff use — are not covered by it: what they receive is processed under their own terms and legal duties, in the United States or wherever else they are established (section 8).
If you are in the EEA or the United Kingdom: there is no adequacy decision for Saint Lucia, no supervisory authority operating there, and no statutory data-subject rights in force there. We say so plainly rather than imply an equivalence that does not exist. The rights in section 11 are contractual commitments we give you, and we honour them on that basis.
10. How long we keep it
| Data | Retention |
|---|---|
| Identity, verification and biometric records, and due-diligence material | 7 years after the end of the relationship — the standard financial-crime record-keeping period, and the period our own AML programme applies |
| The same records of someone who applied for an account but never became a client | We close an application that has had no deposit or withdrawal, no approved verification and no sign-in for 12 months; the 7-year period then runs from that closure, or, for an application we rejected, from the rejection |
| Transaction and trading records | 7 years after the end of the relationship. The record of an order we rejected and the price evidence of a position you closed are deleted 7 years after they were made, whether or not the relationship has ended |
| Correspondence and complaint files of clients | 7 years after the end of the relationship |
| Complaint files of people who do not hold an account with us | 7 years from the last activity on the file; the whole file, including the e-mails, is then deleted |
| Requests about personal data (section 11), of clients and of people who do not hold an account with us | 7 years from when we dealt with the request; its contact details and text are then deleted. For a client whose account we delete sooner, they are deleted with the account, or, for a request not yet dealt with by then, once we have dealt with it |
| Other correspondence from people who do not hold an account with us, and the tickets opened from it | 24 months from receipt. Messages on the mail server are removed 90 days after they arrived there — the originals of messages we have processed, the copies of our replies (counted from sending) and messages our system could not process, of which we keep no copy; the copy in our support system is what we keep |
| Waiting-list sign-ups on our website | Until we contact you at launch, and no longer than 12 months from sign-up; we delete them from the spreadsheet by hand |
| Security and audit logs — the tamper-evident audit trail of the verification system, and the logs of our back office: every access to client data and the AI assistant's proposals and calls | 7 years: the audit trail in line with the client record it belongs to, and the logs of our back office from the day of each entry |
| The log of every direct access to the databases through our database administration tool | 7 years from the end of the month of each entry |
| A one-way fingerprint of the e-mail address, telephone number and identity document of someone who excluded themselves (Responsible Trading Policy, section 2) | Until the self-exclusion ends with a confirmed reactivation; after the rest of the data is deleted, until the end of the self-exclusion's term, so that it keeps blocking a new registration — an indefinite self-exclusion keeps it |
| Operational logs of our systems, which may include the e-mail address or telephone number you registered with | 30 days |
| Product and security telemetry — which pages of the platform you open and which actions you take there | 14 months from the event. Our analytics store keeps it for 400 days, and the internal queues that carry events between our systems, including the queue of events we could not process, keep their copy for at most 30 days |
| E-mail measurement — delivery, the first opening and the first click of each e-mail we send you | With the record of the e-mail itself; when your data is deleted, that record is pseudonymised so that it no longer identifies you |
| Website analytics data | Not in use at the date of this version; when we use it, 14 months, and withdrawing consent stops any further collection |
| Marketing data | Until you unsubscribe, then a record that you have done so, so that we do not contact you again |
When a retention period ends we delete the data or irreversibly anonymise it. If we have assigned an e-mail of yours to another client's support ticket, a copy of its text stays in that ticket's conversation, and the deletion of your account does not reach it; your address and name as its sender, and the e-mail's attachments, are deleted. The audit trail of changes to your account is kept, because it must stay tamper-evident, but the personal values in it — your name, contact details, address and the text of requests we sent you — are replaced by an "erased" marker, so that the record of what changed and when remains without identifying you. Transaction records remain under an identifier that no longer leads to you.
Telemetry is not the record of what you did with your account. Your orders, payments, verification steps and your sign-in history — the method, the IP address and the device of each sign-in — belong to your client record and are kept for the periods above, that is 7 years after the end of the relationship.
11. Your rights, and how to close your account
You can ask us to:
- give you a copy of the personal data we hold about you;
- correct anything that is wrong or out of date;
- delete your data — see the limits below;
- restrict or object to a particular use;
- withdraw consent at any time, for marketing, for analytics cookies, or for the biometric processing (withdrawing consent for biometric processing means we can no longer operate your account, and we treat it as a request to close it);
- have an automated decision reviewed by a person (section 7);
- receive your data in a portable format.
How: write to privacy@axatrading.com from your registered e-mail address. We will respond within 30 days: we log every request with that due date, whether or not you hold an account with us — if you do not, say so and give us the e-mail address to reply to. We may need to verify your identity first, precisely because we must not hand your data to someone impersonating you. Marketing consent you can also withdraw yourself in your account settings; cookie consent through the cookie preferences (section 14).
Closing your account and deleting your data. You can close your account at any time. The full procedure — in the platform, in the mobile app, and from a public page you can use without logging in — is at Account Closure and Data Deletion.
Deleting an account that was never used. If you never submitted verification and no money was ever deposited or withdrawn, nothing obliges us to keep your account: on request we close it and delete its data at once.
The limit on deletion, stated honestly. While you hold an account, and for the retention period after it closes, we keep your records as described in section 10; when you ask us to delete your data and our obligations do not let us delete it yet, we tell you so, withdraw your marketing consent and stop marketing to you — including cards in the platform — and using your data to choose which messages we send you, until you give your marketing consent again, and after your account is closed we use your data for nothing other than those obligations and delete it at the end of that period. That period starts only when your account is closed, so if you ask while it is open, we offer to close it for you; until then we keep using your data to provide the service you still use. We must retain your identity and verification records, your transaction history and the related due-diligence material for 7 years after the relationship ends, in order to comply with financial-crime record-keeping obligations and to be able to respond to a lawful request. Access to those retained records is restricted to authorised staff. Every access through our back office is logged. Direct database access through our database administration tool is limited to named administrators, only from our internal network and with a personal sign-in, and every such access is logged. The retained records are not used for marketing, and they are deleted or anonymised at the end of the period. Data that the other recipients in section 8, which handle it under their own terms or legal obligations, have already received — among them our payment provider, which keeps its own record of each deposit and withdrawal, and the AI document-reading service and the AI assistant our staff use — is held by them under those terms or obligations; deleting your data with us does not delete it there. Suspending or deactivating your account is not the same as deletion, and we will not describe it as such.
12. How we protect your data
- TLS 1.2 or higher between your device and our platform.
- Identity documents, biometric captures and support attachments are encrypted at the application level (AES-256-GCM), with keys held separately from the data; database backups are encrypted with modern authenticated encryption.
- Sign-in by one-time code, passkey or verified identity provider; optional two-factor authentication with backup codes; one-time codes are single-use and time-limited, the number of codes we send and of wrong attempts is limited, and repeated wrong codes lock further attempts for a time. A withdrawal is confirmed with a code sent to your verified e-mail address, which a withdrawal needs; a new withdrawal address and a new passkey are confirmed with a code sent to your verified e-mail address — or your verified telephone number if you have no e-mail address on the account. Withdrawals go only to addresses you have saved, after a hold on new addresses; only one withdrawal to a new address — the first, or the next one if the first is cancelled or does not go through — up to the amount the Deposit, Withdrawal and Refund Policy, section 5, states, may go before its hold ends. We e-mail you when a passkey is added to your account, when two-factor authentication is switched off, by you or by our support team, when a withdrawal address is added and when Google or Facebook is disconnected from your account — also while a detail on your account stops our other e-mail notices (Restricted Territories Policy, section 4).
- Role-based access control in our back office, with a complete audit log of every change to a client record, a log of every access through the back office to sensitive data, and an append-only hash-chained audit trail in the verification system. Direct access to the databases through our database administration tool is limited to named administrators, only from our internal network and with a personal sign-in, and every such access is logged.
- Segregation of production and non-production environments. Our test environments send service and marketing e-mails only to our own domains and test mailboxes; a sign-in code goes to whatever address someone enters in a test environment themselves.
- Regular review of access rights.
No system is completely secure. If a breach occurs that is likely to affect you, we will tell you and tell the relevant authority, promptly and without excuses.
13. Children
Our services are for adults. We do not offer accounts to anyone under 18 and we verify age as part of identity verification. We do not knowingly collect data from children. If you believe a minor has given us data, tell us at privacy@axatrading.com: we will close the account and delete its data — at once where no verification was ever submitted and no money moved, and otherwise as soon as the record-keeping in section 10 allows.
14. Cookies
Set out separately in the Cookie Policy. At the date of this version neither the website nor the application uses any optional technology, so there is no cookie consent to give or withdraw. Whenever we do use one, you can change or withdraw your consent at any time through the "Cookie preferences" link in the footer of every page of the website and in the application under My account → Legal documents, and we honour Global Privacy Control signals from your browser, unless you have yourself switched a category on in our cookie preferences.
15. Changes to this policy
We may update this policy. The version in force is the one published here, with its version number and date; earlier versions stay available at their own addresses, listed on this page. If we make a change that materially affects how we use your data, we will tell you by e-mail — if your account is open, has an e-mail address and nothing on it stops our e-mail notices (Restricted Territories Policy, section 4) — and, where the law requires it, ask for your consent before the change takes effect; where a new version needs your acceptance, the application asks you for it when you next sign in after it has taken effect, as clause 20 of the Client Agreement describes. We do not e-mail a closed account about changes. We will not apply a new purpose to data already collected without a basis to do so.
16. Complaints
If you are unhappy with how we have handled your data, write to privacy@axatrading.com. We will investigate and respond within 30 days.
If you remain unsatisfied, we would rather tell you the truth than point you at a door that does not open: no data protection supervisory authority is currently operating in Saint Lucia, because the part of the Act that would establish one has not been brought into force. There is therefore no Saint Lucian regulator to escalate to. What you do have is our Complaints Handling Policy and, beyond it, clause 24 of the Client Agreement — mediation at our cost, then English law and binding arbitration. You may also have rights under the law of your own country of residence.
Version 1.0. Last updated: 1 October 2026. Axa Trading Ltd., company number 2026-00472, Ground Floor, Rodney Court Building, Rodney Bay, Gros Islet, Saint Lucia.