Privacy Policy

Effective date: 2026-08-13

Audio Joiner is a tool for joining audio files into a single file. It is available as a website and as a Chrome browser extension. This policy explains what happens to your data when you use either of them. Editing and local export happen on your device by default. When your device cannot produce the result itself, the website processes the project on our server instead. We measure how the website is used with analytics that never receive your files. Infrastructure providers process technical request data, and the server-processing providers handle uploaded audio only as explained below.

How Audio Joiner works

Decoding, preview, editing, and local export take place on your device, in your browser. This remains the default mode, and files used in that mode are not uploaded to Audio Joiner servers.

When a project is larger than your device can hold, the export moves to our server automatically, so that it finishes rather than failing. The browser first passes an automated check that the request is genuine. It then uploads the selected source files directly to private storage, using short-lived signed links. The processing server receives project instructions such as track order, trim points, fades, levels, output format, file sizes, and opaque track identifiers; it does not receive the source file names. A worker creates the result and sends it back to your browser. If the server has no room at that moment, your job waits its turn before anything is uploaded, and you are shown where you are in the queue.

Uploaded source objects are deleted when processing finishes, fails, or is cancelled. The result object is deleted as soon as this browser confirms that it received the complete file; if that confirmation never arrives, it is deleted after 15 minutes. An abandoned upload or queued job is deleted 15 minutes after its last activity, and processing has a one-hour watchdog. Operational job records contain identifiers, sizes, status, timestamps, and error codes, not file names or audio-derived analytics, and are removed shortly after the job ends.

Information we collect

We do not currently require an account, and we do not ask for your name, email address, or other personal details to use the editor. In local mode we do not receive your audio. When the export runs on our server, we receive the audio and project instructions needed to perform it, solely because that is the export you asked for. An anonymous, short-lived session token keeps your job separate from other jobs. If you contact support, we receive the email address and message you send, and we use them only to respond. Usage measurement is described in the next section. If you remove the extension and answer the question on the page that opens, we receive what you wrote and, if you chose to leave one, your email address.

Problem reports

When an export fails, the editor offers a button that sends us a detailed diagnostic report about that failure. That report does not leave unless you press it. It holds technical details of the attempt: the error code and stage, the formats, sizes and durations involved, your browser and operating system, and technical messages from the audio engine. It holds no file names and no audio. If you then leave an email address so that we can reply, it is stored with that report and used only to answer you. Reports are deleted 90 days after they arrive.

Separately from that button, we receive a short technical record of the failure itself — described below.

Error monitoring

When something fails in the editor or on the page, a technical record of it is sent automatically, without any action from you: the kind of failure, the stage, the error code, the message from the audio engine, the place in our code, and your browser type. It contains no file names, no audio, none of the contents of your files, and nothing about what you do on the page. No persistent identifier is created, and nothing is stored on your device — no cookies and no other records.

These records are processed on our behalf by Sentry, including outside your country; its privacy policy is at sentry.io/privacy. It receives the IP address a request came from, which is what separates a one-off fault from one affecting many people, and is configured so that the address itself is not stored — only the country and region are derived from it.

The legal basis is our legitimate interest in keeping the product working and finding the defects that stop it working for users. We do not use this information for advertising or profiling. You have the right to object — write to us through the Contact page. If your browser sends a Global Privacy Control signal, error monitoring does not start.

Analytics

To understand how the website performs and where it lets people down, we record events about your visit: the pages you view, general browser and device information, the country your request comes from, your interface language, whether you have the Audio Joiner extension installed, and technical facts about an export you run — how many tracks it had, the combined size of the input in megabytes, the output format, how long it took, whether it ran on your device or on our server, how long it waited in a queue, whether your device was unable to produce the result at all, how you saved the finished file, and whether the export finished, was cancelled, or failed and with which error. We also record whether the rating prompt shown after a finished export was used or dismissed. These events describe the operation, never the material: file names and audio content are not collected. Where the session-recording service described below is active, we also record how you use a page: mouse movement, clicks, scrolling, and the content of the pages displayed to you.

Analytics services process this information on our behalf, and not all of them receive all of it:

• Cookieless analytics runs for every visitor. It sets no cookies, does not build a persistent identifier for you, and reports aggregated statistics only. Part of it receives only the page you are on and measurements of how quickly that page displayed and responded — none of the export details described above.
• Google Analytics uses cookies. In the European Economic Area, the United Kingdom, and Switzerland it stays switched off until you accept it in the banner shown on your first visit, and declining keeps it off. Elsewhere it is on by default.
• Yandex Metrica uses cookies and records sessions: mouse movement, clicks, scrolling, and the content of the pages displayed to you. It follows the same choice as Google Analytics — switched off in the European Economic Area, the United Kingdom, and Switzerland until you accept it in the banner, on by default elsewhere.

If your browser sends a Global Privacy Control signal, we honour it and no analytics runs.

We do not use your files, server-processing contents, or data stored locally on your device for analytics, advertising, model training, or profiling, and we do not sell personal data.

The Chrome extension

The extension lets you collect audio you find on web pages and send it to the Audio Joiner editor to be joined.

