SoundMarshal Privacy Notice
Last updated: 20 November 2026
This notice explains how SoundMarshal handles your information: what the app keeps on your Mac, what it sends, and what happens when you visit soundmarshal.com, email us, join the Discord or leave a tip.
In short
- SoundMarshal changes your sound in your Mac’s memory as it plays. The sound is never recorded or sent anywhere.
- Your settings, presets and device profiles stay on your Mac, apart from the few settings named under “If you share usage data or send crash reports”.
- Once a day the app asks our update server whether there is a new version. That is all it sends by itself. If you choose to share usage data, it also sends some about once a week, and a short problem report with the next daily update check. If you choose to send crash reports, it sends a short crash report with the next daily update check. We keep both under a random number for up to a year.
- The app has no accounts and no ads. The website sets no cookies of its own and counts visits with Cloudflare Web Analytics, which sets none either.
- We count downloads, visits, clicks on our Discord and tip links, and update checks as totals only, with nothing that could identify you.
- We never sell your data or share it for advertising.
Your sound
To change what you hear, SoundMarshal needs macOS’s permission to record your Mac’s audio. macOS calls this recording, but SoundMarshal only processes the sound as it plays, in your Mac’s memory, and passes it straight to the speakers or headphones you choose. It is not saved to a file and not sent to us or anyone else.
What stays on your Mac
SoundMarshal keeps these on your Mac and sends none of them anywhere, apart from the few settings named under “If you share usage data”:
- Your settings, such as per-app volumes, apps you have hidden in the Mixer, the order of your presets, your keyboard shortcut, your Dock icon choice, hidden outputs, whether the welcome steps are finished, whether the audio permission has worked, which version of the License Agreement you accepted, whether you chose to share usage data or send crash reports and the random number that goes with them, the window’s position and when the app last checked for updates. They are in ~/Library/Preferences/com.ardasavas.SoundMarshal.plist.
- Your presets and device profiles, in ~/Library/Application Support/com.ardasavas.SoundMarshal. A device profile includes the device’s name, and a name can include a person’s name (for example “Arda’s AirPods”).
- Any presets you export, wherever you save them.
SoundMarshal starts at login only if you turn on Launch at login in Settings. If you share usage data or send crash reports, a tally of the week’s counts is also kept there, usually for a week at most, and removed when you turn either switch off.
To remove your settings, presets and profiles, open SoundMarshal, go to Settings and click Uninstall. It moves the app, your presets and your settings to the Trash, turns off Launch at login and removes the audio permission. Presets you exported stay where you saved them. If you cannot use Uninstall, the guide that comes with the download explains how to remove each item by hand.
Diagnostics and crash reports
If something sounds wrong, you can run Diagnostics from Settings or the menu bar. It checks each step of the audio path and shows a report in the app. The report stays in the app until you quit or run Diagnostics again. Copy Report puts it on your clipboard. SoundMarshal never sends it; if you email it to us, that is your choice.
The report names SoundMarshal’s version, your macOS version, your output device (its name, identifier and audio format) and any apps you have adjusted in the Mixer, with counters about the audio path. It holds no sound and none of your files. A device name can include a person’s name, and a Bluetooth device’s identifier is a code unique to that device, so read the report before you send it.
When an app quits unexpectedly, macOS saves a crash report on your Mac. When you click Copy Report, SoundMarshal adds how many crash reports macOS kept for it in the last 30 days and the newest one’s file name. For this it looks only at the names and dates of the files in that folder and counts only SoundMarshal’s. It never sends any of them. If you choose to send crash reports, it also opens its own crash reports from after your yes to read where in our code the crash happened (up to three places, each up to five steps deep, as numbers, never names), and sends only that and how many there were. It sends them with the next daily update check, and with the weekly report too if you also share usage data. macOS can also hand the app its own reports about crashes, freezes and heavy processor or disk use; the app keeps only where in our code they happened, in the same way, and nothing else from them. It also counts runs that ended without a normal quit, but only while you also share usage data, and sends that count with the weekly report. That is all “crash reports” means in the app: the files themselves stay on your Mac. Whether your Mac shares crash data with Apple is your choice in System Settings, under Apple’s privacy policy.
Update checks
Once a day, and whenever you choose Check for Updates, SoundMarshal asks our update server, updates.ardasavas.design, whether a new version exists. Like every request on the internet, it carries your Mac’s IP address and standard details such as your preferred language. It also says which version of SoundMarshal is asking, and which version of Sparkle, the open-source updater SoundMarshal uses. Unless you choose to share usage data or send crash reports, it sends nothing else about you, your files or your sound. Nothing downloads or installs until you click to install it. You can turn automatic checks off in Settings.
The server counts these requests as totals, one detail at a time, so we can see roughly how many Macs use SoundMarshal, which versions they are on, and which countries and languages they are in. The count keeps no IP address and nothing else that could identify you.
If you share usage data or send crash reports
Both are off unless you say yes. SoundMarshal asks once, after your sound first starts; a yes turns both on, and you can change either at any time in Settings. Sharing usage data is the switch Help us improve SoundMarshal, under Privacy. With it on, about once a week the update check also carries your setup (your Mac’s model, processor and memory, your macOS version and language, the kind of sound output and its sample rate, and the headphone correction in use, from our catalogue), how the app is used (how many days that week, which pages, how often you used Compare, Hold to Hear, the shortcut, preset import and export, which kind of preset, about how many presets and Mixer apps, whether the shortcut and Launch at login are on, and which Dock icon) and how well it runs (problems with the sound, which problem messages the app showed you, which step of an update failed, how often the sound output changed or a headset switched to call mode, rough CPU and memory use, and, if you also send crash reports, crashes, where in our code they happen and runs that ended without a normal quit). Automatic update checks have to be on for it to be sent.
Sending crash reports is a switch of its own, separate from usage data: Send crash reports automatically, under Sound, which shows again under Privacy as Send only crash reports automatically. With it on, the daily update check carries how many times SoundMarshal crashed and where in our code, as described under “Diagnostics and crash reports”. Automatic update checks have to be on for it to be sent.
A yes to either switch also makes a random number in the app. It is made from nothing about you, and it goes with every report so that we can see one copy’s reports together over time. We keep each report as one row: that number, the week, the app version, your country and language, and what the report carried. A day with a crash or a problem message also gets a small row of its own: that number, the day, the app version, and only the crash and problem facts. It never includes your name, the names of your devices or apps, the names of your own presets, or the sound itself, and we do not keep your IP address with it. Even so, treat it as data about you: a row describes one Mac, and someone who knew that Mac’s setup well might recognise it. We do not try to find out who a number belongs to. A check carries all of this together and, like any request, reaches our server with your IP address, and Cloudflare may keep a record of the request, number and address included, as described under “How long it is kept”.
When you turn either switch off, SoundMarshal stops sending what it covers, asks our server to delete every row with your number, the other switch’s rows included, and then removes the number from your Mac. If the other switch is still on, it starts a new number. It asks right away, and again with its next few update checks, so that one failed attempt does not leave rows behind. If you say yes again later, you get a new number, and the new reports are not linked to the old ones. We keep every row for at most a year, and delete older rows every day. The app does not show your number. Write to us and we will tell you where to find it on your Mac; quote it and we can show you, or delete, every row kept under it. If you delete the app without turning both switches off first, your rows stay until their year is up: we cannot find them from your name or email, only from the number.
The website and downloads
soundmarshal.com and the update server are hosted by Cloudflare. When you visit, Cloudflare receives your IP address and the usual details of a web request, such as the page, your browser and its language, so it can deliver the site and protect it from attacks. Cloudflare uses these under its own privacy policy. It also shows us overall numbers, such as visits per day and the countries they come from, and, for about a month, records of single requests, such as visits it blocked or challenged.
The site sets no cookies of its own. If Cloudflare suspects a visit is automated, it may ask your browser to prove it is not, and then set security cookies, such as cf_clearance, that are used only for that check.
To count visits, we use Cloudflare Web Analytics. Your browser loads a small script from Cloudflare. It reports the page you opened, the site that sent you, how quickly the page loaded, and your browser, system and kind of device. It uses no cookies and keeps nothing about you in your browser, and Cloudflare shows us only totals, such as visits per day, per page and per country.
When you download SoundMarshal from this site, the download is added to daily totals, such as downloads per day and per country, again with nothing that could identify you. Opening soundmarshal.com/discord or soundmarshal.com/tip adds one to a daily count for that link, again with nothing that could identify you.
Email, Discord and tips
These happen only when you choose them.
- Email. Mail to support@soundmarshal.com is forwarded by Cloudflare to our Gmail inbox (Google), and we answer from there. We use what you send only to help you and to fix what you report. We keep a conversation for one year after it ends and then delete it, or sooner if you ask.
- Discord. soundmarshal.com/discord takes you to the SoundMarshal server on Discord, where Discord’s privacy policy applies. We see what Discord shows a server’s owner, such as your Discord name and profile and what you post there.
- Tips. Leave a Tip opens our page on Buy Me a Coffee, whose privacy policy covers your visit and any payment. If you tip, Buy Me a Coffee shows us the name you enter, your email address, your message, and the amount and date of your tip. It never shows us your card number. A tip unlocks nothing.
Where this data comes from
We get personal data in three ways: from your browser or the app when they reach soundmarshal.com or our update server; from you, when you write to us; and from Discord and Buy Me a Coffee, when you use them.
Who handles data for us, and where
- Cloudflare runs the website, the downloads, the update server and the email forwarding.
- Google runs the Gmail inbox where support email arrives.
- Discord and Buy Me a Coffee, only if you use them. They decide for themselves how to handle your data, under their own policies.
These companies are based in the United States and may process data in other countries. Cloudflare, Google and Discord take part in the EU-U.S. Data Privacy Framework, and Buy Me a Coffee uses the European Commission’s standard contract clauses.
Why we use this data
- To deliver the website, the download and updates, and to keep them secure: our legitimate interest in running SoundMarshal safely.
- To count downloads, visits, clicks on our Discord and tip links, and update checks as totals: our legitimate interest in knowing roughly how many people visit and use SoundMarshal, how they find it, on which devices and versions, and in which countries and languages.
- To see how SoundMarshal is used and how well it runs, if you choose to share usage data: your consent, which you can withdraw at any time in Settings.
- To find and fix crashes, if you choose to send crash reports: your consent, which you can withdraw at any time in Settings.
- To answer your email: because you asked us to, and our legitimate interest in helping people who use SoundMarshal.
- To see who tipped and thank you: our legitimate interest in knowing who supports SoundMarshal.
- To run the Discord server: our legitimate interest in offering a place where people can get help.
How long it is kept
- Settings, presets and profiles: on your Mac until you delete them.
- A diagnostics report: in the app until you quit or run Diagnostics again.
- Download, link and update counts: totals only, for as long as they are useful.
- Visit totals from Cloudflare Web Analytics: Cloudflare shows them to us for six months.
- Usage data and crash reports you chose to send: at most a year, and deleted sooner when you turn either switch off.
- Support email: one year after the conversation ends.
- What Buy Me a Coffee shows us about a tip: in our Buy Me a Coffee account, for as long as it exists.
- Discord posts: until you or we delete them, under Discord’s policy.
- Cloudflare’s records of requests: as long as Cloudflare needs them to run and protect its network. The ones it shows us go back about a month.
Your rights
You can ask us what personal data we have about you, who we have shared it with, and for a copy you can take elsewhere. You can ask us to correct or delete it, and to pass that on to the companies above. Where we rely on our legitimate interest, you can object, and we will stop unless the law lets us continue. We make no automated decisions about you. If unlawful handling of your data harms you, you can claim compensation. You never have to give us personal data, but without your email address we cannot answer you.
What we may have is: your emails, if you wrote to us; what Buy Me a Coffee shows us, if you tipped; your Discord name and posts, if you joined the server; your copy’s usage and crash reports, if you turned either on; and, for about a month, the records Cloudflare shows us. Write to support@soundmarshal.com and we will answer within 30 days. These reports carry a random number and no name, so we cannot find yours from your name or email: turning the switches off in Settings is how you delete them, and your number, which we will tell you how to find on your Mac, is how you ask us to show you what we hold.
If you think we have handled your data wrongly, you can complain to the data protection authority where you live. In Türkiye, that is the Personal Data Protection Authority (KVKK), once you have written to us first. In the European Union, it is the authority of your country.
Children
SoundMarshal needs no personal data from anyone, children included. If we learn that a child under 13 wrote to us, we delete the email once we have answered. If your child emailed us and you want that email deleted sooner, write to us. SoundMarshal is not meant for children under 16. If you think a child shared data with us, turn both switches off in Settings on that Mac, or write to us and we will help you find its number and delete what it sent.
Changes
Before SoundMarshal, its website or its support handle data in a new way, we will update this notice and the date at the top.
Contact
The data controller is Arda Savaş. Write to us at support@soundmarshal.com.