Privacy
What we hold, and what we don't.
This page lists every piece of data KODA keeps, why we keep it, and how to get rid of it. It describes what is actually built, nothing more. When we ship something that changes what we collect, this page changes with it.
Last updated 30 August 2026 · Koda Sampler, Inc.
The short version
- We keep what your account needs to work: your email, your licenses, and the machines you've activated them on.
- Our servers count things like downloads and activations. The counts hold no IP addresses, and after 90 days only id-free daily totals survive.
- The KODA apps send light diagnostics: version, OS, and whether installs succeed. If the engine crashes, the Manager sends the crash file. Each has its own switch. The engine inside your DAW makes no network connections at all.
- We don't sell data. There are no ads and no third-party analytics anywhere.
- Email support@kodasampler.com and we'll show you what we hold, correct it, or delete it.
01 · Who we are
Who we are
KODA is made by Koda Sampler, Inc., a United States company: 1119 N Las Palmas Ave, Los Angeles, CA 90038, USA. We are the company responsible for your data across every KODA property: this site, the account dashboard, the vendor portal, and the desktop apps. For anything on this page, write to support@kodasampler.com.
Two companion documents cover the rest of the relationship: the Terms of Service for the websites and your account, and the EULA for the software itself.
02 · Your account
What an account stores
When you create a KODA account we store your email address, a display name if you set one, and an avatar if you upload one. Sign-in runs on Supabase, our account provider, which holds your credentials in hashed form. We also record which access groups your account belongs to, such as early access, because that decides which products you can see and download.
03 · Licensing and activation
Licenses and your machines
Licenses are managed by Keygen, our licensing provider, and the license terms themselves live in the EULA. When you activate a product on a machine, Keygen stores a record of that machine: its name, its platform, and a device fingerprint, a one-way hash built from the machine's hostname, operating system and processor architecture plus a random per-install identifier. That record is what makes seats work, and it's what lets you free a seat up later from your account dashboard or the KODA Product Manager.
A device's name is usually its hostname, and hostnames often contain a person's name ("Alex's MacBook Pro"). If you'd rather not share that, rename your computer before activating.
Keygen's servers see the IP address of activation calls the way any web server does. We do not copy machine records or IP addresses into our own analytics.
04 · Server counts
What our servers count
Our servers keep operational counts: when a license activates or renews and whether it succeeded, when a download runs and how many bytes it moved, and which country a request came from, read from the request itself. These exist so we can answer questions like "did the last update break activations" and "how many installs are alive this week".
Raw counts are tied to your customer id where the server knows it, or to nothing at all. They never contain your IP address, and they expire after 90 days. What survives past 90 days is arithmetic: daily totals with every id dropped.
05 · Feedback and support
Bug reports and feedback
Reports from the Feedback tab in your account dashboard go into our issue tracker, ClickUp, so they actually get fixed. New reports are labeled with your customer id, not your email address. Our team looks the id up when we need to reply. Whatever you write in a report travels with it, so leave out anything you wouldn't put in a bug tracker.
We also keep a copy of each report in our own database, labeled the same way. It means the record of what you told us does not live only with a third party. Ask us to remove a report and we delete both copies.
06 · Email
When we email you
Account email, such as confirmation and password-reset messages, comes from our sign-in provider. Messages you send through the contact form reach us through Resend, an email relay. If you joined the mailing list, that address lives in MailerLite. You put it there yourself, either through the form on this site or by ticking the newsletter box when you created your account, and every mail has an unsubscribe link. Creating an account on its own does not put you on the list. You can turn the newsletter on or off at any time under Settings in your account. We don't buy lists and we don't share ours. If you write to us, we keep the correspondence so we can actually help.
07 · The apps
What the apps on your computer send
The KODA Product Manager and the KODA Packager talk to our servers to do their jobs: signing in, activating and renewing licenses, reading the releases feed, downloading products. The one background job, the license renewer, keeps your activation certificates fresh once a day. It is described in the Manager and you can turn it off in Settings.
Since Manager 0.12 and Packager 0.5.3, the apps also send app diagnostics: which version they are, what OS they run on, and, in the Manager, whether an install or update succeeded or failed (a coarse failure category, never the error text, never a file name). Diagnostics are labeled with a random id you can see in the app's settings; it has no link to your account. This is on by default. The switch to turn it off lives under Diagnostics and usage, and turning it off also discards anything queued but not yet sent. Diagnostics only leave the machine when the app was already talking to us: at launch, on Refresh, and after the daily renewal. Never on a timer.
The KODA engine, the part that loads inside your DAW, makes no network connections at all, for any reason. That is a design rule, not a setting. When it crashes, it writes a file to disk and nothing more. The Manager is what carries that file, described next.
Since engine 1.0.4 and Manager 0.13.1, crash reporting is live. If the engine crashes, it writes a small crash file into its own folder on your machine. On Windows that is a minidump: the call stacks of the DAW's threads plus a list of the modules loaded at the time, and not a copy of the program's memory. On macOS it is a list of raw stack addresses plus the loaded-module list, by file name only. Beside it sits a context note the engine keeps while it runs: engine version, OS version, the DAW's name and version, sample rate and buffer size, which KODA products were loaded, and when the session started. The next time the Manager talks to us anyway, at launch, on Refresh, or after the daily renewal, it sends the set and deletes it from your machine once we confirm we have it. Crash files are labeled with the same random diagnostics id as app diagnostics, so they have no link to your account.
Two things you should know. The module list names every plugin loaded in that DAW session, not only ours, and on Windows it lists them by path, which usually includes your Windows username. We say so rather than pretend otherwise. And if a session ends without a clean shutdown but no crash file was written, the Manager sends the context note alone, counted as an abnormal end rather than a crash, so our crash figures stay honest.
The Crash reports switch under Diagnostics and usage in the Manager controls all of this. It is on by default. Turned off, crash files stay on your machine, untouched apart from a cap of ten, and you can still attach one to a bug report yourself. On our side, crash files land in Cloudflare storage and are forwarded to Sentry, which turns the raw addresses back into lines of code. Each distinct crash becomes one item in our bug tracker, carrying the engine version and a link to Sentry, never the file itself.
Any further diagnostics will be described here before they ship, each with its own switch.
08 · The line
What we never collect
This list is copied from our engineering spec, where it is binding. A feature that wants an item on this list doesn't get built.
- Your audio, or anything rendered from it
- MIDI, notes, or anything you play
- Project or session names
- File names or paths from your machine
- Keystrokes or screen contents
- Your IP address, in any KODA store
- Precise location. A request’s country is as close as we look
- Full-memory dumps
- An inventory of other plugins you own
- Advertising or cross-site identifiers
One exception, spelled out in section 07: a crash file lists every module that was loaded in the DAW when it crashed, other plugins included, and on Windows it lists them by path. It exists only if the engine crashes, and only leaves your machine with the Crash reports switch on.
10 · The community forum
The community forum
Signing into the community forum uses the same account as everywhere else: you sign in once, here, and the forum recognizes you by your customer id, your email address, and your display name if you set one. It never sees your password. The forum runs on Elestio, our hosting provider for it. Anything you choose to post there is as visible as any forum post.
11 · Processors
Who works on our behalf
These companies process data to provide their service to us, and for nothing else. Most run in the United States, so data you give us crosses borders.
| Company | What they do for us | Where |
|---|---|---|
| Cloudflare | Runs our servers, file delivery, the operational counts described above, and the store that holds crash files | United States, global network |
| Supabase | The account database and sign-in | United States (us-east-1) |
| Keygen | Licensing and activation | United States |
| Vercel | Hosts this website, the account dashboard, and the vendor portal | United States |
| ClickUp | Bug and feedback triage, including one item per distinct engine crash | United States |
| Sentry | Error monitoring for our servers, and reading engine crash files | United States |
| Resend | Delivers contact-form messages to us | United States |
| MailerLite | The mailing list, if you joined it | European Union |
| Elestio | Hosts the community forum | United States |
Where data leaves the EEA or the UK, the transfer rests on safeguards such as Standard Contractual Clauses, as implemented by these providers. We may also disclose data if the law requires it, or as part of a merger, acquisition, or sale of assets; this policy follows the data if that ever happens.
12 · Retention
How long we keep things
| Data | How long |
|---|---|
| Account data | For as long as your account exists |
| Raw server counts and app diagnostics | 90 days, then deleted |
| Daily totals derived from them | Kept. They carry no ids at all |
| Server error reports | 90 days |
| Engine crash files and their context notes | 90 days, then deleted. A one-line summary (engine version, OS, DAW, diagnostics id) stays in our reports database |
| The change ledger (grants, revokes, admin actions) | Kept, as the history of accounts and licenses |
| Feedback reports (our database and our tracker) | Until you ask us to remove yours |
| Mailing list address | Until you unsubscribe |
13 · Your rights
Your rights
Email support@kodasampler.com from your account address and we will show you what we hold on you, correct it, or delete it. We aim to complete requests within 30 days.
Deleting your account removes your personal details from our stores. The record that a license was granted survives without them, because license history is a contract record. If you're in the EU or the UK, these are your GDPR rights. We answer them the same way for everyone, everywhere, and we never treat you differently for using them.
For the formally minded: where GDPR applies, we process data to perform our contract with you (accounts, licenses, delivery), with your consent (the mailing list), under our legitimate interest in keeping the service secure and working, and to meet legal obligations. We do not sell or share personal data as the CCPA defines those terms. You can complain to your local supervisory authority, though we'd rather you email us first so we can just fix it.
14 · Children
Children
KODA isn't directed at children under 16 and we don't knowingly hold their data. If you believe a child has given us personal data, email us and we'll delete it.
15 · Changes
Changes to this page
We update this page whenever a shipped feature changes what we collect, and every revision is dated here.
- 30 August 2026Crash reporting is live (engine 1.0.4, Manager 0.13.1). The apps section now says what a crash file holds, where it goes, and what the Crash reports switch does; the never list gains its one exception, the module list; crash files added to retention and to the Cloudflare, Sentry and ClickUp rows.
- 24 August 2026Added the community forum, hosted for us by Elestio and signed into with your existing KODA account.
- 23 August 2026The signup form now offers the newsletter as an optional tick box. It is off unless you tick it, and creating an account never subscribes you on its own.
- 18 August 2026Feedback reports are now also stored in our own database, not only in ClickUp. Removal on request covers both copies.
- 17 August 2026App diagnostics added: Manager 0.12 and Packager 0.5.3 send version, OS and install outcomes, each with an off switch under Diagnostics and usage.
- 17 August 2026First published.