I'm Sjoerd Huissoon, and I make MasterBar on my own in the Netherlands, under the name SYIRD. This page tells you what MasterBar and masterbar.app do with information about you. I've tried to list everything, including the small stuff, so nothing comes as a surprise later.
Under the European privacy law (GDPR) I am the one responsible for this. My details are on the Legal page, and you can always write to privacy@masterbar.app.
MasterBar listens to what Live plays so it can measure it. That sound is handled on your Mac and never sent anywhere. MasterBar has no feature that uploads audio, and I never get to hear or see your music, your recordings or your Sets.
Some modules do hold on to sound for a while, always on your Mac:
The Recorder can listen to Live, to all sound on your Mac, to one app, or to the outputs or inputs of your audio interface. You pick that under Listen To. If you pick an input, macOS will ask whether MasterBar may use the microphone.
To fit in with Live, MasterBar reads Live's settings, its colour theme and its log file (for the delay of your audio interface), and the Set you have open, for its locators and to keep a bar layout per Set. It keeps its own settings on your Mac, including the date you first opened it, the bar layout for each Set (stored by the Set's file name and folder), the beat-sync calibration for each Set, which recordings you dragged into Live, the recent recordings and reference tracks you used, and your licence, which sits in your Mac's keychain.
MasterBar also installs a small helper in Live's Remote Scripts folder. The helper tells MasterBar where Live is playing. It only talks to MasterBar on the same Mac, never to the internet. The Terms list everything MasterBar changes on your Mac and how to undo it.
MasterBar also starts with your Mac, so it's there when you open Live. It turns this on the first time you open it from Applications. You can switch it off with Open at Login in Settings, or in the Mac's System Settings under General, Login Items.
This is the complete list. MasterBar has no ads, and no analytics service from another company.
The update check. About once a day MasterBar asks the update server, which runs on Cloudflare, whether there's a new version. The request contains the version you have, and like every internet request it arrives with your IP address. I use it to count how many copies are in use per day and version: the server turns your IP address into a scrambled code that is different every day, and only that code is kept, until the next day. I can count with it, but I can't tell who you are or follow you from day to day. New versions download by themselves and install when you quit MasterBar or choose Restart to Update. You can turn the check off with Check Automatically, under Updates in Settings.
Anonymous usage stats. With the same check, MasterBar sends a rough picture of how it's used: the macOS and Live version (without the last digit), whether your Mac has an Apple chip or Intel, its model name, the sample rate, which kinds of modules are on the bar, whether the bar sits above Live or on its own, the number of screens, your language and the week you started using MasterBar. The server adds each of these to a count for that day, once per Mac per day, and keeps nothing that tells Macs apart. It helps me decide which macOS and Live versions to support and which modules need work. If you start using MasterBar from version 0.9.5 on, it also reports each of these first steps once, in a separate request when it happens: opening MasterBar, finding Live, allowing Accessibility, hearing sound, adding a module and buying a licence. Such a report holds only the step and the week you started. The server adds it to a count per week, which shows me where new users get stuck. You can turn all of this off with Share Anonymous Usage Stats, under Privacy in Settings.
Crash reports. If MasterBar crashes, it sends a report the next time it opens, so I can find and fix the fault. You can turn this off with Send Crash Reports Automatically in Settings. The report holds the kind of error, the steps in MasterBar and macOS that led to it, the state of the processor at that moment, your MasterBar and macOS version and the model of your Mac. Other software on your Mac (drivers, plug-ins) only appears if it was one of those steps, your user name is taken out of file paths, and the identifiers macOS adds are removed. There's no audio in it, and nothing about your Sets. Reports are stored on Cloudflare and deleted automatically after 180 days. A short summary of each new report (versions, Mac model and one line about where it crashed) also lands in my email, at Google, so I see it quickly. To stop abuse, the server keeps a scrambled code made from your IP address for an hour. The address itself isn't stored.
Your free beta licence. Everyone who uses MasterBar during the beta keeps it free. To make that stick, MasterBar asks masterbar.app for a free beta licence the first time it opens. If that doesn't work, it tries again when it next opens, at most once a day. Nothing about you goes with the request. The server keeps the licence number, the date it was made and the country the request came from, estimated from your IP address, which itself isn't kept. Against abuse, a scrambled code made from your IP address is kept for a day.
The licence check. When it opens, at most once a week, MasterBar checks whether your licence is still valid, for instance after a refund, or when a licence was shared publicly. That check sends only the licence number (and, like any request, your IP address).
MasterBar isn't for sale yet. Once it is, you buy it from Paddle (Paddle.com Market Ltd, United Kingdom), my reseller. Paddle handles the payment, the invoice and the sales tax, and decides for itself what it needs to know about you for that. That part falls under Paddle's privacy notice. I never see your card or bank details.
When you buy MasterBar, Paddle passes me your name and email address and the order numbers; your name and email address can reach me as soon as you enter them in the checkout, before the payment is finished. I use them to make your licence and email it to you, and to help you when you lose it. Your name and email are part of the licence itself, and MasterBar shows your name in Settings, or your email address if there's no name, so it's clear whose licence it is. The licence email is sent through Resend, on servers in the EU. I keep your order details for seven years, because Dutch tax law asks me to, and your licence for as long as it's in use.
If you use the form to have your licence sent again, a scrambled code made from your IP address is kept for a day, to stop people from trying lots of addresses.
If you leave your email address on the site, I use it only to tell you about new versions and news about MasterBar. First you get one email to confirm. Without that confirmation you get nothing else. This runs on your consent, and you can withdraw it any time with the unsubscribe link in every email. After that your address isn't used for mailings any more.
The list is kept with Kit (Kit.com, United States), which stores the addresses and sends the emails for me. Kit only gets your address, and like any request your IP address, when you sign up.
The feedback form doesn't ask for your name. You can say what your message is about, and leave your email address if you'd like a reply. Your message is stored on Cloudflare and also comes to me by email. It only appears on the site, with the date and sometimes my reply, after I've read it and decided to show it. So please don't put things in it you don't want others to read. Your email address is never shown, and it is deleted from the site's storage after 90 days. The copy in my mailbox goes by the rule for emails below. A message stays until I take it down. If you want yours removed, email me and I'll do it.
When you open the form from MasterBar (Help, then Send Feedback), the link carries details that help me find a problem: the versions of MasterBar, macOS and Live, your Mac's model, the sample rate and buffer size, the name of the audio output, which modules are on the bar, how the bar is placed, the number of screens and whether Live is in full screen. The form shows you all of them and only sends them with your message if you leave the box ticked. Because they are in the link, they reach Cloudflare when the page opens, like any web address, but the site doesn't store them unless you send them. They are never shown on the site.
To keep spam out, a scrambled code made from your IP address is kept for an hour. The rules for what gets shown are in the Terms.
masterbar.app is hosted by Cloudflare. Like every web host, Cloudflare handles technical data such as IP addresses to deliver and protect the site. The site sets no cookies and has no ad trackers, and no analytics service from another company. Its fonts are served from masterbar.app itself. Because nothing tracks you, a Do Not Track setting in your browser doesn't change anything here.
There's one exception: the page where you buy MasterBar loads Paddle's checkout, which may use its own cookies to take the payment safely. That happens only on that page.
I count how often MasterBar is downloaded: per day, per version, per country, and by the site you came from, such as a search engine or a forum, as your browser reports it. The country is Cloudflare's estimate from your IP address; the address itself isn't kept. These counts are just numbers. Nothing about you is stored with them.
I also count how often each page is opened: per day, per page, and by the site you came from, as your browser reports it or as the link you followed says. These counts hold no IP address and nothing that tells visitors apart. They are kept for 400 days.
I never sell your data, and I only share it with the services above, each for the job described there:
Some of these companies are based outside the EU. The American ones are covered by the EU-U.S. Data Privacy Framework, and where they offer them, by the EU's standard contractual clauses as well. For the United Kingdom the EU has decided that its protection is adequate.
Making and sending your licence is part of our agreement when you buy MasterBar. Keeping order details is a legal duty. The mailing list, and the email address and MasterBar details you send with feedback, run on your consent. The update check, the daily count, the page counts, the anonymous usage stats, crash reports, the feedback form and the abuse protection rest on my legitimate interest in keeping MasterBar working, safe and free of spam, and in knowing roughly how many people use it and read the site. For those I keep the data as small as I can, as described above, and you can object to them. Nothing is decided about you automatically.
You can ask me what I have about you, and have it corrected, deleted or sent to you. You can also object to how I use it, or ask me to use it less. Email privacy@masterbar.app and I'll answer within a month. If you think I'm getting it wrong, you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, or the one where you live. In the UK that's the ICO.
MasterBar isn't meant for children under 16, and I don't knowingly collect anything from them.
When MasterBar changes in a way that matters for this page, I update it and change the date at the top. Bigger changes also go in the update notes.
Questions about privacy: privacy@masterbar.app