Privacy policy

Last updated 15 November 2026.

In short

  • Newsounds does not sell your personal data and does not use it for advertising.
  • No advertising or tracking cookies are set. The only cookies keep you signed in.
  • Projects you back up to the server are stored there as they are. They are not end-to-end encrypted.
  • Cloudflare hosts the service and Resend sends its emails. Google and Apple handle sign-in if you choose them.
  • You can delete any project in the app. To delete your account, write to privacy@newsounds.cc.

What this covers

This policy covers newsounds.cc, the app at daw.newsounds.cc, and the Newsounds apps for iOS and desktop, which sign in to the same server. It says what is collected about you, why, who else handles it, how long it is kept, and what you can do about it.

Who is responsible

Newsounds is run by one person, who decides what personal data is collected and why. That person is the controller of your data under the GDPR and the UK GDPR, and can be reached at privacy@newsounds.cc.

Visiting the site

Cloudflare serves these pages and sees the details of each request, such as your IP address and browser, as any web host does. Cloudflare also keeps logs of requests to the Newsounds server for a limited time. They record the page asked for, the result, and any error the server reports.

The front page, the sign-in page, and the app also use Cloudflare Web Analytics. It counts visits without setting a cookie or storing anything on your device, and records the page, where you came from, your country, how fast the page loaded, and your browser, operating system, and device type. This page does not use it.

Some requests, among them access requests, sign-in codes, and browser-check reports, are limited in how often one network can send them. The limit uses your IP address as a counter key in Cloudflare's rate limiter and, for sign-in codes, the address the code goes to as well. Neither is written to Newsounds's database.

The basis is Newsounds's legitimate interest in knowing whether the site works and who it reaches.

Asking for access

On the front page you can ask for access with your email address. That makes an account for the address, which waits for an administrator to let it in. The account holds the address, which is also its name, and the time you asked. Nobody can sign in to it until someone signs in with that address, which makes the account theirs.

The first time an address asks, it gets one thank-you email, sent through Resend and answered at support@newsounds.cc. Asking again sends nothing more. The address is used later to write to you when you are let in. Nothing else is sent to it.

The form is protected by Cloudflare Turnstile, which tells people from automated bots. Your browser loads its script and a small frame from challenges.cloudflare.com, and Cloudflare checks signals from your browser there; it may keep a little state in your browser's storage for that frame. The form gives Newsounds a token, and Newsounds sends the token and your IP address to Cloudflare to check it. Neither is stored by Newsounds. Cloudflare processes these on Newsounds's behalf.

The basis is your request, a step you asked for before having an account, and Newsounds's legitimate interest in keeping the form free of abuse.

The account is kept like any other until it is deleted, which you can ask for at any time; see Deleting your data below.

Your account

An account stores your email address and a name. If you sign in with Google or Apple it also stores the name they send, the identifier they give you, the tokens they issue, and, from Google, the address of your profile picture. An account made with an emailed code is named by its address.

Each account also has a status that says whether it has been let in and, where an administrator has set one, a storage limit. Administrators see every account's name, address, and status, and are told in the app when a new account is made. When an administrator lets an account in, its address is sent an email saying so.

If you sign in with an emailed code, Resend delivers the mail. The code stays valid for ten minutes, three wrong guesses cancel it, and only a hash of it is stored, never the code. There are no passwords.

Google and Apple tell Newsounds who you are when you choose them, and learn that you signed in to Newsounds. What they do with that is set by their own privacy policies.

Each device you sign in on gets a session: a record of its IP address, its browser's user agent text, and when it was made, with a cookie or token that points to it. A session lasts seven days and renews while you use it. Signing out removes the record. One that runs out unused is not removed on a timer and stays until the account is deleted.

The basis is the contract you enter by using Newsounds, which cannot work without an account. Keeping the IP address and user agent with a session is Newsounds's legitimate interest in security.

The account is kept until it is deleted. To have it deleted, see Deleting your data below.

Your projects and audio

Projects are stored on your device, in your browser's storage or the app's. Nothing in it reaches Newsounds unless you are signed in, and Newsounds cannot delete what is only on your device.

While you are signed in, projects are also backed up to the Newsounds server. That stores each project's document, saved versions, edit history, and the audio you recorded or imported with its file names, lengths, and sample rates. It also stores who the project is shared with and the links that open it.

To record, Newsounds asks your browser or device for microphone access. What you record is project audio and is handled like the rest of the project.

People you share a project with can see its contents and one another's names, and the owner also sees their email addresses. While a project is open, they also see where your cursor is, what you have selected, and whether you are in its voice chat.

A share link opens the project for anyone who holds it. The link is stored in readable form so its owner can copy it again, and stops working when it is revoked.

Inviting someone by email address stores that address, in lower case, with the role offered. It is kept until the person signs in with that address and the invite becomes membership, the owner cancels it, or the project is deleted.

Projects are not end-to-end encrypted. The server, and so the person who runs Newsounds, can technically read them. Connections to the server use HTTPS.

This is stored with Cloudflare, in its Durable Objects, R2, and D1 services. Newsounds does not choose a region, so Cloudflare does.

The basis is the contract: storing and syncing your work is the service.

Everything is kept until you delete it. Deleting a project deletes its document, saved versions, edit history, and the audio no other project of yours uses, and ends its links, invites, and memberships.

After a project is deleted, Newsounds keeps only a record of its ID and when it was deleted, so that an old copy cannot bring it back. The record holds no name or content.

Profile and settings

You can add a short bio and a picture to your account. Other people using Newsounds cannot see them. Removing the picture deletes its file, and saving a new bio replaces the old one.