• Local page inspection. On pages where you have granted access, the extension inspects the page on your device to identify audio. It does not send page content or browsing history to Audio Joiner.
• Retrieving a chosen source. When you choose an audio source, your browser requests that file from the website hosting it, using your existing session with that website. That website handles the request under its own privacy policy. The file is then kept and processed on your device.
• No upload to Audio Joiner servers. The extension does not upload your audio to servers operated by Audio Joiner. Audio is handed from the extension to the editor inside your browser.
• Local queue. The audio you add, together with basic descriptive information about it such as file names and where it came from, is stored in your browser on your device so your queue survives until you clear it. Clearing the queue removes this data.
• No analytics inside the extension. The extension itself contains no usage analytics and reports nothing about the pages you visit. When you open the Audio Joiner website, the website can tell that the extension is installed, and that fact is part of the website analytics described above.

When you remove the extension

When you remove the extension from your browser, your browser opens a page on our website that asks one question: why you removed it. Nothing is sent from that page unless you write an answer and press the button. Closing the tab sends nothing.

If you do answer, we receive what you wrote and, if you chose to leave one, an email address so that we can reply. We ask for nothing else: the page has no account, no sign-in, and no verification step. What you write is used to decide what to fix and what to build next, and an address you leave is used only to answer you. Answers are deleted 90 days after they arrive.

The legal basis is our legitimate interest in understanding why people stop using the product. You are under no obligation to answer, and you can object, or ask us to delete an answer you sent, through the Contact page.

Data stored on your device

The website stores a small amount of data in your browser to remember preferences such as your interface language and analytics choice. Once your files have finished uploading for a server export, your browser also stores that job’s identifier and the anonymous session token, so that you can close the tab and collect the result later; both are removed when you receive the result, and the stored record expires on its own. If you ask to be notified when your result is ready, the notification is shown by your browser, and only while the page is not in front of you; we do not send it, and you can withdraw the permission at any time. The extension stores your audio queue and short-lived technical data needed to hand audio to the editor. Except for information sent through server processing, this browser data stays on your device and can be removed by clearing the relevant browser data.

The website also keeps the project you are working on in your browser: the audio files you added, the waveforms built from them, and the edits you made, such as track order, trim points, fades, levels, and crossfades. That is what lets a project survive a page reload. It stays on your device, is kept for up to seven days, and is removed when you clear the project or when you clear your browser data.

Cookies and infrastructure services

The website uses no cookies for accounts or advertising. Analytics cookies are set by Google Analytics and Yandex Metrica only, and only where they are active as described above. The website and the assets it needs to run are delivered from domains operated by Audio Joiner. It also loads the analytics scripts described above from their providers’ own domains. When an export runs on our server, it loads an automated verification check and communicates with our own service domains.

We use a hosting and security provider for delivery, request verification, and protection. It processes technical request data such as your IP address, browser information, request time, referrer, and network or security error data, and may use cookies that are strictly necessary for security. Server processing and temporary storage run on infrastructure located in Germany. Files are encrypted in transit with HTTPS, kept in private storage, and reachable only through short-lived signed links. We do not use this information for advertising.

When the extension retrieves a file from another website, that website receives the request and handles it under its own privacy policy.

Data sharing

We do not sell your audio files or share them for advertising. For server processing, our hosting and security providers carry and protect the requests and host the temporary storage and processing server; they act as infrastructure providers for the requested operation. The analytics information described above is processed on our behalf by our analytics providers and, where Google Analytics and Yandex Metrica are active, by Google and by Yandex, either of which may process it outside your country. The screen shown after a finished export links to the Chrome Web Store and to a feedback form; following either takes you to Google, which handles your visit and anything you write there under its own policy. Websites you choose audio from receive those file requests and handle them under their own privacy policies. If you contact support, the email providers involved process your message and email address.

Your rights

Depending on where you live, data-protection laws such as the GDPR and the CCPA give you rights over your personal data, including the rights to access, correct, or delete it, and to object to processing. Where we rely on your consent for analytics, you can withdraw it at any time, either by declining in the banner or by turning analytics off in the site settings; withdrawing does not affect processing that already happened. Local browser data can be cleared on your device. Server-processing content is anonymous and short-lived by design; cancelling the job requests immediate deletion, and the automatic limits above apply even if the browser disconnects. If you have contacted support, you can ask us about the email address and message we hold.

Security

Audio and queue data stored on your device are protected by your browser and your device. Keep your browser profile and device secure. Local-mode files remain inaccessible to Audio Joiner. Server processing uses HTTPS, private storage, scoped signed links, anonymous session tokens, strict size and time limits, and automatic deletion. No internet service can guarantee absolute security, so keep your own copy of every source file and do not upload material you are not permitted to process.

Children’s privacy

Audio Joiner is a general-purpose tool and is not directed at children. We do not knowingly collect personal information from children.

Changes to this policy

We may update this policy from time to time, and we will revise the effective date at the top of this page when we do. If a change materially affects how the website or the extension handles your data, we will make that change clear in the product before it takes effect.

Contact

If you have questions about this Privacy Policy, contact us at [email protected].