ALCHMYBack to alchmy.io

LEGAL

ALCHMY Privacy Policy

Version 1.1 · Effective

This Privacy Policy explains how Electropreneurs LLC collects, uses, discloses, retains, and otherwise processes personal information in connection with ALCHMY, including the ALCHMY website, accounts, closed-beta program, desktop application, related services, and support interactions (collectively, the “Service”).

ALCHMY is operated by:

Electropreneurs LLC
4460 Bermuda Dunes Place
Oceanside, CA 92057
United States

In this Privacy Policy, “ALCHMY,” “we,” “us,” and “our” refer to Electropreneurs LLC.

This policy should be read together with the ALCHMY Terms of Service. The version number and effective date of this policy are shown at the top of the page where it is published. If you accepted an earlier version, the changes since that version are summarized at the end of this policy.

1. Scope

This Privacy Policy applies to personal information we process when you:

  • visit or interact with the ALCHMY website;
  • join the ALCHMY waitlist;
  • receive an invitation to the closed beta, or accept these documents in order to take part;
  • create or use an ALCHMY account;
  • use the ALCHMY desktop application with Ableton Live;
  • send ALCHMY a typed or spoken request;
  • participate in a closed beta or other pre-release program;
  • communicate with us for support;
  • voluntarily provide feedback or diagnostic information; or
  • otherwise interact with the Service.

This policy describes both information processed on ALCHMY’s systems and information that the desktop application stores locally on your Mac.

2. What ALCHMY Is and How It Works

ALCHMY is an AI assistant for Ableton Live. It runs as a desktop application on your Mac and connects to your open Live Set through an Ableton Control Surface script (“AlchmyBridge”) that the installer places in your Ableton User Library.

You talk to ALCHMY in one chat window, by typing or by speaking. ALCHMY reads details of your open Live Set, sends your request and that context through ALCHMY’s own service (the “gateway”) to an AI provider, and returns an answer. When you ask ALCHMY to make a change, it makes that change directly in your Live Set through AlchmyBridge. There is no separate approval step. Section 6 of the Terms of Service and Section 3 of this policy describe this in more detail.

ALCHMY does not take screenshots of your screen, does not capture the audio coming out of Ableton Live, and does not record from your microphone except while you deliberately use Voice as described in Section 4.

3. Information We Collect

The information ALCHMY processes depends on how you interact with the Service.

3.1 Waitlist Information

When you join the ALCHMY waitlist, we may collect:

  • your name;
  • email address;
  • operating-system preference, such as macOS or Windows;
  • the source or location of the waitlist form you used;
  • submission and update timestamps; and
  • technical information necessary to receive and secure the submission.

We use this information to maintain the waitlist, communicate with prospective users, plan platform support, administer beta access, and understand interest in ALCHMY.

3.2 Account, Beta, and Acceptance Information

If you are invited to the closed beta, we process information including:

  • your email address;
  • your account identifier;
  • authentication and session information, handled through our authentication provider (we never see or store your plaintext password);
  • invitation and entitlement status, which determines whether your account may use ALCHMY;
  • an installation identifier, a random identifier for your Mac that the application sends with each request;
  • the application version and build you are running; and
  • a record of your acceptance of the Terms of Service and this Privacy Policy: the version you accepted, the date, and the country (and state or province, if any) you told us you live in.

How acceptance is recorded during the closed beta: we send you the current Terms of Service and Privacy Policy before you receive the application. You accept by replying to our invitation from the email address we will use for your account. We keep your reply as the record of acceptance, and we enter your account identifier, your declared country of residence, and the version you accepted into the configuration of ALCHMY’s service. That configuration is what allows your account to use ALCHMY’s AI features: typed requests, Voice, and quick commands all require a current acceptance. We never derive your residence from your IP address or from anything the application sends; it comes only from what you tell us.

3.3 Your Requests and Conversation

When you send ALCHMY a message, typed or spoken, we process:

  • the message itself;
  • the recent conversation: earlier turns of the current chat, short summaries ALCHMY keeps of the chat, and the last operation it was working on;
  • ALCHMY’s answers and the changes it reports making;
  • the song key, genre, or other project facts you tell ALCHMY, which it keeps as context for that Live Set; and
  • information returned by the tools ALCHMY uses to read your Live Set and your Sample Library (see 3.4 and 3.5).

