Privacy policy

This policy explains what personal information audionode collects, why we have it, and what we do with it. It applies to the website at audionode.io. Our Terms of use cover the sample licence. Read both.

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

We do not ask for payment card numbers on audionode itself. If that changes, the provider who takes the payment will have its own terms.

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.

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.

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 and account records
• 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.

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.