Privacy Policy

ForgeMuse (“ForgeMuse”, “we”, “us”) respects your privacy. This policy explains what personal data we collect when you visit forgemuse.net (the “Site”), join our beta, or use a ForgeMuse account and the desktop app (together, the “Service”), why we collect it, and the rights you have, including the rights granted to people in the European Economic Area (EEA), the United Kingdom and Switzerland under the GDPR.

A.1Who we are

ForgeMuse, registered in the Netherlands (KVK 42109815, btw-id NL869775716B01), is the data controller for personal data processed through the Service. For any privacy question, or to exercise your rights, contact us at [email protected].

A.2The short version

Your creative work stays on your machine. The code the swarm writes, the projects it builds, the prompts you give it: those live locally and run against your own Claude or ChatGPT subscription. They do not pass through our servers. What does reach us is the minimum needed to run accounts, billing and the voice features, listed honestly below.

A.3What we collect

• Beta signup details: the email address (and optionally name and project idea) you submit to join the beta. We also record, with that signup, the IP address and browser user-agent it came from, and which page it came from, to spot abuse of the form. That is kept with the signup rather than in the short-lived logs described below.
• Account details: when you sign in, our authentication provider WorkOS gives us your name, email address and avatar. We also store the sign-in tokens that connect your devices, so you can see and revoke them on your dashboard.
• Your devices: when the desktop app signs in, the connection it creates records the app version and which operating system it runs on, so we can support you and serve the right update. Your account also carries the date you first downloaded the app and when it last checked in. You can see every connected device on your dashboard and revoke any of them.
• Billing details: payments are handled by Stripe. Stripe collects your card details and billing address; we never see your full card number. We store your Stripe customer reference and your subscription status.
• Voice audio: speech-to-text can run one of three ways, and the app tells you which is active. It can run entirely on your machine, in which case no audio leaves it at all. It can go directly from your machine to Groq if you have supplied your own Groq key, in which case it does not touch our servers. Otherwise it is relayed through our server to Groq, so that our provider keys stay off your machine. Speech-out is relayed through our server to ElevenLabs. On the relayed paths we pass the data through and discard it: we do not store your recordings or your transcripts.
• Voice usage counts: so we can meter a plan and spot abuse, we keep a running daily total per account of how many speech requests you made and how much audio and text they amounted to. These are numbers only. They are derived from the traffic, never from its content, and they cannot be turned back into anything you said.
• Technical / server logs: our server automatically records basic technical data for security and reliability: your IP address, browser type (user-agent), the page requested and a timestamp. These logs are short-lived. We also keep an aggregate daily counter of how often each page was viewed; it is a bare number per page per day, with no cookie, IP address or anything else about you attached.
• Error diagnostics: if something breaks, our error-monitoring service (Sentry) receives technical details of the failure so we can fix it. We configure it not to include personally identifying content beyond what a request inherently carries (such as an IP address).
• What we do not collect: no advertising or analytics tracking, no behavioural profiling, no data sold or shared with advertisers, no third-party tracking pixels, and no copies of the code or projects the swarm builds for you.

A.4Why we process your data (legal bases)

• Contract: running your account, your subscription and billing, and relaying voice audio when you use voice features. Without this processing the Service cannot work.
• Consent: adding your email to the beta list and sending you beta updates. Every such email contains an unsubscribe link, and you can withdraw consent at any time.
• Legitimate interests: keeping the Service secure and operational (short-lived server logs, error diagnostics, abuse prevention). We balance this against your rights and freedoms.
• Legal obligation: keeping invoices and payment records for as long as Dutch tax law requires.

A.5Who processes data for us

We do not sell or rent your personal data. We share it only with the processors that run parts of the Service for us, under data-processing agreements:

• Stripe (payments and invoicing),
• WorkOS (sign-in),
• Groq (speech-to-text for voice input),
• ElevenLabs (text-to-speech for voice output),
• Resend (sending our email),
• Sentry (error monitoring),
• Cloudflare (serving app downloads) and our hosting provider.

Your prompts to the AI go from your machine to your own model provider, under your own subscription and their terms; they do not pass through our servers. Which provider that is depends on the engine you choose in the app: Anthropic if you run Claude Code, or OpenAI if you run Codex. You can run both, and each conversation goes only to the provider whose engine produced it. If you connect the app to your Anthropic account, it also asks Anthropic for your own plan usage so the app can show you what you have left; that request carries your Anthropic credentials and no content. We may disclose data where we are required to by law.

A.6International transfers

Several of these providers process data in the United States. Where data leaves the EEA, we rely on an appropriate safeguard: the EU–US Data Privacy Framework where the provider is certified, and otherwise the European Commission’s Standard Contractual Clauses.

A.7Cookies

We use only strictly necessary cookies required for the Site to function securely:

• a session cookie and a CSRF-protection token, set by our framework (Laravel) to keep signed-in sessions and forms secure.

Because these are essential and are not used for tracking or analytics, they are exempt from the consent-banner requirement under the EU ePrivacy rules, which is why you will not see a cookie banner. We do not set any advertising, analytics or tracking cookies. If that ever changes, we will ask for your consent first.

A.8Fonts and third parties

The Site’s fonts are self-hosted on our own servers. The website loads no fonts, scripts, pixels or other resources from Google or any other third party, so browsing it shares your IP address with nobody but us.

One thing in the desktop app works differently, and we would rather say so than let you find it in a firewall log. The first time you turn on the “Hey Muse” wake word, the app downloads the open-source wake-word models it needs from their public release page on GitHub. That download shows your IP address to GitHub, like any other download would. It happens once, the files are then cached on your machine, and it does not happen at all if you never enable the wake word.

A.9How long we keep it

• Beta signup emails: until the beta ends or you unsubscribe or ask us to remove you, whichever comes first.
• Account details: until you delete your account (which you can do yourself from the dashboard) or ask us to.
• Voice audio: not stored; relayed and discarded, or never sent at all on the on-device path.
• Voice usage counts: kept per day for the current and previous billing period so a plan can be metered, then deleted with your account.
• Device records: for as long as that device stays connected. Revoking it on your dashboard removes the record.
• Server logs: a short period (typically up to 30 days) for security, after which they are deleted or anonymised.
• Invoices and payment records: seven years, as Dutch tax law requires, even after account deletion.

A.10Your rights

If you are in the EEA, the UK or Switzerland, you have the right to access your data, correct it, delete it (the “right to be forgotten”), restrict or object to processing, port your data, and withdraw consent at any time. To exercise any of these, email [email protected] and we will respond within the timeframe the law requires (usually one month). You also have the right to lodge a complaint with your local data protection authority; in the Netherlands that is the Autoriteit Persoonsgegevens.

A.11California residents

We do not sell or share personal information as those terms are defined in the CCPA/CPRA, and we do not use it for cross-context behavioural advertising. California residents may exercise their rights to know, delete and correct by emailing [email protected]; we do not discriminate against anyone for exercising them.

A.12Children

The Service is not directed at children under 16, and we do not knowingly collect their personal data.

A.13Changes to this policy

We may update this policy as ForgeMuse grows. We will post the new version here and update the “Last updated” date above. Material changes will also be communicated by email to account holders and beta subscribers.

A.14Contact

Questions about this policy or your data? Email [email protected].