Because what you type or say is user-authored, it may contain personal information or information about your creative work. Avoid including sensitive personal information that ALCHMY does not need to answer your request.

3.4 Details of Your Live Set

To answer a request, ALCHMY reads your open Live Set through AlchmyBridge and sends what it read with the request. Depending on the request this includes:

  • track, clip, device, and arrangement-marker names;
  • tempo, time signature, Live’s Scale setting, and the song key you give ALCHMY;
  • mixer state: fader levels, pan, mute, solo, sends, output routing, and the settings of devices on your tracks, including device and plug-in names;
  • the MIDI notes in clips ALCHMY reads;
  • the arrangement: sections, clips, and empty bars; and
  • the results of changes ALCHMY made, so it can verify them.

Names you give tracks, clips, devices, and markers are sent exactly as they appear in Live. If those names contain personal information, for example a collaborator’s name, that information is sent with the request.

3.5 Your Sample Library and Audio Files

ALCHMY has a Sample Library made up of the sample folders you add and the Factory sounds that ship with ALCHMY. ALCHMY analyzes your samples locally on your Mac (for example their tempo, key, and loudness) so it can find the right sound when you ask for one. Your sample audio is never uploaded.

When you ask for a sound, ALCHMY’s search results, including the file names and the locations of those files on your Mac, are sent with the request so the AI can choose and place a sample. File locations include your macOS user name. The same applies to the file locations of audio clips already in your Live Set when ALCHMY reads them.

3.6 Voice: Your Spoken Requests

ALCHMY can turn a spoken request into text. Section 4 describes exactly when the microphone is on, what is sent, and what is kept.

3.7 Quick Commands

A few short requests (adding a high-pass or low-pass filter, setting the tempo, creating a track) run without waiting for the full assistant. Exact phrasings are recognized on your Mac. Requests that are not exact phrasings are also sent, as text, to a second AI provider, TypeSafe AI, Inc., to check whether they are one of those commands. Section 5 describes this in detail.

3.8 Technical, Security, and Operational Information

We process information necessary to authenticate users, operate the Service, protect it from abuse, troubleshoot failures, enforce usage limits, and maintain reliability. On ALCHMY’s servers this is metadata only:

  • user and account identifiers;
  • installation identifiers;
  • request identifiers and timestamps;
  • the application version, build, and source commit;
  • authentication and entitlement events;
  • which AI model answered, token counts, estimated cost, and outcome codes;
  • for a spoken request, the size of the upload, which reflects how long you spoke;
  • rate-limit, quota, and spend information;
  • error categories and security audit events; and
  • network information made available to our infrastructure providers, which includes IP addresses.

ALCHMY’s servers are built and tested so that your messages, your spoken recordings, their transcripts, the details of your Live Set, and ALCHMY’s answers are not written to our logs or databases: every record the gateway writes is limited to a fixed list of metadata fields, and our automated tests plant sample content in requests and check that none of it reaches a log line or a database row. Request content passes through the gateway in memory on its way to and from the AI provider.

Not every communication from the desktop application is a request you made. ALCHMY also communicates with its services for sign-in, entitlement, and configuration, and it checks for software updates automatically (Section 7.4).

3.9 Keyboard Permission for Push-to-Talk

Push-to-talk (holding Right Command while Ableton Live is in front) requires macOS’s Input Monitoring permission. ALCHMY asks for it only after you choose to turn push-to-talk on in your account menu, and only when Voice is available for your account. ALCHMY uses that permission only to check whether Right Command is held and whether another key or a mouse button is pressed at the same time. It does not receive the text you type, it does not record which keys you press, and nothing about your keys is stored, logged, or sent. The Record button in ALCHMY needs no such permission.

3.10 Support, Feedback, and Diagnostics

If you contact us or voluntarily send feedback, we may process your contact information, correspondence, bug reports, feature requests, feedback, and any screenshots, recordings, or files you choose to share with us.

