CodaKeys Privacy Policy

The CodaKeys app

The app has no advertising, analytics or tracking, and unless you turn on the reports or the update checks described below, it sends us nothing. Your projects, recordings, settings and prompts stay on your Mac, in CodaKeys' folder in your user Library. API keys you enter are kept in the macOS Keychain.

Some features connect to outside services that you choose to use. When you use one, CodaKeys sends what that feature needs straight from your Mac to the service, under your own account, and that service's privacy policy applies. We don't receive a copy.

If macOS asks to send a crash report, Apple handles it under its own policy. Apple shares crash reports with app developers only if you turned on "Share with app developers" in System Settings.

Crash, error and performance reports

CodaKeys can send us reports that help us fix problems, but only if you turn them on. It asks once, with both choices off, and you can change them at any time in Settings > Permissions.

• Crash and error reports. When CodaKeys crashes: where in its code it crashed. When it stops responding for 5 seconds while its window is on screen: where in its code it was stuck, and whether a song was playing. Each of these reports, and each error report below, also has the last 30 things you did in the app, such as opening a project or pressing Play. When something fails: what failed, such as a plug-in (its product name, maker and version), an export, a freeze, an add-on install, an update, opening or saving a project, the audio device or the Claude panel, as a category rather than the message on screen. When the audio device stalls, it also says whether the device was open and running, how long since CodaKeys opened it, how many of its inputs were open, how many dropouts it had had, and whether restarting it brought the sound back. When an update fails: the step it got to (such as setting up, checking, downloading, unpacking or installing), the updater's error number and the kind and number of the error under it (such as a network time-out), whether you asked for the check, and the version it was getting. When a project won't open or save: how (such as Open Recent or an autosave), why, as a category (such as a file that isn't a CodaKeys project), the project format's number in the file and the one this CodaKeys reads, whether its folder is on this Mac, an external or network drive or iCloud Drive, whether that drive is nearly full, and whether CodaKeys can write there, never the project's name or where it is. When the audio device won't open: the kind of error (such as the device is gone), whether CodaKeys had a saved device setup to restore, and whether CodaKeys may use the microphone. When an add-on install fails, however it started (in Studio Setup, the quick setup, the Claude panel's Install or Update buttons, or by Claude): which add-on, and the step or check that stopped it, as a category (such as the download, its checksum or signature, Homebrew, your password, macOS's installer, no internet connection, or running out of time), never the installer's output. When the Claude panel can't find or start Claude Code: where it was found, as a category such as Homebrew, never the folder; how it was installed, its version and whether it is older than CodaKeys needs; whether looking it up through your shell found it, did not, timed out or failed; your shell's type (such as zsh or bash); and the error or exit number. Every report lists the program files CodaKeys has loaded (its own, macOS's, and any plug-in running inside it) with their build IDs, which turn code addresses into names. An error or not-responding report names each file alone; a crash report also has the folder it is installed in, which can include your Mac's account name, and we have set Sentry to remove that name.
• Performance data. How long opening a project, exporting, rendering and each of Claude's tools take, and how often the audio dropped out while a song played.
• With every report. Your CodaKeys and macOS versions, your Mac's model and memory, your audio sample rate, buffer size and device type (built-in, USB, Bluetooth or other, never its name), and a random install ID made when you said yes. Your email address too, only if you typed it in, so we can reply.

Reports never include your audio, MIDI or notes; the names of your projects, tracks, files or folders; lyrics; anything from your Claude conversation or prompts; API keys; device names; or CodaKeys' settings and logs. The app's "What CodaKeys sends" page lists every field.

Reports go to Sentry (Functional Software, Inc.), the service we use to read them, which keeps them for 30 days. Sentry sees your IP address when a report arrives, as any internet service does; we have set it not to store it.

Turning a switch off stops those reports from then on. To have the reports from your Mac deleted, write to hello@codakeys.com with the install ID shown in Settings > Permissions. After you turn both switches off, it stays shown there until you quit CodaKeys.

The website

• Email sign-up. If you sign up for updates, we keep your email address with Resend, our email provider, and use it only to send CodaKeys news and release notes. Every email has an unsubscribe link.
• Beta requests. If you ask to join the beta, your email address is emailed to our inbox (forwarded by ImprovMX to the developer's Gmail) so we can approve it, and the invite we send you through Resend carries a download link made for you. We use that address only for the beta.
• Analytics. We use Vercel Web Analytics to count page views. It sets no cookies and reports only totals, such as pages viewed, referring sites, country and device type.
• Hosting. The site runs on Vercel, which keeps standard server logs, including IP addresses, to run and protect the service.
• Downloads. The CodaKeys download is served by GitHub, which sees your IP address like any other download.

We don't use advertising cookies, we don't run ads, and we don't sell or share personal information.

Your choices

You can unsubscribe from our emails at any time. To see, correct or delete the email address we hold, write to hello@codakeys.com and we'll act on it within 30 days. We honor these requests for everyone, wherever you live, including rights under California and other state privacy laws.

Children

CodaKeys and this website are not meant for children under 13, and we don't knowingly collect their information. If you think a child has signed up, tell us and we'll delete it.

How long we keep it

We keep your email address until you unsubscribe or ask us to delete it, and a beta request until you ask us to delete it. Sentry keeps reports for 30 days.

Security

We use reputable providers and protect access to our accounts with two-factor sign-in. No service is perfectly secure, but we keep what we hold to the minimum above.

Changes

If this policy changes, we'll post the new version here with a new effective date, and tell people who signed up if the change is significant.

Contact

Bostick Technologies and Art LLC, New York, NY · hello@codakeys.com