Privacy Policy

Who we are

Remove Audio (remove-audio.com) is operated by Code Master BV (VAT BE 1012.022.972), Belgium. We are the controller of the personal data described here. You can reach us at support@remove-audio.com.

Two ways the tools run

Every tool has a switch between This device and Cloud, and what we collect depends on it.

• This device: the work happens in your browser on your own computer or phone. Your file is never uploaded, no account is needed, and nothing about the file itself leaves your device.
• Cloud: you sign in, your file is uploaded over an encrypted connection to our servers, processed there and kept for the period you choose, then deleted. The Cloud is paid in credits.

What we collect on this device

Nothing from your file: no content, no name, no account link. To know whether the tools work, we record a few small usage events about the run itself.

• When a run starts, fails or is refused before it starts: which tool, whether it ran on this device or in the Cloud, the file type, the size, how many files, and for a failure its category and a rough video quality band such as 4K or 1080p. A failure also says how far the run got, the error's technical name and class and, for the AI models, the operation it stopped in, never the error's text. A failure in the Cloud also carries the job's id so we can find the failed job; the event itself is not tied to your account. These events also carry coarse facts about your browser and computer: the browser family and major version, the operating system, whether it is a phone or a computer, whether its graphics card can run our AI models, who makes it and its generation (a family shared by millions of machines, never the model), and in Chrome a rough memory figure. Never the full browser string, the graphics card model, the screen or the time zone, which together could identify a device.
• When you download a finished file: the tool, the output file type, the size and the number of files. If you are signed in, this one event carries your account id, so we can tell whether a Cloud job was delivered.
• When a file is passed from one tool to the next on the site, and when a browser tab crashed during a run, recorded on your next visit so we learn which files are too big for which devices. That crash record also says how far the run had got, how long it had run, whether the tab was in the background when it died, the size limit that admitted the file, and in Chrome whether the browser is a 32-bit or 64-bit build.
• When you click the button that asks Google to make us a preferred source: which page it was on, nothing else.
• Feedback: when you answer how a run went, your answer (bad, fine or good), and, if you choose to tell us why, the name and message you type; with it the tool, whether it ran on this device or in the Cloud, how many files finished or failed and their total size, your device type, browser and its version, the page you were on, the page you came from and your browser language. It goes to a spreadsheet at Google and is not linked to an account.
• Page analytics from Google Analytics: pages viewed, approximate region, device and browser type, aggregated.

What we collect in the Cloud

The Cloud needs an account and stores your files for as long as you ask.

• Your account: the email address, and the name and profile picture your sign-in provider holds and shows in your account menu, a user id, your plan and your credit balance.
• Your files: the file you upload and the result we produce, stored on our servers in the United States, encrypted in transit and at rest. They are deleted after the retention you pick when you start the job: 24 hours by default, 7 days, 30 days, or kept until you delete them (30 days and longer are for customers with a pack or plan). You can delete any job and its files at any time from your workspace.
• Job records: which tool ran, when, the settings you chose, the name of the file, the duration billed, the credits reserved and settled, whether the result was downloaded, and the error when a job failed. These accounting records stay after the files are gone.
• Payments: our payment provider handles your card; we never see the card number. We keep your customer id at the provider, your purchases, your subscription status and the credits they bought.
• Support: the emails you send us and what you tell us in them.

How we use it

Only to run the service you asked for and to keep it working. Running your Cloud jobs, billing and support rest on our contract with you; the usage events, the analytics and abuse detection on our legitimate interest in a tool that works; the accounting records on our legal obligations; anything else only on your consent, which you can withdraw at any time.

• Run your Cloud jobs, bill credits for them and give credits back when a job fails.
• Answer support requests and act on feedback.
• Find out which tools deliver, which fail and on which devices, from the aggregated events above.
• Detect abuse, fraud and technical problems, and meet legal obligations.
• We do not sell your data, we do not build advertising profiles, and we show no ads.

Who processes data for us

A few providers process data on our behalf, under contracts that bind them to these purposes. They are based in the United States or store data there, so your data leaves the European Economic Area, under the EU-US Data Privacy Framework where the provider is certified and otherwise under the European Commission's standard contractual clauses.

• Amazon Web Services (United States): hosting, file storage and the servers that run Cloud jobs.
• Clerk: sign-in and account management.
• Stripe: payments, credit packs and subscriptions.
• Google Analytics: aggregated page analytics.
• Google (Apps Script and Sheets): the spreadsheet that receives tool feedback.
• Your file is processed by software we run ourselves. No third-party audio service receives it.

Cookies and local storage

The cookies and browser storage we use are listed in our cookie policy. In short: site essentials, sign-in, analytics, and the cached files of the AI models that run on this device. No advertising cookies.

How long we keep it

As short as the purpose allows.

• Cloud files: the retention you chose, or until you delete the job, whichever comes first.
• Usage events: 180 days, then deleted automatically.
• Account data, job records and payment records: while your account exists, and afterwards only what accounting rules require us to keep.
• Support emails: as long as needed to help you, then archived with our mailbox.

Security

Files travel over HTTPS, are stored encrypted, and access is limited to the systems that run your job. Processing is automated: nobody looks at your files unless you ask us to help with one, or we have to investigate abuse or answer a legal request.

Your rights

Under the GDPR you can ask to see, correct, export or delete the personal data we hold about you, to restrict or object to its processing, and to withdraw consent where we rely on it. Write to support@remove-audio.com and we answer within a month. You can also complain to the Belgian Data Protection Authority or your local supervisory authority.

Children

The Cloud and accounts are for people aged 16 and over. If you believe a child has created an account, tell us and we delete it.

Changes

When this policy changes, the date at the top changes with it. A change that affects how your data is used is announced on the site before it applies.