Privacy policy

This policy explains how AudioNode handles personal information for the website, your account, the sample library, and Fletcher Audio plugin purchases, giveaway claims and licensing. The Terms of use cover website and sample use; each plugin also has its own product EULA. Accepting an EULA does not opt you into optional marketing or optional analytics.

1. Who is responsible

audionode runs this site and decides how personal information is used. If you have a privacy question, write to hello@audionode.io.

2. Information we collect

We collect what we need to run the library:

• Account details you give us, such as name, email, password, country, and profile photo
• Google account details if you sign in with Google, including the email Google shares with us
• Download history, credit balance, and which samples or packs you used
• Packs, covers, and files you upload, plus the name and email we show as the creator
• Technical logs such as IP address, browser, and basic device information
• How you use the site, including plays and downloads, when analytics is on
• Plugin order and payment records, including the product, account and checkout email, order/payment references, amounts, currency, tax, payment/refund/dispute status and receipt links returned by the payment service.
• Plugin giveaway claims and their campaign, plus the entitlement and licence records used to provide access to your plugin.
• Plugin licence activity, including the licence reference, product, derived device identifier, computer name, activation and renewal times, authorisation expiry, deactivation and licence-status changes. The device identifier is pseudonymous, not anonymous; it can be associated with your account and licences.
• Recorded plugin download requests, including the product, platform, file format, release version, access source and time. These record issuance of a download link; they do not prove a completed transfer or installation.
• Product agreement acceptance records: agreement version and document checksum, account, purchase/claim/download context and time, plus separate immediate-access and cancellation acknowledgements where given for a purchase.

Plugin purchases use Stripe Checkout and its managed payment services. We provide checkout with your account email, product and order references and receive payment, refund, dispute and receipt information to fulfil and support your purchase. Payment details are entered with the payment provider, not into AudioNode's own card-entry form. The checkout provider's privacy notice explains its own processing. Do not send payment card details or a complete licence key in a support message.

Stripe privacy policy

3. Why we use it

We use this information to:

• create and keep your account, including login links and password resets
• let you preview, download, and organise sounds
• count credits and stop abuse
• process uploads and show packs in the library
• send mail you asked for, such as a magic link or a security notice
• understand how the site is used so we can keep it working and improve it
• meet the law, and protect the service and other people

We do not sell your personal information. We do not rent email lists.

We use plugin account, order and claim records to fulfil purchases and giveaway claims, provide download and receipt access, recover licences and respond to support requests. We use licence/device records to issue and renew authorisations, enforce the computer allowance, let you manage devices and investigate misuse or an access error. Authorised administrators can review relevant records and licence-management events for those purposes. A licence check-in measures an activation or renewal request; it is not a record of how long you listened or worked in a DAW.

Plugin activation and local storage

During explicit activation, the plugin sends your key, product identifier, derived device identifier and a shortened computer name to AudioNode over HTTPS. Renewal sends the signed device authorisation instead of the reusable key. The service also receives normal connection information such as your IP address. The computer name can contain personal information. Licensing requests do not send audio, project contents or parameter settings, and the platform's raw device identifier is not included in the licensing request.

The plugin keeps its signed device authorisation and validation timestamps locally for offline use and renewal. The shared licensing client does not save the reusable activation key in its cache, an operating-system key vault or DAW project state. A licence file that you choose to download does contain your key, so keep that file private. You can recover the same key/file from your signed-in account. Deactivating a computer or letting its authorisation expire does not by itself erase the account's licensing history.

Automatic update checks request public release information for your platform. They do not send the licence key, device identifier, audio or project contents; the service receives normal connection information. You can switch automatic update checks off using the plugin's update controls. Turning off update checks does not turn off the separate licence-renewal process.

The current licensing and download records do not report successful installer completion or uninstallation. They are not used to infer that a requested installer was run or that a plugin was removed. An account and the required licence/device information are needed for online activation and renewal; withholding or deleting information needed to validate the licence can prevent those functions. Contact support to discuss an access or privacy request.

4. Cookies and similar tools

We use a small number of cookies and similar storage:

• A session cookie so we know you are logged in
• A short-lived cookie during Google sign-in
• A cookie if you dismiss a site banner
• Local settings in your browser for theme and sidebar, which stay on your device

If Google Analytics is enabled, Google may set its own cookies to measure traffic. You can block cookies in your browser. The site may not stay logged in without the session cookie.

5. Analytics

We may use Google Analytics 4 to see page views and events such as plays, downloads, and uploads. Google processes that data under its own terms. We use it in aggregate to learn what is working, not to build a public profile of you.

Nodium beta advertising measurement

On the Nodium beta page (audionode.io/beta/nodium) we use the Meta Pixel, but only if you accept advertising cookies in the popup. It tells Meta that you visited the page and, if you apply, that an application was sent, so we can see which Facebook and Instagram ads work. Meta also receives the technical details any website request carries, such as your IP address, browser and device. We do not send your name, email address, DAW, computer or anything you type in the form, and the Pixel's automatic event collection is turned off.

Rejecting has no effect on your application. Your choice is stored in your browser for six months; change it at any time with Cookie settings at the bottom of the Nodium beta page. If you accept, Meta may set its _fbp and _fbc cookies. If you later reject, we stop sending events and delete those cookies from your browser, but information Meta already received stays with Meta and is handled under Meta's own privacy policy.

Meta privacy policy

6. Who we share it with

We share personal information with companies that help us run audionode, and only as much as they need:

• hosting and database providers that store the site, account, plugin entitlement and licensing records
• payment and checkout services for plugin payments, receipts, tax handling, refunds and disputes
• private file-storage and email-delivery providers supporting plugin documentation, downloads and transactional messages
• object storage for sample files, previews, covers, and profile photos
• email delivery for login links, password mail, and similar notices
• Google, if you choose Google sign-in or if analytics is on

We may also share information if the law requires it, or if we need to protect audionode, our users, or the public. If the project is sold or merged, account data may move with it under this policy or a replacement we will point you to.

7. How long we keep it

We keep account data while your account is open. Download history stays so you can see what you took and so we can run the library. Uploaded packs stay until they are removed. Logs are kept for a limited time unless we need them for security. Mail we send is not stored as a permanent inbox on audionode.

8. Your choices

You can change your name, country, profile photo, password, and connected Google account in Settings. You can ask us for a copy of the personal information we hold, or ask us to correct it. You can ask us to close your account. We may keep a minimal record if we must, for example to prevent abuse or to finish a legal duty.

There is no in-product delete button yet. Email hello@audionode.io and we will help.

You can manage activated computers and recover personal licence files in My licences. You can request access to or correction of your personal information, and ask about deletion, restriction, objection or portability where those rights apply, by contacting hello@audionode.io. Deactivation is a licence-management action, not a request to erase all associated records. You can also raise a data-protection concern with the UK Information Commissioner's Office at ico.org.uk, or another competent authority where applicable. Accepting a product EULA does not prevent you from exercising your data-protection rights.

9. Children

audionode is not aimed at children under 16. Do not create an account for someone that young. If we learn we have collected information from a child, we will delete it.

10. Where data lives

We use cloud providers that may store and process data in more than one country. If you use audionode from the UK or the EEA, that can mean a transfer outside those regions, with the safeguards those providers offer.

11. Changes

We may update this policy. The date at the top is the latest version. If a change is material, we will try to tell you on the site or by email.