ALCHMY does not automatically send us diagnostic files, crash reports, or usage telemetry. Sharing a log or a diagnostic record with us is always a separate action you take. Please review materials before sending them and avoid sharing creative or personal information that is unnecessary to diagnose the problem.

4. Voice: When ALCHMY Listens and What Happens to Your Recording

4.1 When the Microphone Is On

ALCHMY uses your microphone only:

  • while you hold the push-to-talk key (Right Command) with Ableton Live in front; or
  • between clicking Record and Stop in the ALCHMY window;

and only when Voice is available for your account. ALCHMY shows that it is listening. It never listens on its own, continuously, or for a wake word. A recording stops automatically after 60 seconds. If another key or a mouse click joins Right Command within the first 350 milliseconds (about a third of a second), recording never starts; after that, pressing another key or clicking cancels the recording at once and nothing is sent. The first time you record, macOS asks you whether ALCHMY may use the microphone.

4.2 What Is Sent, and to Whom

Recordings shorter than half a second, or silent, are discarded on your Mac without being sent anywhere. Otherwise the recording is sent through ALCHMY’s gateway to OpenAI’s speech-to-text service, only to turn it into text. ALCHMY’s gateway makes one call to OpenAI’s audio transcription endpoint with the recording, the language setting (English), and a fixed list of music-production vocabulary that helps the transcription. It sends no conversation, no details of your Live Set, no Library names, and no account identifiers with the recording.

Anything the microphone picks up while ALCHMY is listening, including other people’s voices or music playing in the room, is part of the recording and is sent. Do not record other people without their permission.

4.3 What Is Kept

ALCHMY does not keep your recording. On your Mac it exists only in memory while it is being captured and sent, and that memory is cleared afterwards; it is never written to disk, to a log, or to a diagnostic record. On ALCHMY’s servers it passes through in memory and is never stored. ALCHMY’s servers keep only metadata about the request (Section 3.8).

OpenAI processes the recording to produce the text. OpenAI’s published API data documentation states that data sent to its API is not used to train its models unless the customer opts in; we have not opted in, and we have confirmed that the data-sharing settings for ALCHMY’s OpenAI account are turned off. The same documentation (as we read it on October 18, 2026) lists the audio transcription endpoint as keeping no abuse-monitoring logs and no application state, while stating that abuse-monitoring logs for API usage are otherwise kept for up to 30 days by default. We have not yet confirmed with OpenAI how those statements apply to ALCHMY’s account. Until we have, you should assume that OpenAI may keep a spoken request for up to 30 days for abuse monitoring under its API policies. We have no zero-data-retention agreement with OpenAI, and we cannot recall a recording once it has been sent.

If you cancel, or sign out, before the recording starts uploading, nothing is sent. Once the upload has started it cannot be recalled; OpenAI may still turn it into text, and ALCHMY then discards that text.

4.4 What Happens to the Text

The transcript is treated exactly like a message you typed. With push-to-talk, it is sent to ALCHMY as soon as you release the key, and ALCHMY shows the text on screen briefly; if a push-to-talk recording reaches the 60-second limit, the text goes to the message box for you to check instead of being sent. With the Record button, the text appears in the message box so you can review it before pressing Send, and it is saved in that chat as an unsent draft until you send or delete it. From there it follows the same path as a typed message (Sections 3.3 and 3.7), so a spoken request that is not an exact quick command is also sent, as text, to TypeSafe.

5. Quick Commands and TypeSafe

To run a few short commands faster, ALCHMY’s gateway sends the text of each message that is not an exact command ALCHMY already recognizes, typed or spoken and up to 4,000 characters, to TypeSafe AI, Inc. (255 California St, Suite 1300, San Francisco, CA 94117, United States). TypeSafe answers only whether the message is one of a small, fixed list of commands. ALCHMY then parses the command and acts on it locally, or hands the request to the full assistant.

TypeSafe receives the words of your message exactly as you typed or spoke them. If your message names a track or a device, TypeSafe receives that name. ALCHMY adds nothing else: no account details, no other details of your Live Set, no conversation history, no file locations, and no audio. Your answers to questions ALCHMY asks you are never sent to TypeSafe.

