For years, Bartender was one of those Mac utilities people installed and then forgot aboutin the best possible way. It cleaned up the chaos in the macOS menu bar, tucked away noisy icons, revealed them when needed, and generally made your Mac feel less like a digital junk drawer. Then, suddenly, the app itself became the messiest icon on the menu bar.
The controversy around the Bartender app for Mac is not simply that it can request Screen Recording permission. That part has a technical explanation. The real problem is trust. A utility that needs sensitive macOS permissions quietly changed hands, changed signing certificates, and appeared with new ownership details that were not clearly communicated to paying users at the time. For a simple-looking menu bar app, that is the software equivalent of finding out your houseplant has been filing tax documents in your name.
This article breaks down what happened, why Mac users were alarmed, what Screen Recording permission really means, and how to think about privacy when small apps ask for big access.
What Is Bartender for Mac?
Bartender is a macOS menu bar management app. Its main job is to organize the row of small icons at the top-right of your Mac screen: Wi-Fi tools, cloud sync apps, VPNs, battery utilities, backup software, clipboard managers, calendar widgets, and the twelve other tiny icons that somehow multiply when you are not looking.
The app lets users hide menu bar items, reveal them with a click or gesture, create spacing, search for items, build presets, and make the Mac menu bar feel cleaner. For users with smaller MacBook screens, especially models with a notch, this can be genuinely useful. A crowded menu bar can push icons out of view, and Bartender became popular because it solved that problem elegantly.
That popularity is part of why the 2024 ownership controversy hit so hard. Bartender was not some random download from a suspicious corner of the internet. It was a long-running paid Mac utility with a loyal user base and a reputation built over many years. People trusted it because they trusted the developer, the update history, and the app’s behavior. When the identity behind the app became unclear, the entire trust equation changed.
Why Does Bartender Ask for Screen Recording Permission?
The phrase “can record your screen” sounds terrifying, and honestly, macOS does not do much to make it feel less dramatic. Apple’s privacy settings describe Screen & System Audio Recording as permission that allows apps to record your screen and audio, or just audio. That is a broad category, and it covers everything from Zoom to screen recorders to utilities that need to inspect what is visible on screen.
Bartender’s own explanation is that it needs Screen Recording permission to read menu bar items so it can show the correct image for each item and manage what is displayed. According to the app’s permission documentation, Bartender says it reads only the menu bar area and does not record the screen in the normal video-capture sense. It also notes that macOS may show a purple menu bar indicator when the app reads the screen.
So, is Bartender secretly filming your desktop like a tiny menu bar paparazzo? There is no public evidence proving that. But the permission itself is still powerful. Once users grant Screen Recording access, they are relying on the developer’s promises, the app’s code, Apple’s platform protections, and their own ability to notice when something changes. That is a lot of trust to place in a utility whose whole personality is “I hide little icons.”
The Other Sensitive Permission: Accessibility
Screen Recording was not the only reason security-minded Mac users raised an eyebrow. Bartender also uses Accessibility permissions, which are common among automation, window management, and interface-control tools. Accessibility access can allow apps to interact with the system interface, move items, click controls, and perform actions that ordinary apps cannot.
Again, Bartender has a practical reason for requesting this access: it needs to arrange and manipulate menu bar items. The concern is not that Accessibility permission is automatically evil. It is not. Many legitimate Mac utilities need it. The concern is that Screen Recording plus Accessibility is a sensitive combination. One permission can help an app see what is on screen; the other can help an app act on the interface. That is exactly the kind of access users should grant only to software they understand and trust.
What Actually Happened With Bartender’s Ownership?
In June 2024, the Mac community discovered that Bartender appeared to have changed ownership without a clear public announcement before the change became visible to users. The issue surfaced after MacUpdater warned users that the company behind Bartender had been replaced in a silent and questionable manner, particularly around version 5.0.52 and later.
Reports at the time described a change in the app’s signing certificate. That matters because macOS uses developer signing and notarization as part of its trust model. A certificate change does not automatically mean malware. Developers sell apps, companies reorganize, and certificates can legitimately change. But when an app with sensitive permissions changes certificate without a clear explanation, users naturally ask: who is now responsible for this software?
The answer became clearer later, but not immediately enough to calm everyone. Public reporting and later statements connected Bartender to Applause, a company described by the new owners as a small team of indie developers based in New York City. Bartender’s website later identified Applause Group, Inc. in its copyright footer. The new owners also published a post saying they should have communicated better and that they had overlooked a formal announcement during the transition.
That explanation may be true. It may also be completely ordinary from a business standpoint. But for users, the damage was already done. In privacy-sensitive software, silence is not neutral. Silence is a feature, and not a popular one.
The Certificate Change Was the Spark
The certificate change became the visible clue that something had shifted behind the scenes. Users noticed that the app was no longer signed as expected. Reports mentioned signatures associated with App Sub 1 LLC and then Bartender App LLC, while the Setapp version and later public materials pointed toward Applause Group.
To a nontechnical user, this may sound like corporate paperwork soup. To Mac power users, it looked like a supply-chain concern. A supply-chain problem happens when software people trust is altered, transferred, compromised, or repackaged somewhere along the distribution path. The scary part is that the user may still think they are installing the same trusted app, even when the people controlling it have changed.
That is why the Bartender issue became bigger than Bartender. It touched a question every modern computer user eventually faces: when you install an app, are you trusting the name on the icon, the developer behind it, the update mechanism, the platform, or all of the above?
Then Came the Telemetry Question
The situation became more uncomfortable when users and writers reported that Bartender 5.0.52 included code related to Amplitude, a product analytics framework. Analytics frameworks are not inherently malicious. Many software companies use them to understand crashes, feature usage, update problems, and onboarding issues. But adding analytics to a privacy-sensitive app during an unclear ownership transition is, to put it politely, a bold seasoning choice.
The new owners later said Amplitude was added to understand how many users were running into permission issues caused by the certificate change. They also said it was removed in version 5.0.53 onward. That removal was the right move, but it did not erase the bigger concern: users did not feel fully informed before the change.
Privacy is not just about whether data is abused. It is also about whether users are told what is happening before they have to discover it through update warnings, reverse engineering, Reddit threads, or a digital mob carrying pitchforks made of command-line tools.
Does Apple Notarization Mean Bartender Is Safe?
One defense offered during the controversy was that Bartender was signed by a valid Apple developer identity and notarized by Apple. That is useful information, but it is not the same thing as a complete privacy guarantee.
Apple notarization helps confirm that an app has passed automated checks and is not known malware at the time of notarization. It is an important layer in macOS security. But notarization does not prove that every business decision is transparent, that every analytics choice is ideal, or that every future update will behave exactly as users expect.
Think of notarization like a restaurant health inspection. It helps you avoid obvious disasters. It does not tell you whether the new owner changed Grandma’s soup recipe, raised the prices, or started collecting everyone’s favorite spoon preferences for “product improvement.”
Why the Bartender App Controversy Matters
The Bartender controversy matters because many Mac users rely on small utilities. These apps make macOS feel personal and productive. They resize windows, manage clipboards, automate tasks, organize screenshots, block distractions, control audio, and clean up the menu bar. But many of the best utilities need deep permissions to do their jobs.
That creates a strange bargain. The more useful a Mac utility is, the more access it may need. The more access it needs, the more trust it requires. And the more trust it requires, the more important transparency becomes.
Bartender’s core function was not the problem. Users understood why a menu bar manager might need unusual macOS access. The problem was the mismatch between access and communication. When an app can see part of your screen, control interface elements, and update itself under new ownership, users deserve clear notice before anything changes.
Was Bartender Actually Recording Users?
There is no credible public proof that Bartender was secretly recording users’ screens and uploading footage. The more accurate statement is that Bartender requests a macOS permission category that allows screen recording. The app’s stated purpose is to inspect menu bar items, not to capture full-screen video.
However, this distinction can be confusing for normal users because macOS permissions are broad. Apple does not offer a special “read only the menu bar icons and please don’t be weird” permission. Instead, the app falls under Screen Recording or Screen & System Audio Recording. That means users see a scary prompt, and developers must explain exactly why the permission is needed.
This is where Bartender’s situation became a perfect storm. A scary permission plus unclear ownership plus a certificate change plus analytics equals a trust crisis. None of those ingredients alone necessarily proves wrongdoing. Together, they make a very spicy privacy stew.
How Mac Users Should Evaluate Apps Like Bartender
1. Check Who Owns the App
Before granting Screen Recording, Accessibility, Input Monitoring, Full Disk Access, or Automation permissions, check the developer’s website, release notes, privacy policy, and company identity. If ownership recently changed, look for a direct announcement. If you cannot figure out who controls the app, that is a warning sign.
2. Read Release Notes Carefully
Release notes are not just boring paragraphs written to make “bug fixes and improvements” sound alive. They can reveal certificate changes, analytics additions, privacy changes, and compatibility updates. If an app with sensitive permissions changes behavior but does not explain why, slow down before updating.
3. Review macOS Privacy Settings
On macOS, go to System Settings, then Privacy & Security. Review Screen & System Audio Recording, Accessibility, Input Monitoring, Automation, and Full Disk Access. Turn off permissions for apps you no longer use or no longer trust. This is not paranoia; it is digital housekeeping. You clean your kitchen. Clean your permission list too.
4. Consider Network Monitoring Tools
Advanced users often use firewall tools to see when apps connect to the internet. This can help reveal unexpected analytics, update checks, or background traffic. It is not necessary for everyone, but it can be useful when evaluating privacy-sensitive utilities.
5. Look at Alternatives
Some users moved to alternatives such as Ice, Hidden Bar, Dozer, iBar, or other menu bar managers. Each option has trade-offs. Some are open source but less feature-rich. Some are simpler and require fewer permissions. The right choice depends on whether you need advanced triggers, notch handling, hidden bars, styling, or just a way to make Dropbox stop staring at you from the menu bar.
What Developers Can Learn From the Bartender Situation
The lesson for developers is simple: trust is a product feature. It should be designed, maintained, documented, and protected. If your app asks for powerful permissions, your communication must be stronger than average. If your app changes ownership, say so clearly. If your signing certificate changes, explain why before users discover it through warnings. If you add analytics, disclose it plainly and offer control where possible.
Developers sometimes underestimate how much emotional trust users place in small utilities. A menu bar app may seem minor, but it lives on the user’s machine every day. It launches at login. It updates in the background. It asks for system-level access. That is an intimate software relationship, even if the app’s main job is hiding icons like a tiny digital butler.
What Users Can Learn From the Bartender Situation
The lesson for users is not “never install Mac utilities.” That would be dramatic, and also boring. The Mac ecosystem is better because independent developers build clever tools Apple never gets around to making. The better lesson is to match permission level with trust level.
If an app only changes wallpaper, it should not need Full Disk Access. If an app manages your menu bar, it may need unusual permissions, but you should understand why. If an app changes ownership, you should expect a clear explanation. If that explanation arrives only after users start investigating, skepticism is fair.
Modern privacy is not about panic. It is about attention. Most people do not need to audit binaries or read developer certificates for fun. But everyone can review permissions, delay suspicious updates, and ask whether an app still deserves the access it once earned.
My Experience With Menu Bar Apps and Permission Fatigue
Anyone who has used a Mac for productivity knows the menu bar can become ridiculous. At first, it is clean and peaceful: Wi-Fi, battery, date, maybe Spotlight. Then you install a password manager, a VPN, a cloud drive, a calendar helper, a screen capture tool, a clipboard manager, a focus timer, a temperature monitor, a keyboard remapper, and suddenly your menu bar looks like a crowded airport departure board.
That is why an app like Bartender is so appealing. It promises calm. It says, “I will take this tiny chaos and make it elegant.” And for many users, it did exactly that. The first time you hide unnecessary icons and reveal them only when needed, your Mac feels cleaner. You may even feel like the kind of person who labels power cables and folds fitted sheets correctly. This feeling lasts about six minutes, but it is wonderful.
The catch is that convenience often arrives holding a permission prompt. A menu bar utility may ask for Accessibility. A screen capture utility asks for Screen Recording. A keyboard tool asks for Input Monitoring. A backup app asks for Full Disk Access. After a while, users become numb. They click “Allow” because they want the app to work. The permission dialog becomes another speed bump between desire and productivity.
The Bartender controversy snapped many people out of that habit. It reminded users that permissions are not decorations. They are doors. Once opened, those doors should be reviewed whenever the person on the other side changes. If a longtime developer sells an app, the trust does not automatically transfer like a license key. The new owner has to earn it.
That does not mean every acquisition is suspicious. Good apps change hands all the time. Developers burn out, move on, retire, or sell successful products to teams with more resources. That can be healthy. But when an app has deep access to a Mac, the handoff should be loud, boring, and crystal clear. “Here is who owns the app now. Here is what changed. Here is what did not change. Here is what data we collect. Here is how to contact us.” Boring transparency is beautiful. In security, boring is the luxury package.
In my own workflow, the Bartender story would make me pause before updating any utility with Screen Recording or Accessibility access. I would check the release notes, revisit macOS Privacy & Security settings, and ask whether I still need the app. Sometimes the answer is yes. Sometimes the answer is, “Actually, I can remove three menu bar icons and live like a normal mammal.” Either way, the useful habit is the same: do not grant permanent trust to software just because you trusted it once.
Conclusion: The Real Issue Is Not the Menu BarIt Is Trust
The Bartender app for Mac became controversial not because menu bar management is dangerous, but because powerful permissions require clear ownership and honest communication. The app’s Screen Recording permission has a technical purpose, and there is no public proof that Bartender secretly recorded users. Still, users were right to be concerned when ownership, signing, and analytics questions appeared without enough early transparency.
For Mac users, the takeaway is practical: review permissions, understand what sensitive access means, and pay attention when trusted apps change hands. For developers, the takeaway is even simpler: if your app asks users to trust you with their screen, their interface, and their workflow, do not make them solve a mystery to learn who “you” are.
The menu bar may be small, but the trust behind it is not.
