monody Privacy Policy
Last updated: 17 November 2026
BlazeApps LLC, 30 N Gould St Ste 100, Sheridan, WY 82801, USA ("we", "us") makes monody and is the controller of the personal data described here. Questions and requests: support@monody.ai.
The short version
- Your music stays on your computer. We never receive your audio, recordings, voice or project files.
- Usage and error data only if you say yes. The desktop app can send us which parts of monody you use and what goes wrong (errors, crashes, audio dropouts), so we can fix problems. It is off until you allow it, never includes your music, audio, what you type to the assistant or the names of your tracks, clips, projects or files, and Settings > Privacy turns it off. The app has no advertising. On monody.ai, optional Google Analytics runs only after you accept analytics cookies. You can reject them or change your choice at any time using Cookie settings in the footer.
- The assistant doesn't leave a copy with us. An AI request passes through our servers to OpenAI or Microsoft Azure OpenAI, depending on our service configuration. We do not store the request or reply. Provider processing and retention follow the applicable service terms and configuration. The app asks for your permission before it sends anything, and you can take that permission back at any time.
- We don't sell your data, share it for advertising, or train AI models on it.
- Stripe or Apple handles payments. Stripe on the web, Apple in the Mac App Store version. We never see your card.
What we collect, and when
Using the app without an account
monody works offline and without an account. Apart from usage and error data you have allowed (below), the only request the app makes on its own is an update check, when it starts and about once a day while it runs: it asks our server whether a newer version exists, sending its version number and platform (macOS or Windows). Like any internet request, this shows your IP address to our server; we don't store it.
Your projects, recordings, settings and logs stay on your computer (in Documents/monody and the app's settings folder). We have no access to them.
Your account
- Email address and password. We store the password only as a salted scrypt hash.
- When you created the account, confirmed your email and last used it, which version of the Terms you accepted, your plan, your credit balance, and whether the account is locked.
- Signed-in devices: for each sign-in, a label such as "monody on macOS", the platform, the app version, and when it was created, last used and expires. We store sign-in tokens only as hashes. The app keeps its token in your system's keychain (macOS Keychain or Windows DPAPI).
- On account.monody.ai, two cookies that are strictly necessary: one keeps
you signed in (
monody_session, 30 days) and one protects forms against forgery (monody_csrf, 1 year). These are essential account cookies; they do not depend on your choice about optional website analytics.
Purchases
For web purchases, Stripe collects and processes your payment details, billing name, address, country and tax information under its privacy policy (https://stripe.com/privacy). We send Stripe your email address and an account identifier to link your purchase to your monody account. We receive customer, checkout, subscription, invoice and transaction identifiers, payment status, plan, prices and billing periods. We keep Stripe's purchase notifications, which can contain billing details and amounts. We do not receive your full card number or security code. Where the checkout identifies Stripe Managed Payments as the seller, Stripe also acts as Merchant of Record.
Records of earlier Paddle purchases remain with Paddle and us under the retention periods below. Paddle's privacy policy applies to its processing.
In the Mac App Store version of monody, Apple is the seller. Apple collects your payment details and handles the charge, tax, renewal, cancellation and refund under its own privacy policy; we never see your Apple ID or your card. The app gives your signed purchase to our servers, and Apple sends us notifications about it. We receive and keep the transaction IDs, the product, the subscription status and dates (including renewals, refunds and whether it is a test purchase), and an identifier we generated for your account that the purchase carries so we can match it to you.
The AI assistant
monody asks for your permission before it sends the assistant anything. The first time you use the assistant (and again if what we send or who receives it changes) the app shows who receives your requests and what is sent, and sends nothing until you allow it. You can turn the permission off at any time in Settings > Privacy; the assistant then stops sending and asks again before its next request. The choice is stored on your computer.
When you send the assistant a request, our server passes to OpenAI or Microsoft Azure OpenAI:
- your request;
- a description of the open project: track and clip names, notes, device settings, tempo, automation and arrangement, with audio files referred to only by a content code;
- what is selected on screen, and the earlier messages of the conversation.
It never sends audio. Track and clip names are whatever you typed or imported (a dropped audio file's name becomes its clip's name, and an imported Ableton set keeps its track names), so leave personal details out of them if you don't want them sent. We don't send the AI provider your email or your account ID, and we ask it not to store the response for its own application features.
We don't store requests, project descriptions or replies. For each request we record the time, the model, token counts, the cost, the credits charged, the outcome and the provider's request ID, to meter credits, bill and investigate problems.
OpenAI or Microsoft Azure OpenAI handles requests under the applicable service terms and configuration. We do not control provider retention; if you do not want your requests sent there, do not allow the sharing.
Your chats with the assistant are kept on your computer, in a chats folder
inside the project's folder, so you can open one again and carry on where you
left off. We don't keep a copy: when you continue a chat, its earlier
messages go with your next request as described above, and nothing more. A
copy of the project folder includes its chats.
You can delete a chat, or all of a project's chats, from the assistant's chat
list.
If you set up monody with your own OpenAI API key (a developer option), requests go directly from your computer to OpenAI under your own agreement with OpenAI, and we receive nothing. If you connect monody to Claude or another app through MCP, that app reads your project under its provider's privacy policy, not ours.
Voice input
When you talk to the assistant or hum notes into a clip, monody records from your microphone only while the microphone (or Hum) is on. The microphone stays open for a minute afterwards so the next take starts at once, and your system may show it as in use; nothing is recorded in that minute. monody recognizes what you say and the notes you sing on your computer: your voice is never sent to us, to an AI provider or to anyone else, and the recording is discarded once it has been recognized. What it recognized, your words and the notes you sang, goes to the assistant like a typed request (see above).
Recognizing speech needs a model of about 550 MB, which the app downloads once, when you ask it to, from Hugging Face (huggingface.co). Like any download, that shows your IP address to Hugging Face; we send it nothing about you. Replies read aloud use only the voices installed on your computer.
Crash reports
If monody crashes, the next launch shows you the report and asks whether to
send it. Only if you choose Send do we receive the app version, build and
platform, the technical crash details, the last lines of the app's log, and
any note you add. Before sending, the app replaces your home-folder path with
~ and removes email addresses, keys and tokens. Log lines can still contain
project names or folder names outside your home folder; you can read the whole
report before you decide. If you are signed in, monody stores the report with
your account. We also send a copy to Sentry, our error-tracking provider, to
group crashes and help diagnose them. Sentry does not receive your account id
or email.
The cloud service also sends unexpected server errors to Sentry so we can diagnose service failures. Those events include the error type and stack trace; they do not include request bodies, account IDs, email addresses, or request URLs. Sentry processes this copy under its own service terms and retention settings.
Usage and error data (optional)
A release build of the app asks once whether to send usage and error data. Nothing is sent until you choose Send usage and error data. Settings > Privacy turns it off at any time: that stops it at once and deletes the random identifier the app made for it. If what we collect or who receives it changes, the app asks again. Settings > Privacy also shows what was recorded recently.
With your permission, the app sends:
- which parts of the app you use: the views, dialogs and settings you open, the controls you click (by their internal name, never the text on them), the kinds of edits you make (for example "add a MIDI clip"), assistant requests (their outcome, duration, model, token counts, the length of the request in characters, whether it was spoken, and which tools ran, never their text), exports, imports, stem separation and other long tasks;
- the size of the open project, in counts only (tracks, clips, devices, plug-ins, session clips and scenes);
- what goes wrong: error codes and messages, where in the app an error message was shown (not its text), crashes (the signal and the app version, not the report itself), audio dropouts and how loaded the audio engine ran, and slow steps;
- the app version and build, your operating system, processor type and number of processor threads, the app's language, the window size, your plan and whether you are signed in;
- a random identifier for this installation and one for each session. If you are signed in, the data is linked to your account ID.
Before anything leaves your computer, the app removes file and folder paths, file names, email addresses, keys and tokens, and text in quotation marks from messages. It never sends your music, audio or recordings, what you type or say to the assistant, the assistant's replies, or the names of your projects, tracks, clips or files. An error message can still describe what happened in general words.
The data goes to our servers, which pass it to PostHog, our analytics provider, without your IP address. We use it to see which features people use, to find and fix errors, and to improve monody.
Activity on your account
When you create an account, confirm your email, sign in, start a checkout, complete or change a purchase, send feedback or a crash report, or use the assistant through our servers, our servers record that event in PostHog with your account ID, never your email address and never the content of a request: for example the plan, price and currency of a purchase, or the model, outcome, token counts and cost of an assistant request. Errors on our servers are recorded without any account. We use this to understand and run the service. You can object to it by writing to support@monody.ai.
Emails
Every account gets service emails: confirming your email address, resetting your password and, after a purchase, confirming what you bought and how to start using it. Payment receipts and billing emails come from your payment provider.
News emails (monody releases and new features) go only to people who asked for them: with the box on the sign-up form, the button on the early-access page, or on your account page. Before we added that choice in October 2026, the way to get monody on monody.ai was an early-access sign-up that said "We'll email you when monody is released", so accounts created before then get these emails too. We send them only to confirmed email addresses. Every news email has an unsubscribe link, and your account page turns them off. We keep when and where you said yes. Resend sends these emails for us and keeps your address on our list, marked unsubscribed if you unsubscribe, so you aren't emailed again. We don't track whether you open our emails or click their links.
When you contact us
Your email address and what you write, so we can answer you.
Our websites
On monody.ai, we ask before loading Google Analytics 4, provided by Google LLC. If you accept, it helps us understand which pages people visit, which sources bring visitors, and clicks on our early-access, download and checkout links. A link click does not tell us that a download, registration or purchase was completed.
Analytics receives page addresses and titles, referring websites, campaign labels, timestamps, browser and device information, and a random cookie identifier. Google processes your IP address to provide approximate location information; GA4 does not log or store individual IP addresses. We do not send your account ID, email address, form contents, music or project data to Analytics. We remove URL fragments and query parameters other than restricted campaign labels from the page addresses we send.
We do not load Google Analytics or send it measurement requests before you accept or if you reject. We do not use Google Signals, advertising cookies, remarketing, or session recordings. This website measurement is not installed in the desktop app or on account.monody.ai.
| Cookie | Purpose | Duration |
|---|---|---|
monody_analytics_consent |
Remembers whether you accepted or rejected analytics; contains the choice, policy version and expiry, not a visitor ID | 180 days |
_ga, _ga_* |
Google Analytics identifiers for measuring visits and sessions; set only after acceptance on monody.ai | Up to 180 days, without extending expiry on each visit |
monody_session |
Keeps you signed in on account.monody.ai | 30 days |
monody_csrf |
Protects account forms against forgery on account.monody.ai | 1 year |
Your choice: Accept analytics and Reject analytics are available in the same banner. Rejecting does not limit use of the website. Open Cookie settings in the footer to change your choice, including withdrawing consent. Rejecting after acceptance stops further collection, removes the Analytics cookies this site can access, and reloads the page to unload the Analytics script. Withdrawal does not affect processing that took place before withdrawal. To request deletion of previously collected data, contact support@monody.ai; we may need information to identify the relevant records because Analytics is not linked to your monody account. We ask again when your saved choice expires or our consent version changes.
Read how Google uses data from partner sites and Google's privacy policy.
Our hosting providers also log technical request data (IP address, time, page, browser) for security and operations, under their own retention policies. Web checkout redirects you to Stripe's hosted payment page. Stripe's privacy policy covers its payment processing and related storage. Earlier Paddle purchases may still use Paddle's billing portal.
Changes our staff make to your account
When our staff change something on your account (your plan, credits, or a lock), we record the change, who made it, and the account's email address, for accountability and to resolve disputes.
Why we use it
| Purpose | Legal basis (GDPR) |
|---|---|
| Running your account, sign-in, plans, credits, AI requests, service emails, updates | Performing our contract with you (Art. 6(1)(b)) |
| Security, preventing fraud and abuse, rate limits, records of staff changes, defending legal claims | Our legitimate interest in a safe, reliable service (Art. 6(1)(f)) |
| Diagnosing unexpected cloud-service errors | Our legitimate interest in keeping the service reliable (Art. 6(1)(f)) |
| Crash reports | Your choice to send one (Art. 6(1)(a)); you can ask us to delete it |
| Optional usage and error data from the app | Your consent (Art. 6(1)(a)); withdraw in Settings > Privacy |
| Account activity events in our product analytics | Our legitimate interest in understanding and improving our service (Art. 6(1)(f)); you can object |
| Optional website analytics | Your consent (Art. 6(1)(a)); withdraw through Cookie settings |
| News emails | Your consent (Art. 6(1)(a)); withdraw with the link in any news email or on your account page |
| Billing and tax records | Legal obligations (Art. 6(1)(c)) |
We don't make decisions about you based solely on automated processing that have legal or similarly significant effects. Automatic rate limits or fraud checks can block a request for a while; write to us and a person will look at it.
Who receives it
We share personal data only with the providers that help us run monody, under contracts that limit what they may do with it, and when the law requires it.
| Who | What for | What they get |
|---|---|---|
| Microsoft Corporation (USA), through Azure OpenAI, or OpenAI (USA) | The AI model behind the assistant, only after you allow it | AI requests as described above, under the applicable provider service terms and configuration. |
| Render Services, Inc. (USA) | Hosts our servers and database, located in Frankfurt, Germany | All data held by our cloud service |
| Stripe (the Stripe entity serving the purchase) | Processes web payments; Merchant of Record only where identified at checkout | Account email and identifier, purchase and billing data |
| Paddle (Paddle.com Market Ltd, UK; Paddle.com Inc., USA) | Seller and Merchant of Record for earlier Paddle purchases | Earlier purchase and billing data |
| Apple Inc. | Seller and payment processor for purchases made in the Mac App Store version; an independent controller for purchase data | Purchase and billing data; we receive the transaction data described under Purchases |
| Resend (USA) | Sends our service and news emails, and keeps the news list | Your email address, the email, and whether you unsubscribed from news |
| Vercel Inc. (USA) | Hosts monody.ai | Website request logs |
| PostHog, Inc. (USA) | Product analytics | Usage and error data from the app, only with your permission, and account activity events, with your account ID or a random installation ID; never your IP address, email, music or assistant requests |
| Google LLC (USA) | Optional website analytics, only with your consent | Website interaction and device data described above |
| Namecheap, Inc. and Google LLC (USA) | Forward and hold the email you send us | Your emails to us |
We may also disclose personal data when the law or a valid legal process requires it, to protect people's rights and safety, or as part of a merger or acquisition, in which case the successor remains bound by this policy. We don't sell personal data and don't share it for cross-context behavioral advertising, as California law defines those terms.
International transfers
Our database is in the EU (Frankfurt). Some of the providers above process data in the United States or the United Kingdom. For transfers out of the EEA, the UK and Switzerland we rely on adequacy decisions (including, where a provider is certified, the EU-U.S. Data Privacy Framework) or on the European Commission's Standard Contractual Clauses. If you are in Turkey, you give your data directly to us, a company outside Turkey, and we protect it as this policy describes.
How long we keep it
- Account data and devices: while your account exists. When you delete your account, they are deleted at once; when you ask us to, within 30 days.
- AI usage cost records (the amount, date, model, token counts and whether a request finished): tied to your account while it exists. When you delete your account, they are not deleted but are cut loose from you: your user ID, your email address, the provider's request ID and any note our staff wrote about the record are removed, and what stays is the figures with no link to you. We keep them to account for what our AI provider bills us (a request still running when you delete your account is settled in the same way). They contain no prompts, messages or project content.
- Sign-in records that have expired or been signed out: 30 days.
- Your address on the news list at Resend: while your account exists. Deleting your account removes it.
- Billing records (subscriptions, credit purchases, payment providers' notifications): as long as tax and accounting law requires, generally up to 10 years.
- Records of staff changes to your account: until disputes about them are no longer possible, and no longer than 5 years after the account is closed.
- Crash reports: until we have fixed the problem, and no longer than 2 years.
- Emails to us: as long as needed to answer you and keep a record, up to 3 years.
- Hosting logs and AI requests at the AI provider: as described above.
- Usage and error data and account activity events (PostHog): up to one year, then deleted. When you delete your account, we ask PostHog to delete the events linked to it; PostHog does that in its weekly deletion runs, so they can stay there for a few more weeks. To have them deleted while you keep your account, write to support@monody.ai.
- Website analytics: user-level and event-level data are retained in GA4 for 2 months, without resetting user retention on new activity. Aggregated reports may be retained longer. Website cookies and your saved choice have the durations listed above.
Deleted data can remain in encrypted database backups for a short time until they roll over.
Your rights
Wherever you live, you can ask us to give you access to your personal data or a copy of it, correct it, delete it, restrict its use, or stop using it on the basis of our legitimate interests, and you can withdraw a consent you gave. These rights come from the GDPR (EU and UK), Article 11 of KVKK (Turkey) and the privacy laws of US states such as California; we offer them to everyone. We will not treat you differently for using them.
Write to support@monody.ai from your account's email address. We may need to confirm it is you, and we answer within one month. You can delete your account yourself with "Delete your account" on your account page at account.monody.ai, or ask us to. Deleting it cancels any active subscription. The app keeps working without an account.
You can also complain to a data protection authority, for example the one where you live, the UK's Information Commissioner's Office or Turkey's Kişisel Verileri Koruma Kurumu (https://www.kvkk.gov.tr). We would like the chance to help first.
Security
Connections use TLS. Passwords and sign-in tokens are stored only as hashes, and licenses and app updates are cryptographically signed. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires. Please report security problems to support@monody.ai.
Children
monody is not for children under 16, and we don't knowingly collect their data. If you think a child has given us personal data, write to us and we will delete it.
Changes
We post changes here with a new date. We tell you about material changes by email or in the app before they take effect.
Contact
BlazeApps LLC, 30 N Gould St Ste 100, Sheridan, WY 82801, USA · support@monody.ai