TypeSafe’s published privacy policy states that it does not train or fine-tune models on customer prompts, that its services are hosted in the United States, and that it retains personal data for as long as reasonably necessary to provide its services; its customer agreement states that it may keep technical records derived from requests (such as classifications, statistics, and metrics) and use them to improve its services. TypeSafe has not committed to a specific retention period for ALCHMY’s requests. We rely on TypeSafe’s published terms for these statements and cannot recall a message once it has been sent.

ALCHMY currently cannot switch off quick-command recognition on its own for one account: one acceptance record covers your use of all of ALCHMY’s AI features together. If you object to quick-command recognition, contact us (Section 11); until a separate control exists, stopping it means pausing the AI features for your account.

6. Information Stored Locally on Your Mac

ALCHMY stores the following on the computer where you use it, under your control:

  • your chats, including your messages, the text of your spoken requests, unsent Record drafts, ALCHMY’s answers, and the song key and other project facts you told ALCHMY, in a database at ~/Library/Application Support/SmartCoproducer/labs/;
  • a diagnostic record of each request, in the same folder: the full request and response, including the details of your Live Set that were sent, the model’s replies, and the tools ALCHMY used. ALCHMY deletes these records after 30 days, or sooner once they exceed 250 MB or 1,000 records. Chats are not deleted automatically;
  • your Sample Library: the folders you added (their locations), file names, ALCHMY’s analysis of each sample, the Factory sounds, copies of sounds you dragged into Live, and an “ALCHMY” folder inside your Ableton User Library that holds samples and presets placed into your Sets;
  • your saved sign-in, in the macOS Keychain; an installation identifier; and a local key the application uses to talk to Ableton Live;
  • application logs in ~/Library/Logs/SmartCoproducer that are designed to record what the application did (start-up, connection and error categories), not your messages, recordings, or answers; and
  • the ordinary website data and cache of the application window.

Only your macOS user account can read these files. They are not tied to your ALCHMY account: anyone who signs in to ALCHMY on the same macOS user account can see your chats. Signing out of ALCHMY removes your saved sign-in but does not clear your chats or diagnostic records. Do not share one macOS user account between different ALCHMY users.

You can delete a chat from the chat list or clear the current chat’s memory at any time. The bundled uninstaller has two modes: the standard uninstall removes the application and its Ableton components and keeps your data; the complete uninstall also removes the chats, diagnostic records, Sample Library data, logs, saved sign-in, and the local Ableton key, but keeps the copies of sounds you dragged into Live, the “ALCHMY” folder in your Ableton User Library (your Sets may reference it), and records left by earlier ALCHMY versions in ~/.alchmy-ax, which you can delete yourself. The macOS Microphone and Input Monitoring permissions are managed by macOS in System Settings and are not changed by the uninstaller.

7. How We Use Information

We use the information described in this policy to:

  • provide and operate ALCHMY, including reading your Live Set and making the changes you ask for;
  • authenticate users and maintain accounts;
  • administer invitations, beta access, and entitlement;
  • record and enforce acceptance of the Terms of Service and this policy, including which countries ALCHMY is available in;
  • turn your spoken requests into text when you use Voice;
  • recognize quick commands;
  • generate AI answers and carry out requested changes;
  • maintain conversation continuity and application state;
  • secure the Service and prevent abuse;
  • enforce quotas, rate limits, and spending limits with our AI providers;
  • troubleshoot and diagnose failures;
  • provide support;
  • communicate with you about your account or beta participation;
  • deliver software updates;
  • understand demand for ALCHMY and platform support;
  • evaluate and improve the Service and develop new functionality;
  • comply with legal obligations;
  • establish, exercise, or defend legal claims; and
  • protect ALCHMY, our users, and others.

We do not use your name, likeness, screenshots or recordings of your work, your music, or statements you make about ALCHMY in public materials, such as marketing, case studies, or testimonials, without your separate permission.

Where applicable law requires a specific legal basis for processing, our bases may include performance of our agreement with you, our legitimate interests in operating, securing, supporting, and improving the Service, compliance with legal obligations, and consent where consent is required or is the appropriate basis. The applicable basis depends on the information, purpose, and jurisdiction.

