6 ms·
Update to our privacy policy and apology
- underseacables 5y agoI didn’t really worry so much about this issue because I’m only a minor user of the software, but I really like it. I understand why this issue raised a great deal of concern, but I kind of just shrugged. I hoped that things would work itself out because it is good software.
- axguscbklp 5y agoMaybe I am being uncharitable, but my initial reaction is: What is all this verbiage? Just make software that does not phone home. Audacity does not need to phone home to implement any of the features that people actually use it for, so make it not phone home. There is no need for legalese or complex explanations. Whatever you think you are going to get out of getting more user data, just drop it. You do not need it. Just make the software not phone home, end of story. Like I said, though, maybe I am being uncharitable. Am I missing something?
- TedDoesntTalk 5y ago> Am I missing something I think so. It optionally phones home to see if there are version updates. It optionally phones home after a crash. They have to publish legalese to comply with GDPR because those phones to home store audacity version number, operating system and operating system version number, and country of origin (based on up). It allows them to know when it’s safe to drop support for certain operating system versions.
- axguscbklp 5y agoWhy not just drop all that version updating and error reporting functionality?
- InsaneOstrich 5y agoBecause it's useful?
- deleted 5y ago[deleted]
- TedDoesntTalk 5y ago… sure, and why not just publish the binaries on CD-ROM?
- axguscbklp 5y agoWould they still need to publish legalese if they made it so that updates and sending of error reports required the user to click a button every time, and under the button there was some text explaining exactly what data was going to be sent?
- ohgodplsno 5y agoYes. Laws _require_ you to have a privacy notice. Just because your license says the software is provided AS IS does not mean it's enough. Noone is going to bother you if it's a small open source project by a bunch of maintainers, but as soon as you're a company, you have to.
- TedDoesntTalk 5y agoFor the USA, that's not always true: https://www.swlaw.com/blog/data-security/2015/03/12/why-you-need-a-privacy-policy-part-2-avoiding-three-common-fumbles/#:~:text=There%20is%20no%20general%20federal,that%20can%20lead%20to%20liability https://www.swlaw.com/blog/data-security/2015/03/12/why-you-.... But I know Audacity has a sizable European userbase, too.
- selfhoster11 5y agoAre you suggesting that Audacity is something that needs a lot of auto-updating? It's not like an OS. Updating it can wait.
- pabs3 5y agoIt is pretty simple to do telemetry and phoning home correctly; be transparent and give the user control. Show them exactly what is being sent, how it will be used, let them edit the data and let them choose to when/how send it or not send it. The 0ad project does this well IMO.
- teknopaul 5y agoNope.
- TedDoesntTalk 5y agoThis is one of the best apologies and most thorough explanations of a faux pas that I’ve ever read. Great job, very well written.
- wereHamster 5y agoIt's a repeating pattern: companies try to push as far as they can, if users don't complain they get away with whatever they're doing. If users complain they write an empty apology letter and try again in a few months.
- meowface 5y agoUnrelated to this particular scandal and its (likely?) resolution, but, if I were them, I'd immediately fire the guy who was essentially threatening to torture/kill someone in a GitHub issue a few days ago over an alleged copyright infringement dispute (https://news.ycombinator.com/item?id=27891005 https://news.ycombinator.com/item?id=27891005). Then maybe they can start moving past the last few months of chaos. He's "Head of Strategy", though, so doubtful anything will happen. [Latest updates to the story below] A supposedly leaked statement from their "Chief Product Officer", possibly suggesting the death threat is officially approved: >We put a lot of effort to neutralize his code, and spent a lot of $ and time for this. His actions are total copyright infringement. So I suppose none of us should worry about his feelings. Response from the threatened author: >If the statement is real, does it mean my project costs them a lot of money and effort, so it's ok to send a kind of death-threat to me? The author posted a call for help here: https://github.com/Xmader/musescore-downloader/issues/130#issuecomment-884549957 https://github.com/Xmader/musescore-downloader/issues/130#is... >Rather than money, more importantly, I need good lawyers for copyright, immigration status / status of political refugee I find this orders of magnitude more outrageous and infuriating than the telemetry brouhaha. Based on the actual facts, that scandal seemed a bit overblown despite their poor handling of it. This, on the other hand, is truly fucked up.
- perihelions 5y agoI've submitted that call for help as a separate HN story. Seems pretty damn important!
- dkdbejwi383 5y agoI think this situation/comments have been blown out of proportion a bit. To me, the situation reads more like: Muse Group have held back on litigating over copyright infringement (whether that is a valid claim or not) because they are aware of the alleged infringer's precarious political situation, however they've turned a blind eye for too long and are now in a difficult position where they either lose money where they are paying for licences for content that this developer has allegedly stolen, or they litigate to protect their interest and risk having the guy deported. It seems like they're just trying to be frank and level with the guy. Maybe it's just that text isn't the best way to get this message across, or the CPO's communication style doesn't work for some folks. But I don't think it's like an "offer you can't refuse" mobster tactic as some would like to claim.
- comex 5y agoNote that since the whole privacy policy fiasco, another issue with Muse Group has come up; my guess is that this is what they're referring to when they mention in the thread that they're deleting "off topic" content. Muse Group's head of strategy told someone to take down their (allegedly copyright-violating) repository or else supposedly be at risk of being deported to China and then punished for their alleged political speech against the Chinese government. https://twitter.com/marcan42/status/1417085393762099200 https://twitter.com/marcan42/status/1417085393762099200 The irony is that the original MuseScore data being mirrored in the repository is itself full of copyright violations.
- rPlayer6554 5y agoHoly crap, that's scary.
- kbenson 5y agoI'm always hesitant to buy into these framings of things. It seems as a society we've become far to enamored of beleiving every single thing that can be construed as "nice business, it would be a shame if something happened to it" type extortion as that without any consideration. The options here are believing someone when they say "I would report this but it might cause far more harm to the person than I feel comfortable being responsible for" but going into more detail than strictly required, or believing that it's all a thinly veiled threat to get them to act. I'm more inclined to believe it's both, that the person making the statement doesn't want to be responsible for something like that, and is also spelling it out so the person in question is aware of what's possibly on the line, because "there will come a time when hesitation is no longer possible" is not necessarily a threat, it's a statement of fact for anyone that wants to retain a copyright, as if you don't defend it you end up losing it. There may be more to it that puts it in a different light, and I'll also definitely admit that I might have a bit of bias just from seeing that it came from twitter. My default assumption about anyone getting outraged about anything on twitter is that they've likely jumped to conclusions and gotten one or more salient facts wrong, and that generally has served me well. Twitter, as a medium, seems to work best in expressing extreme emotions and not delivering all the useful facts, so incentivizes such things. Edit: Correction, in fact it's trademark that you can lose if you don't defend it, not copyright, and has happened to "aspirin, escalator, butterscotch, zipper, yo-yo, thermos, and heroin" according to one source I found. I'm not sure exactly how this affects my point materially though, as I don't think that's necessarily a requirement for wanting to enforce the law on something that you think it causing you harm.
- sleavey 5y agoIf they were truly repentant the explanation would be a few sentences saying that they screwed up and everything is back to the way it was before and they won't do it again. Instead it's an essay.
- dkdbejwi383 5y agoIf they'd only come out and said one or two sentences, people would still be up in arms about them holding back information and not being forthcoming. I appreciate the fact they've spent some time actually thinking about this and working on revising their policy and making a thought out statement.
- sleavey 5y agoIf the one or two things they had said included "everything is going back to the way it was before" then I don't think people would have been up in arms.
- teknopaul 5y agoCorrect. They have just reiterated repeatedly in different ways that they are not listening. What everyone wants is the phone home code removed. If they just did that a git commit comment would suffice.
- square_usual 5y agoI really like the other thread on the front page right now [1] that's very relevant but not quite the same thing, because it makes the more important point here: this Privacy Policy change (aside from the provision barring children from using it) wasn't a big deal if you actually sat down and thought about it for a second, but the reputation of the Muse Group, and through them, Audacity, has fallen due to everything they've done, and I think it'll be very very hard to fix that now. Sure, they've "fixed" the privacy policy, but others on this thread have already brought up that one of their members is threatening an expat with deportation, and let's not forget the new CLA they made for Audacity. When people started forking Audacity over the privacy policy change I was surprised (in the "is this what it take for people to fork?" sense), but I sure hope those forks stick around and improve because I don't trust Audacity to not do stupid things again. 1: https://lwn.net/Articles/862073/ https://lwn.net/Articles/862073/, HN: https://news.ycombinator.com/item?id=27926611 https://news.ycombinator.com/item?id=27926611 E: A couple of edits to space stuff out and add links.
- bscphil 5y agoAs someone accustomed to reading privacy policies, it was immediately obvious to me that this was the case. After the Audacity team got bought out (aquihired?), some lawyers from Muse had a look over the privacy policy and pointed out the obvious: that if a court ordered them to, they would have to turn over any information they had. So they added that to the policy. Perfectly boring stuff. Indeed, despite the massive amount of fearmongering I saw about it on Twitter, that appears to be what happened: > The most unclear and damaging part of the original document stated that we collect personal information “…necessary for law enforcement, litigation and authorities' requests (if any)”. This was interpreted to mean that we intended to collect and store unspecified additional information on top of the basic system information mentioned elsewhere in the privacy policy. This is not true, as could be seen through inspection of the source code and network analysis of the release binaries. However, we agree that the wording used in the old privacy policy made it sound like it might be true. We have now changed the wording to remove this source of confusion. To be clear, any organisation, if ordered by the court, is required to cooperate with an investigation, and doing otherwise is considered to be an obstruction of justice. These are not the rules we create, these are the requirements we must follow. However, we would only be able to provide the specific information mentioned in the privacy policy (outlined below) and nothing more. On the other hand, I 100% agree with everything else you've said about Muse: they appear to be deeply untrustworthy and have a deservedly bad reputation for some of the stuff they've done. Likewise, I hope a community fork takes off and succeeds. Sometimes an issue like this is the straw that breaks the camel's back. Similarly, resentment stewed among contributors toward OpenOffice before it was forked, and that turned out to be a massive success.
- matco11 5y ago>The old privacy policy contained a provision that discouraged children under 13 years old from using the program. After extensive further consultation with our lawyers, we have determined that this provision is unnecessary given the actual mechanics of data transmission and storage. This is great. Does anyone have any idea on how the actual mechanics of data transmission and storage can play on the legal side of things to enable use by under 13?
- kbrosnan 5y agoThe provision in the privacy policy likely comes from a overly cautious interpretation of COPA. The Childrens Online Privacy Act (COPA) Requires companies doing business in the US to get parental consent before creating an account for a child under 13 (among other things).
- acituan 5y agoToo many words is a yellow flag; those words including a lot of opining about out of scope things like how users might be unnecessarily scared by the legal language of GDPR is an orange flag; some of their points being factually incorrect is a red flag. Maybe they are truly honest and just have a bad GDPR + PR team, but I just can't bring myself to trust them. From their apology; > The best example is the catchall phrase ‘personal information’, a non-specific term that understandably raises concerns for regular readers. Personal information is actually a pretty accurate designation with sufficiently clear boundaries in GDPR context and the concerns it may raise are perfectly valid. It can't be downplayed to "just legalese". E.g only because IP address are personal information you had to separate your collection and retention policies very clearly, and could be help accountable on that. > The most unclear and damaging part of the original document stated that we collect personal information “…necessary for law enforcement, litigation and authorities' requests (if any)”. > In addition, the steps we have taken to anonymise all stored data means that it would be of extremely limited use to anyone. Be that as it may, those records are required for your GDPR compliance too, an information that is pretty useful about how honestly this policy will be executed. > It is verifiably untrue that we hid the exact data being collected. As noted by journalists who investigated the issue, Audacity is free and open source software, and an inspection of its source code shows that the data it shares is extremely limited. That is only true for the client code. To my knowledge the server side code is not public, as such it is completely unverifiable outside an audit context that whether you merely collected the IP address or also retained it for example. I am not an active user anymore, but I hope people make repeated data takeout requests just for that redundant bit of evidence in case they are found to be in non-compliance.
- Rebelgecko 5y ago>We have taken steps to ensure that we never store a full IP address (we now truncate it before hashing or discard it entirely Let's say there's still 30 bits of an ipv4 address left after they "truncated it before hashing". How long would it take to brute force the entire truncated address space? An hour?
- selfhoster11 5y agoSimply put, I don't trust them. Not any more. This issue was handled atrociously and the next computer I'm installing Audacity on will either have a pre-Muse version or a fork on there.
- therouwboat 5y agoJust to stir this mess even more, "MuseCY SM Ltd., a Cyprus company with an address at Spyrou Kyprianou, 84, 4004, Limassol, Cyprus" Is that tax haven?
- perihelions 5y agoThat page displayed a Russian address a week ago, >"For the purposes of this Notice, WSM Group with registered office at Moskovsky pr-t,40-1301, Kaliningrad, Russia, 236004 (“Audacity“, “us“, “we“, or “our“) acts as the data controller for the Personal Data that is collected via the App and through the App." The new version replaced that line with this: >"For the purposes of this Notice, MuseCY SM Ltd., a Cyprus company with an address at Spyrou Kyprianou, 84, 4004, Limassol, Cyprus (“Audacity Team“, “us“, “we“, or “our“) acts as the data controller for the personal information that is collected via the App and through the use of the App, as further outlined in section 2 (“personal information”)." source: archive.is mirrors https://archive.is/https://www.audacityteam.org/about/desktop-privacy-notice/ https://archive.is/https://www.audacityteam.org/about/deskto...
- richeyryan 5y agoThat address in Cyprus is in the EU so if it is acting as their data controller it probably has something to do with that.
- teknopaul 5y ago"data controller" is a GDPR term.
- NmAmDa 5y agoI think nothing really changed. They only provided clearer explanation on what they are collecting and why, even though it's still not as clear as it needs to be.