Settings that follow you between browsers, such as your theme, key bindings, and the name collaborators see beside your cursor, are stored with your account, each with the time it was changed.

Some plugins sign you in to another service and keep a token in the plugin's page. For plugins set up that way, Newsounds stores the token with your account, encrypted, so you stay signed in on your other devices. You can remove a plugin's saved sign-in in the app.

Plugins that sign you in to another service run in a page of their own at plugins.daw.newsounds.cc. That service receives what the plugin sends it, your IP address included, and has its own privacy policy.

The basis is the contract: these are features of your account.

They are kept until you remove them or the account is deleted.

Bug reports and browser checks

Report a bug, in the Help menu, sends a report only when you press send. It holds your description, the project's state (which can include track and file names), your recent actions, diagnostics, browser or device details, and, if you add one, a screenshot. Audio files are never uploaded with it. The report is stored with your account ID.

The browser check at daw.newsounds.cc/check sends its report only when you press Send report. It holds your browser's user agent text and the results of the checks, and is linked to your account only if you were signed in.

Administrators read reports to find and fix problems, and for nothing else.

The basis is your consent, which you give by sending a report and can withdraw by asking for it to be deleted.

Reports are kept until an administrator deletes them or the account they are linked to is deleted. Nothing deletes them on a timer.

The iOS beta

From the Help menu, a signed-in account can ask for an invite to the iOS beta. That stores the account's email address, the time, and where the request stands. Our server then sends the address to Apple's App Store Connect to invite it to TestFlight (an administrator does so by hand when that fails), so Apple receives the address and handles it under its own privacy policy. The request is kept until an administrator deletes it.

The basis is your request.

Voice chat and remote control

Voice chat connects the people in a project directly to one another. Audio goes from browser to browser, and Newsounds does not receive or record it: its server only passes on the messages that set the connections up. Those messages carry network addresses, so the others in the chat can see your IP address. A signed-in account is also given Cloudflare's connection servers, which see your IP address and, when no direct path exists, relay the audio.

Remote control lets your browser operate the Newsounds desktop app on another of your machines. While that machine is connected, its name and the project it has open are held so that your other devices can find it. The connection runs directly between the two, or through Cloudflare's relay.

The basis is the contract: these are features you choose to use.

Cookies and storage on your device

Signing in sets a session cookie. It is needed to keep you signed in, is hidden from page scripts, and is sent only over HTTPS and only to Newsounds. Signing in with Google or Apple also sets a short-lived cookie while you are away at the provider, to check that you come back to the sign-in you started.

The app keeps your projects and settings in your browser's storage, and the apps keep your sign-in token there too. That stays on your device, apart from what the features above sync to the server.

Newsounds sets no advertising or tracking cookies.

Who else handles your data

Cloudflare hosts the service and stores everything described above. It also provides Web Analytics, Turnstile, the rate limiter, and the connection and relay servers for voice chat and remote control. It acts for Newsounds as a processor.

Resend sends the sign-in codes, the thank-you email, and the email saying an account has been let in. It receives the address and the message, and acts for Newsounds as a processor.

Google and Apple provide sign-in if you choose them. Each is a controller of its own for your account with it.

Plugin services, such as TONE3000, get what you send them when you use their plugin. They are not processors for Newsounds.

Newsounds does not sell personal data or give it to advertisers or data brokers. It discloses data only where the law requires it.

Data leaving your country

Cloudflare and Resend are US companies, and Cloudflare handles data in many countries. If you are in the UK or the European Economic Area, your data is therefore transferred to the US and elsewhere. These transfers rely on the safeguards the providers offer: the EU-US Data Privacy Framework, or the standard contractual clauses in their data processing terms, with the UK addendum for UK users.

Your rights

Wherever you live, you can ask what Newsounds holds about you, ask for it to be corrected, and ask for it to be deleted.

If the GDPR or UK GDPR applies to you, you can also ask for a copy of your data in a usable form, ask for its use to be restricted, object to any use based on Newsounds's legitimate interest, and withdraw consent where consent is the basis. Withdrawing consent does not undo what was done before.

If you live in California or another US state with a privacy law, you have the right to know what is collected about you, to have it deleted or corrected, and to opt out of the sale or sharing of your data. Newsounds does not sell or share personal data for advertising, so there is nothing to opt out of. You will not be treated differently for using these rights.

To use any of these, write to privacy@newsounds.cc from the email address on your account, so the request can be matched to you. You will get an answer within one month.

In the app you can already delete a project, remove your picture, remove a plugin's saved sign-in, sign out, and export your projects and mixes.

If you think your data has been mishandled you can complain to your data protection authority: in the UK, the Information Commissioner's Office, and in the EU, the authority of your country. You do not have to write to Newsounds first.

Deleting your data

There is no delete-account button yet. To delete your account, write to privacy@newsounds.cc from its email address. That removes the account with its sign-ins and sessions, synced settings, saved plugin sign-ins, profile, bug reports and browser check reports, your place in shared projects, and the projects you own with their audio.

An address in an iOS beta request is not part of an account. Write in the same way and it is deleted too.

Data deleted from Cloudflare's database can stay in its restore history for up to 30 days before it ages out.

Emails already sent cannot be recalled. Resend keeps its own log of the mail it has sent, under its own policy.

Children

Newsounds is not for children under 13. If you think a child has an account, write to privacy@newsounds.cc and it will be deleted.

Changes

A change to this policy is posted on this page with a new date at the top.

Contact

For a question about this policy, or to use any right above, write to the person who runs Newsounds:

privacy@newsounds.cc