7.1 Your Agreement to Recording

When you accept this policy and the Terms, you also agree that, when you hold the push-to-talk key or click Record, ALCHMY may record what you say and send the recording through its service to OpenAI to turn it into text. That is your own agreement to being recorded. It does not cover other people. If anyone else may be heard while ALCHMY is listening, you are responsible for telling them and for obtaining any consent that the recording laws applicable to you and to them require (some United States states require the consent of everyone who is recorded), or for not using Voice in that situation. Your agreement here is separate from, and does not replace, any data-protection legal basis described above.

7.2 Changes ALCHMY Makes to Your Live Set

Processing your Live Set includes writing to it: when you ask, ALCHMY adds, edits, and removes tracks, clips, MIDI notes, devices, device settings, mixer settings, arrangement markers, and samples in your open Set, acting on the track selected in Live or the one you name. ALCHMY reports what it changed. ALCHMY has no undo of its own. To take a change back, use Live’s Edit ▸ Undo (Cmd+Z). One request can produce several Undo steps, so you may need to undo more than once; Live’s Undo history belongs to the open Set and is lost when you close it; Undo does not remove sample files that ALCHMY copied into your Ableton User Library; and if ALCHMY stops part-way through a change, the completed steps remain in your Set until you undo them. Save before you ask for changes, and work on copies of Sets you care about; see Section 8.5 of the Terms of Service.

7.3 AI Providers

When you use ALCHMY, information needed to answer your request is transmitted through ALCHMY’s gateway to an AI provider. ALCHMY uses OpenAI for answers and for speech-to-text, and TypeSafe for quick-command recognition.

For answers, the information sent to OpenAI is your message, the recent conversation, the details of your Live Set and Sample Library described in Section 3, and ALCHMY’s instructions to the model. ALCHMY configures every request so that OpenAI does not store it as application state, and it never attaches your name, email address, account identifier, or installation identifier to a request. Your message and the names and file locations it contains can nevertheless identify you, and they are sent as they are.

OpenAI’s published API data controls state that API data is not used to train OpenAI models unless the customer opts in, that OpenAI may keep abuse-monitoring logs for up to 30 days by default, and that eligible customers may apply for zero data retention. We have confirmed that the data-sharing settings for ALCHMY’s OpenAI account are turned off. We have not been approved for zero data retention and do not claim it. We cannot delete a request from OpenAI’s systems once it has been sent.

7.4 Software Updates and Downloads

You download ALCHMY from, and ALCHMY checks for updates on, our release server at download.alchmy.io, which runs on Cloudflare’s network. Each download and each daily update check sends your IP address, the time, the file requested, and your application version to that server. ALCHMY does not send a profile of your computer. Cloudflare processes those requests for us and also uses traffic data to run and secure its own network under its terms. The files stored there are the public installers and update feed, never your data.

8. AI and Product Improvement

8.1 What We Do Not Do Today

ALCHMY does not use your messages, recordings, transcripts, Live Set details, samples, or any other content from your use of ALCHMY to train or fine-tune any model, and we do not run benchmarks on it. The closed-beta application sends no usage telemetry, no crash reports, and no in-app feedback: the shipped build contains no component that does so, and there is no setting that turns such a component on. We have confirmed that OpenAI’s data-sharing settings for ALCHMY’s account are turned off, and TypeSafe’s published terms state that it does not train on customer inputs, as described in Sections 4.3, 5, and 7.3.

8.2 Product Interaction Information

Subject to applicable law, we may in the future use product-interaction information to evaluate and improve ALCHMY: which features you use and when, timings, outcomes and error categories of requests, and ratings or feedback you give us about ALCHMY itself. Product-interaction information does not include the text of your prompts or spoken requests, the details of your Live Set, your sample names or file locations, or any other creative material contained in your requests, in ALCHMY’s answers, or in ALCHMY’s records of them. This statement preserves our ability to develop ALCHMY in the future; it does not describe a current practice, and we will update this policy and provide notice before any such collection begins. If we ever want to use any information from your use of ALCHMY, including prompts, transcripts, interaction records, or product-interaction information, to train or fine-tune a machine-learning model, we will first update this policy and the Terms of Service, give you notice, and obtain your separate authorization where required. Your acceptance of this policy is not that authorization.

