Privacy Policy
Last updated: 2 November 2026
This Privacy Policy explains how Kaizen Investments ("Kaizen", "we", "us" or "our") collects, uses, shares and protects personal data when you use the SwarMind website and services (the "Platform"). It should be read with our Terms of Service.
SwarMind is a private, invitation-only beta. This policy describes the Platform as it currently operates. Some features described in the Terms or on the Platform are still being built; where that affects how data is handled, we say so.
1. Who is responsible
The controller of your personal data is Kaizen Investments, George Town, Grand Cayman, Cayman Islands. You can contact us about privacy at thetradingjourney1@gmail.com.
Where applicable data-protection law (for example the EU or UK General Data Protection Regulation, "GDPR") applies to our processing, we process your personal data in accordance with it.
2. Personal data we collect
Account and identity data. Your email address, the user and session identifiers issued by our authentication provider (Supabase) and checked by our application's identity and session service, and your password if you sign in with one (handled by the authentication provider). If you sign in with Google, we receive basic profile information from Google, such as your name, email address and profile picture. We keep a profile with your email address, display name and avatar.
Authentication and session data. Cookies and similar tokens that keep you signed in (see section 8).
Technical and log data. When you use the Platform, our servers and hosting providers process technical information such as your IP address, browser user-agent, the pages and API paths requested, timestamps, request identifiers and error details. Our own application logs record request paths, request identifiers and errors; our hosting providers may also record IP addresses in their logs. We also collect page-performance measurements (for example load and responsiveness timings, the page path, a coarse device type, your browser user-agent and a random identifier for the browser tab session).
Member-created content. Content you create or configure in the Platform, such as watchlists and watchlist sets, flags, notes, saved screens, alert rules and alert history, custom portfolios, signal rules, webhook destinations and their delivery logs, trade ideas, reviews and other content you share with the pod, studies and private reports, and messages you send to research or assistant features. Some preferences and drafts are stored only in your browser's local storage.
Usage, quota and spend records. Records of feature usage events, usage summaries, and, for AI features, usage, quota and cost records linked to your account.
Research-tool records. When you use the Platform's research tools, in particular through an access key (for example from an MCP or command-line client), our data warehouse may keep records linked to your account or access key, such as: access-key records (key identifiers and the label and role attached to the key, which may include your name or email address); logs of research queries, tool calls and data access (including the query text and parameters, the tickers and dates requested, the client name and a hash of the requesting IP address); usage, cost and AI-usage records (such as the AI model used, token counts and estimated cost); research artifacts, studies, backtest and scanner runs and custom configurations; content you save through the research tools, such as watchlists, notes, strategies, position watches (including the entry, stop and target prices you enter), feedback, alert rules and alert events, and delivery preferences (including webhook addresses).
AI prompts and outputs. When you use AI features, your prompts, the context the Platform attaches to them and the resulting outputs are processed by AI model providers (see section 5) and may be recorded with your account.
Discord desk-channel messages. The pod's desk discussion takes place in Discord channels configured by Kaizen. Discord hosts those channels and processes your messages there under its own terms and privacy policy. Our Discord bot handles messages from those channels as follows:
- What it collects: messages posted in the channels configured for the bot, and recent messages in the channels a member asks the bot to read when asking it a question. For each message it collects the content and metadata: your Discord user ID, username and display name, the channel's name and ID, the message ID and link, when the message was posted and edited, attachment details (file name, link, type and size) and details such as embeds, reactions and replies.
- Why: to produce the desk's daily, morning-prep, weekly and development reports, to answer questions members ask the bot, and to build the desk trade-review archive on the Platform, which indexes messages that mention ticker symbols by trading session and ticker.
- Where it is stored: desk-channel messages (content, your Discord user ID and display name, channel, message link, posting and editing times and attachment details) are archived in our application database. The reports, which may quote messages and name participants, are posted in Discord; the daily, weekly and development reports are also saved in our data warehouse, and the daily and morning-prep reports are published on the Platform.
- Who sees it: signed-in members can view the archived messages on the Platform, with the author's display name and a link to the message, and the reports published there; reports posted in Discord are visible to the members of the channels they are posted in. Members permitted to use the bot can also export a channel's message history, including this metadata, as a file posted in Discord.
- AI processing: to produce reports and answers, the bot sends message content, display names, timestamps, channel names, message links and attachment file names (and, for questions to the bot, recent channel messages, text attachments from the reports channel and any images attached to the question) to the AI model providers listed in section 5: Anthropic, or OpenRouter, which routes requests to model developers such as Moonshot AI.
- Retention: archived messages and the reports derived from them are kept while the pod operates and are deleted on request (section 10). The archive keeps the first captured version of each message; later edits or deletions in Discord are not applied to it automatically.
Legal acceptance records. When you accept these documents, we record your user identifier, the version of the documents you accepted and the time of acceptance, taken from our database's clock; these three items are the record of your acceptance. We also store, as supporting context only, your browser user-agent and a one-way hash of a shortened form of the IP address from which our servers received the request, which may belong to an intermediary such as our website host rather than to you. This context is reported with the request and is not tamper-proof evidence. We do not store your full IP address in this record. Acceptance records are deleted together with your account (section 9).
Communications. If you email us, we keep the correspondence. Our contact address is a Gmail account, so Google processes your emails and our replies as our email provider (section 5).
We do not ask for special categories of personal data (such as health data) and ask that you do not enter such data into the Platform.
3. How we use personal data and our legal bases
Where applicable data-protection law requires a legal basis, we rely on the following:
| Purpose | Legal basis (where applicable law requires one) |
|---|---|
| Creating and administering your account, authenticating you and providing the Platform and the features you use, including storing your content and delivering alerts you configure | Performance of our contract with you |
| Running AI features you request, including sending prompts to AI providers | Performance of our contract with you |
| Producing desk reports and answers from the pod's Discord desk channels and keeping the desk trade-review archive | Our legitimate interests in operating the pod's shared desk research |
| Enforcing usage limits, quotas and spend controls; preventing abuse; securing the Platform; investigating incidents | Our legitimate interests in operating a secure and sustainable service |
| Monitoring performance and reliability and improving the Platform | Our legitimate interests in a reliable, usable service |
| Recording your acceptance of our legal documents and keeping records needed to establish, exercise or defend legal claims | Our legitimate interests and, where applicable, compliance with legal obligations |
| Communicating with you about your account, changes to our terms and the service | Performance of our contract and our legitimate interests |
| Complying with law and responding to lawful requests | Compliance with legal obligations |
| A sale, merger, restructuring or other business transfer (section 7) | Our legitimate interests |
Where we rely on legitimate interests, you may object (section 10). We do not sell your personal data, and we do not use it for third-party advertising. We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects.
5. Service providers and where data is processed
We use the following service providers. The list reflects the Platform's current code and infrastructure documentation; where a provider's processing location is not confirmed here, we say so.
| Provider | What it does for us | Location |
|---|---|---|
| Amazon Web Services (AWS) | Hosting of the SwarMind application service behind app.swarmind.io, which handles identity and session authority, studies, research chat, AI admission and spend controls, and member MCP access | Frankfurt, Germany (EU) |
| Resend | Sending of transactional email, such as account confirmation, sign-in and password-recovery messages (through our authentication provider's email integration) | Region not specified |
| Supabase | Authentication (accounts, sign-in, sessions) and application database for member records such as profiles, watchlists, notes, alerts, settings and legal acceptance records | United States (us-east-1) |
| Vercel | Hosting and delivery of the SwarMind website, including its server functions; Vercel Speed Insights page-performance measurement | Server functions: Frankfurt, Germany (EU); session middleware and content delivery: global edge network; Speed Insights: location not specified |
| Railway | Hosting of the website's application backend, scheduled jobs, the pod's Discord bot and related services | EU (Netherlands) and US regions |
| Hetzner | Data warehouse for market and analytical data. It also holds research-tool records linked to your account or access key (such as access-key records; query, tool and data-access logs; usage and cost records; research artifacts and configurations; and content saved through the research tools, including alert rules and alert events) and the Discord desk reports, both described in section 2 | Falkenstein, Germany (EU) |
| Sign-in with Google (OAuth), only if you choose it; email service for our contact address (thetradingjourney1@gmail.com, a Gmail account), so Google processes the emails you send us and our replies | Region not specified | |
| Discord, Slack or another endpoint you configure | Delivery of alerts and notifications to webhook destinations you set up | Determined by the destination you choose |
| AI model providers: DeepSeek, OpenRouter (which routes requests to model developers such as Moonshot AI), xAI and Anthropic | Processing of prompts and generation of AI outputs when AI features are used | Varies by provider; may be outside your country |
As a result, personal data is processed in the European Union (Germany and the Netherlands) and in the United States. Providers whose location is shown above as not specified or varying, in particular the AI model providers, may also process it in other countries, including countries outside the European Union and the United States.
AI features are being introduced gradually and may be disabled at times. When an AI feature is used, the prompt and context are sent to the provider configured for that feature. AI providers process this data under their own terms, which may include retention for abuse monitoring.
Market-data providers. The Platform obtains market data, fundamentals, filings and macro data from third-party sources (for example Massive, formerly Polygon.io, Financial Modeling Prep, SEC EDGAR, FRED and the CFTC). Requests our servers send to these sources concern market identifiers such as ticker symbols and dates; we do not intend to send your personal data to them. The exception is the images described in the next paragraph, which your browser loads directly.
Images loaded from third-party hosts. Some images on the Platform are loaded by your browser directly from the host that stores them, which therefore receives your IP address, browser user-agent and other standard request information: company logos from Financial Modeling Prep, when our primary logo source has no image; profile pictures, from wherever they are stored (for example Google, for profiles created with Sign-in with Google); and other images whose links appear in Platform data or member content (for example chart images in shared trade ideas). These hosts handle that information under their own terms.
6. International transfers
Personal data may be transferred to and processed in the United States and the European Union, and some service providers (for example AI model providers) may process it in other countries. These countries may not offer the same level of data protection as your own. Where applicable data-protection law requires it, appropriate safeguards are used for such transfers. You can contact us for more information.
7. Business transfers
If Kaizen or the Platform, or any part of either, is sold, transferred, merged, restructured, financed or otherwise reorganised, or is the subject of due diligence for such a transaction, personal data may be disclosed to and transferred to the prospective or actual buyer, successor or other party, subject to appropriate confidentiality. Any successor will be required to handle your personal data in line with this Privacy Policy, unless and until it is changed in accordance with section 13.
9. How long we keep personal data
We keep personal data while the pod operates, for the purposes described in this policy. When you ask us to delete your data (section 10), or when the pod closes, we delete or anonymise it where technically feasible, unless we need to keep specific data to comply with legal obligations or to establish, exercise or defend legal claims.
Records of your acceptance of our legal documents are deleted together with your account. Archived Discord desk-channel messages and the reports derived from them are kept while the pod operates and are deleted on request (section 2). Backups and logs held by our service providers are deleted on their own schedules.
10. Your rights
Where applicable data-protection law (for example the EU or UK GDPR) grants you rights, you may have the right to:
- access the personal data we hold about you and receive a copy;
- have inaccurate data rectified;
- have your data erased;
- restrict our processing;
- receive data you provided to us in a portable format (data portability);
- object to processing based on our legitimate interests;
- withdraw any consent you have given, without affecting processing before withdrawal; and
- lodge a complaint with a data-protection supervisory authority, in particular in the country where you live or work or where an alleged infringement took place.
To exercise a right, email thetradingjourney1@gmail.com. We may need to verify your identity. We will respond within the time required by applicable law. Some rights are subject to limits and exceptions; if we cannot fully meet a request, we will explain why.
11. Security
We use technical and organisational measures designed to protect personal data, including encrypted connections (HTTPS), authentication for member features, access controls on member data and restricted access to production systems. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Please keep your credentials safe and tell us promptly about any suspected unauthorised access.
12. Children
The Platform is not directed at children, and we do not knowingly collect personal data from children. If you believe a child has provided personal data to us, contact us and we will take appropriate steps to delete it.
13. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version on the Platform with a new "Last updated" date and give notice of material changes through the Platform, and may also notify you by email.
14. Contact
Questions or requests about this policy or your personal data: Kaizen Investments, George Town, Grand Cayman, Cayman Islands. Email: thetradingjourney1@gmail.com.