Privacy Policy

Privacy Policy

This page explains the information that Northmark (run by an individual; "we" below) handles on this site (fxbroker-compass.com) and when you verify an account on the KAI Discord server. KAI is our project to have an AI (a large language model) make FX decisions and to test its learning and reasoning.

Operator and contact

• Operator: Northmark (run by an individual)
• Contact: contact@fxbroker-compass.com (for requests about personal information, start the subject line with [PRIVACY])

1. Information handled when you view the site

When you open the site, your browser sends the following to us and to the outside services we use:

• Your IP address (used to determine your country and kept in the hosting provider's logs)
• Device information such as browser, operating system, language, and screen size
• The pages you view, the referring page, and the date and time
• Cookies and values stored in your browser's storage (see the Cookie Policy)

The list of recipients, what they receive, and why is on the External transmission notice page.

Google Analytics 4 (GA4)

• Used to count which pages are read and how the site is used (for example, clicking a partner link or a Discord invite link).
• We do not use Google signals (turned off). Ad personalization is also off.
• Data is kept for 14 months (the setting that extends this on each new visit is off). Visitors are counted per device (browser).
• We send only the fields we have listed for each event. We do not send account numbers, Discord user IDs, or email addresses, or any converted (hashed) form of them.
• For visits from the EEA, the UK, and Switzerland, analytics cookies are not set until you agree. In other regions, analytics is on from the start, and you can turn it off at any time under "Cookie settings" at the bottom of the page.

Partner link tracking and conversion import

• When you click a partner broker's link, a tracking field (sub ID) in the link carries the page language, the link's position, and the identifier GA4 placed in your browser (client ID, only when analytics cookies are present). This goes to the partner.
• When a partner notifies us of a result (an account registration, a deposit, a commission amount, and so on), we may send that identifier, the partner's name, the commission amount, the language, and the link position to GA4, so we can see which page an account was opened from. We do not send names, email addresses, or account numbers.

Microsoft Clarity

• Only if you choose "Allow" for analytics in the cookie settings yourself, we record on-page activity (clicks, scrolling, screen movement) with Microsoft Clarity. It does not run until you make that choice.

Vercel Analytics and Speed Insights

• Features of Vercel, which serves this site, that count page views and measure page speed. They do not use cookies.

2. Information handled in Discord account verification

To see all record notifications and the language channels on the KAI Discord server, you need to verify an account. For verification we receive:

What we receive

• The trading account number you enter and its broker
• Your Discord user ID and username
• The verification status (pending, approved, rejected), the language you chose, and the dates of the request and the decision
• A record used to stop abuse (how many accounts the same person tried within a short time; account numbers are kept in converted form)

We do not ask for, and do not receive, email addresses, passwords, names, or identity documents.

Why

• To check, against the information our partner brokers send us, that the account was opened through our partner link and that it has a first deposit
• To give and remove Discord roles
• To stop one account being used by several people, and other abusive requests
• To count how many verifications took place (this record holds only the broker, language, date and time, and a random number, and cannot be traced to a person)

Where it is kept

• Requests are kept in a database on a computer the operator manages.
• To decide on approval, the request (including the account number) is sent to the operator's work chat (Slack).
• For the operator's dashboard, a list with account numbers cut down to the last 4 digits (including the Discord user ID, username, and status) is kept in a private code-hosting service (GitHub).

How long

• The record of tried accounts (abuse prevention) is deleted after 30 days.
• We have not set a retention period for the other request records. Leaving the Discord server does not delete them automatically. To have them deleted, write to the contact address above with your Discord username and account number. We will delete the records and remove the verified role.

Discord /ask

• The text of a question you send with /ask on Discord is sent to an outside AI provider's API to write the answer. Please do not include account numbers or other personal information.

Information that Discord itself handles is covered by Discord's own privacy policy.

3. Information we receive from partner brokers

We take part in the referral programs of our partner brokers (XM, Exness, HFM). For accounts opened through our partner links, the partners send us:

• The account number, the partner's customer number, the account type, trading platform and currency, and the country
• The registration date and whether identity verification is complete (we do not receive the documents themselves)
• Whether and when a deposit was made (for HFM, this includes deposit, withdrawal, and balance amounts)
• Whether the account traded, the number of trades, the trading volume, and the last trade date
• The commission amount paid to us

How we receive it: XM — a CSV exported from the partner dashboard; Exness — the partner API; HFM — a CSV exported from the partner dashboard.

The fields we import do not include names, email addresses, phone numbers, postal addresses, passwords, or identity documents (we have checked that our import process does not read these fields).

Why: to confirm Discord verification (section 2), to total referral commissions and results, and to see which pages accounts were opened from.

Where and how long: on a computer the operator manages and in a private code-hosting service (GitHub). We have not set a retention period. To have it deleted, write to the contact address above.

4. Information received through inquiries

When you email us, we use your email address and message to reply and to keep a record.

5. Sharing with third parties and the outside services we use

• We do not sell personal information.
• We do not give it to third parties without your consent, except where the law requires.
• We use the following outside services to run the site (we entrust information to them): Vercel (hosting), Google (GA4), Microsoft (Clarity), Discord (server and bot), GitHub (private storage of code and data), Slack (the operator's work chat), and an AI API provider (answers to /ask).
• Many of these providers are outside Japan (for example, in the United States), and information may be stored on servers in those countries. Each provider handles it under its own privacy policy.
• Once you follow a partner link to a broker's site, that broker's privacy policy applies.

6. Legal bases (GDPR and UK GDPR)

• Consent: analytics cookies in the EEA, the UK, and Switzerland; Microsoft Clarity
• Steps related to a request you make: handling your Discord verification request
• Legitimate interests: running and improving the site, preventing abusive requests, confirming partner results
• Legal obligation: where the law requires it

7. Retention periods

8. What you can do

• Ask for access, correction, deletion, or a stop to use: write to the contact address above (start the subject with [PRIVACY]). So that we can confirm it is you, include your Discord username and account number for anything about Discord verification. We respond within the period the law sets.
• Turn off analytics: reject it under "Cookie settings" at the bottom of the page. You can also use Google's opt-out browser add-on.
• You can use the rights given by the law where you live (Japan's Act on the Protection of Personal Information, the GDPR and UK GDPR, the CCPA/CPRA, the LGPD, and others), and you can complain to a supervisory authority.
  • Japan: Personal Information Protection Commission https://www.ppc.go.jp/en/
  • EU: https://edpb.europa.eu/
  • UK: ICO https://ico.org.uk/
  • Brazil: ANPD https://www.gov.br/anpd/

9. People under 18

This site and Discord verification are not intended for people under 18.

10. Security

Connections are encrypted with HTTPS. Request records and partner information are kept where only the operator can access them and are not shown on any public page (the operator's dashboard that opens over the internet also shows only the last 4 digits of Discord verification account numbers).

11. Changes to this page

We update this page when the facts change. The date of the last update is shown at the top of the page.