8.3 Creative Assets

We do not treat your use of ALCHMY as permission to use your audio recordings, stems, MIDI, Ableton Live project files, samples, or similar creative works, or the creative material embedded in your prompts, spoken requests, Live Set details, and ALCHMY’s records of your sessions, to train generative AI models. If we want to use any of that material for model training in the future, we will establish a separate process and seek your authorization rather than relying on your use of ALCHMY or your acceptance of the Terms of Service.

8.4 Spoken Requests and Detailed Project Context

Your spoken recordings, their transcripts, and the detailed project context ALCHMY sends with a request are used only to provide the requested functionality and are not used by ALCHMY as training material for ALCHMY’s models. If we materially change this practice, we will update our disclosures and obtain authorization where required by applicable law.

9. How We Disclose Information

We disclose personal information to the service providers and other recipients necessary to operate ALCHMY. Each provider acts under its own terms and may use its own subprocessors, which it publishes.

Infrastructure, Authentication, and Database

Supabase (Supabase Pte. Ltd.) provides authentication and the database that holds account, entitlement, installation, and usage records. Its servers for ALCHMY are in the United States (AWS us-east-1).

Vercel (Vercel Inc.) runs ALCHMY’s gateway in the United States and hosts the ALCHMY website. Vercel’s platform keeps operational logs of requests to the gateway and the website, which include IP addresses, for its own retention period.

AI Providers

OpenAI provides answers and speech-to-text (Sections 4 and 7.3).

TypeSafe AI, Inc. provides quick-command recognition (Section 5).

Downloads and Updates

Cloudflare, Inc. hosts and delivers ALCHMY’s installers and update feed at download.alchmy.io (Section 7.4).

Email

We use Google Workspace (Google LLC) for the support@alchmy.io mailbox that receives your acceptance replies, support requests, and privacy requests.

Apple

Apple notarizes the ALCHMY software and shows the macOS permission dialogs. Apple does not receive your data through ALCHMY.

Professional and Legal Recipients

We may disclose information to attorneys, accountants, insurers, auditors, consultants, or other professional advisers where reasonably necessary.

Legal and Safety Disclosures

We may disclose information if we reasonably believe disclosure is necessary to comply with applicable law, regulation, legal process, or lawful governmental request; to enforce our agreements; to detect, investigate, or prevent fraud, abuse, or security incidents; to protect the rights, property, or safety of ALCHMY, our users, or others; or to establish, exercise, or defend legal claims.

Business Transfers

If ALCHMY or Electropreneurs LLC is involved in a merger, financing, acquisition, reorganization, sale of assets, or similar transaction, information may be transferred as part of that transaction subject to applicable law.

We do not sell your music or creative assets. We do not sell personal information, and we do not share it for cross-context behavioral advertising.

10. Retention

We retain different categories of information for different periods based on why the information is needed.

10.1 Waitlist

We generally retain identifiable waitlist information for up to 24 months from the person’s waitlist signup, unless the person asks us to delete it earlier, the person becomes an ALCHMY user and the information becomes subject to another applicable retention purpose, we are required to retain particular information by law, or a limited record is reasonably necessary to establish, exercise, or defend legal claims. During the closed beta this process is operated manually; we do not represent that every waitlist record is deleted at the exact moment it reaches 24 months.

10.2 Gateway and Operational Records

ALCHMY’s gateway records are kept for category-specific periods: request and event records for 30 days, security audit records for 90 days, and the usage and cost ledger for 365 days. During the closed beta the purge that removes expired records is run manually by the founder, at least once a month, so a record can remain up to a month beyond its period. Records used to prevent duplicate requests and the per-day usage counters that enforce your limits contain no content and are kept until your account is deleted. If you ask us to delete your data, every record tied to your account is deleted at that point, except that your account identifier in the usage and cost ledger is replaced with a pseudonym and security audit records expire on their own 90-day schedule.

Our hosting and database providers keep their own operational and sign-in logs, which can include your IP address, for the retention periods set by their plans.

10.3 Acceptance Records

We keep the record of your acceptance of the Terms of Service and this policy, including your declared residence, for as long as your account exists or the closed beta runs, and afterwards as long as reasonably necessary to demonstrate what you accepted.

10.4 Spoken Recordings, Transcripts, and Requests at Our AI Providers

ALCHMY keeps no recordings and no request content on its servers. What OpenAI and TypeSafe retain is governed by their published terms as described in Sections 4.3, 5, and 7.3.

10.5 Local Data

Your chats stay on your Mac until you delete them. Diagnostic records are deleted automatically after 30 days or when they exceed 250 MB or 1,000 records. Local information is under the control of the macOS user account in which ALCHMY runs; we cannot see or delete it remotely.

10.6 Account and Legal Records

We may retain account, entitlement, acceptance, security, support, and legal records for as long as reasonably necessary for the purpose for which they were collected, to meet legal obligations, resolve disputes, protect the Service, and enforce agreements. Backups and service-provider infrastructure may retain residual copies for limited periods according to their retention cycles.

11. Your Privacy Rights and Choices

Depending on where you live and applicable law, you may have rights concerning your personal information, including the rights to know or confirm whether we process your personal information; to request access to it; to request correction of inaccurate information; to request deletion of certain personal information; to request restriction of or to object to certain processing; to obtain information about recipients; to request portability; to withdraw consent where processing is based on consent; and to exercise these rights without unlawful discrimination.

These rights are not absolute. Applicable law may permit or require us to retain information or decline a request in certain circumstances.

To make a privacy request, email support@alchmy.io from the address you use to sign in to ALCHMY. We may need to verify your identity. During the closed beta, requests are handled manually by the founder: we acknowledge a request within 3 working days and answer within 30 days. We will search ALCHMY’s own systems rather than treating deletion of your account as equivalent to deletion of every associated record, and we will tell you what we deleted, what we kept and why (for example security audit records that age out on their own schedule), and what you need to delete on your own Mac, with instructions.

What we cannot do: we cannot recall a recording or a message that OpenAI or TypeSafe has already processed; their own terms govern what they keep. We also cannot delete the request logs that Cloudflare, Vercel, and Supabase keep about network requests; those expire under each provider’s own retention.

Your choices in the application:

  • Voice: you do not have to use it. Do not press Record or hold Right Command, or turn ALCHMY off in System Settings ▸ Privacy & Security ▸ Microphone. You can type every request.
  • Push-to-talk: you can leave it off, or revoke ALCHMY’s Input Monitoring permission in System Settings.
  • Quick commands: see Section 5.
  • Local data: delete a chat, clear a chat’s memory, sign out, or run the complete uninstall (Section 6).

12. Regional Privacy Information

12.1 Where ALCHMY Is Available

During the closed beta, ALCHMY is available only to invited participants who live in a country we have reviewed. Today that is the United States. Your country of residence is the one you declare when you accept these documents; if it changes, tell us. ALCHMY’s service refuses AI features for an account whose declared residence is not in a listed country, and we do not currently offer ALCHMY to residents of the European Union, European Economic Area, United Kingdom, or Switzerland. If we make ALCHMY available in additional countries, we will update this policy and, where required, add the disclosures and safeguards those countries require.

12.2 United States and California

Residents of certain U.S. states may have privacy rights under applicable state law. California law, for businesses to which its requirements apply, may provide rights concerning access, correction, deletion, disclosure, sale or sharing of personal information, use of sensitive personal information, and non-discrimination. The applicability of a particular state privacy law depends on statutory thresholds; nothing in this policy claims that a law applies to Electropreneurs LLC when it does not. Where a law applies to us, we will honor the rights it requires. ALCHMY does not sell personal information or share it for cross-context behavioral advertising.

12.3 Other Regions

If ALCHMY becomes available where the GDPR, UK GDPR, or another privacy law applies to our processing, we will process personal information in accordance with that law, including providing applicable rights, establishing an appropriate legal basis, and putting appropriate transfer safeguards in place before processing begins.

13. International Data Processing

ALCHMY is operated by Electropreneurs LLC in the United States and relies on service providers that process information in the United States. Cloudflare’s network also answers download and update requests from data centers worldwide. Your personal information is therefore processed in the United States. Where applicable law requires safeguards for an international transfer of personal information, we will use an appropriate transfer mechanism or other legally permitted basis.

14. Security

We use technical and organizational measures designed to protect information processed through ALCHMY. Current controls include: sign-in through our authentication provider with short-lived access tokens; entitlement checks on every request; AI-provider credentials held only on our servers, never in the application; a gateway built and tested so that request content is not written to logs or databases; database access that is denied by default; local files on your Mac readable only by your macOS user; signed and notarized software with signed, verified updates; and restricted access to production systems.

No system is completely secure, and we cannot guarantee that information will never be accessed, disclosed, altered, lost, or destroyed despite our safeguards. If we identify a privacy or security incident affecting you, we will investigate and respond according to our incident procedures and applicable legal requirements.

15. Website Analytics, Cookies, and Browser Technologies

The ALCHMY website includes no third-party analytics, advertising, session-replay, or tracking scripts. It uses only the browser technologies necessary for functionality, security, authentication, and session management. Our hosting provider processes technical request information, such as IP addresses and request metadata, as part of providing its service.

If we introduce analytics, advertising technologies, or non-essential cookies that materially change these practices, we will update this policy and provide consent or opt-out controls where required.

16. Marketing Communications

If you join the waitlist or otherwise ask to receive information from us, we may send communications about ALCHMY, beta availability, launches, or related product information where permitted by applicable law. Today these messages are sent by hand. You may ask us to stop at any time by replying “remove”, and we will. Operational messages about your account, security, beta participation, legal notices, or the Service are different from marketing messages and may still be sent where necessary.

17. Children

ALCHMY is intended for adults. You must be at least 18 years old to create an account or participate in the ALCHMY beta. We do not knowingly offer the Service to anyone under 18. If you believe a person under 18 has provided us with personal information in connection with an ALCHMY account or beta participation, please contact us.

18. Contact Us

Questions or requests concerning this Privacy Policy or our processing of personal information may be sent to:

Electropreneurs LLC
4460 Bermuda Dunes Place
Oceanside, CA 92057
United States

Email: support@alchmy.io

This address receives support requests, privacy requests, and acceptance replies, and it is monitored by Electropreneurs LLC.

19. Changes to This Privacy Policy

We may update this Privacy Policy as ALCHMY evolves. When we do, we change the version number and effective date shown at the top of the published policy.

If a change materially affects how we process personal information, for example a new category of data, a new service provider, or a new retention period, we will send closed-beta participants the new version and ask them to accept it again before the change applies to them. ALCHMY’s service checks the version you accepted: until you accept the current version, ALCHMY’s AI features (typed requests, Voice, and quick commands) stop working for your account.

19.1 Changes in Version 1.1

Version 1.1 replaces version 1.0, which described an earlier design of ALCHMY and was never published or accepted by anyone. The material changes are:

  • ALCHMY makes changes to your Live Set when you ask (Sections 2 and 7.2); version 1.0 described an assistant that only advised.
  • ALCHMY does not take screenshots and does not analyze the audio coming out of Live; it reads your Live Set through AlchmyBridge (Sections 2 and 3.4).
  • Voice and the microphone, with recordings sent to OpenAI for transcription (Section 4).
  • Quick commands and the new provider TypeSafe AI, Inc. (Section 5).
  • Sample Library file names and locations, including your macOS user name, are sent with sample requests (Section 3.5).
  • The acceptance record, your declared country of residence, and the countries where ALCHMY is available (Sections 3.2, 12.1).
  • Local data: the chat database and 30-day diagnostic records replace the earlier screenshot cache and conversation store (Section 6).
  • Cloudflare for downloads and updates, and Google Workspace for the support mailbox (Section 9).
  • The current purge cadence for gateway records (Section 10.2).

Read the ALCHMY Terms of Service.