Even looking at the filename seems pretty suspect, as an aside. What if the filename was BankruptcyPreparation.docx, or TerminationOfBobDobbs.pdf, etc? The metadata about a file should be confidential as well.
Had it been BankruptcyPreparation.docx, or any other sensitive file name I would never have shared it. Going forward I won't be sharing dog.gif either.
I'll continue to use your products. Even if you were to post BankruptcyPreparation.docx. Here's why: You're not a bunch of fucking idiots.
If 37signals was a mish-mash of security issues and red flags, ya, I might be a bit pissed to see BankruptcyPreparation.docx mentioned.
Some of us would love to hear that 37signals fucked up large and did something imperfect. Not because of narcissism or blind hate, but just because it makes their success digestible, makes them human.
You're welcome.
What I will question, however, is the assertion that looking at user filenames is suspect. That's easily fair game, and to claim otherwise is as ridiculous as claiming your dentist has no right to see your dental records, or your bank shouldn't know how much money is in your account.
If you're that protective of your data, then it's up to you make wiser decisions. For starters, don't name your files SuperSecretPrivateInfo.doc and then give them to other people to store. Take a look at their extremely readable privacy policy. Send them an email with questions. If you care so much, take action and stop blaming other people for your own laziness.
The issue is not that they looked at things, the issue is that they chose to tell the world about it.
Really: What is it here that makes you so upset? Would you be concerned if your dentist told you, "I filled a cavity last year"?
IMO, there is customer data on their servers that they should not disclose without the consent of their customer. If so, the moment you allow a service provider to expose some information without such consent, you are accepting the fact that there are is a border (no matter how vaguely defined) between 'OK to disclose' and 'not OK to disclose' data, and that it is up to the service provider to decide where that border lies.
Because of that, I think a provider should not disclose any information about their clients, no matter how tiny, even if the information cannot be traced to any particular user, unless their terms of service clearly state what they will disclose (or sell to third parties)
(And yes, I _do_ read terms of service)
We can go back and forth on this all day long, but these are the facts: (1) your online data is not safe, unless you encrypt it yourself and (2) in this instance, no user identifiable information was given.
At least 37signals never said that they don't have access to those files, like other companies would make you believe:
http://www.businessinsider.com/dropbox-updates-security-term...
Fucking BINGO. I'm always shocked how many people on HN don't understand this, considering the high percentage of techies and programmers.
We expect more from them.
I am not trying to be argumentative but want to respond to a point you made as I think it is critically important for many HNers running or aspiring to run SaaS solutions-
"If you're that protective of your data, then it's up to you make wiser decisions. For starters, don't name your files SuperSecretPrivateInfo.doc and then give them to other people to store."
For real? I guarantee that 37signals would not sanction such a ridiculous statement. Most SaaS companies wouldn't touch such claims with a 40' pole.
The industry lives and breathes on the feeling that the data is confidential. We're currently looking at some hosted helpdesk ticket solutions, and I can tell you that if there was even the slightest hint that the vendors casually browsed our data we would rethink the whole adventure.
You can waive your arms and talk yourself blue in the face about your security protocols, but in the end it all comes down to trust. This kind of slip-up erodes that trust.
Have you ever supported a product that has external users? Eventually have to see their data in some way, shape, or form. Whether it be a username, email address, ip address, user-agent strings, filenames, etc; there are times when troubleshooting, verifying functionality, validating report data, etc where you will have to look at at least some subset of actual customer data somewhere. It is simply unrealistic to think otherwise.
How would you go about providing customer support or auditing without looking at the customer data required to complete such tasks?
(edited to add quote)
And if an apartment dweller had a plumbing leak, the landlord would enter their apartment and fix the leak. They would access on a need basis. They wouldn't do casual sneak and peeks and then post analysis on the entry door that seven residents have bongs in their living rooms.
Seriously, though, mechanisms to deal with exception situations, such as customer support, has nothing to do with "looking because it made for a fun blog post".
I only engage in this conversation because this is important for many HNers -- spin all the justifications you want, or blame users (a good attitude that guarantees business failure), however this was a serious blunder that other businesses should look to avoid.
Even if you do casually trawl the data of your users, for the love of all things unholy don't talk about it.
You could maybe classify that as looking at customer meta-data if you wanted to.
Though if you think that is bad, what do you think of when you call a bank and the person at the other end can see all of your private banking data? Or even when you call some other company and some random call centre employee has your whole transaction history in front of them. Shouldn't that worry you more?
Perhaps saying, "it was a cat" was a poor idea if they only read the filename, but a lot of people are making a lot of assumptions here. If you're dealing with regulated or high-value data, you probably shouldn't be using 37signals without doing any kind of audit of their operating practices anyway.
You're assuming 37signals made an agreement ("we won't be able to see your filenames in our logs") that they intentionally never made, and then you're claiming they violated said non-existent agreement.
If you're a company with super-sensitive data then it's on YOU to choose the appropriate place to store that data. There are services made explicitly for that sort of thing. It's absolutely ridiculous and irresponsible to require a certain level of privacy features, sign up for a service that doesn't have those privacy features, and then act as if they violated your trust.
Having said that, their security policy does suggest that customers expect some level of privacy. It's just bad form to publicly announce that you've been poking around the content of customer data as part of a fun blog post about metrics.
Nobody is building classified weapons on Basecamp. If you say that Basecamp customers shouldn't expect any measure of privacy, I'll respectfully acknowledge that you might be correct about that.
I respect that viewpoint immensely, and I wish more people would think like that.
I think the main issue here is that the words "privacy" and "security" are so vague as to be meaningless. Consequently, people have mapped their own personal definitions on to them. For example, different people may care about different subsets of the following:
- Do you use SSL when I transfer sensitive data to your servers? - How secure is your database? What do you use to protect stored data from hackers? - Do you share user data with third-parties? If so, do you anonymize it? - Do you prevent your own employees from accessing my data? - Do you have an SLA that guarantees I will be able to access my data the vast majority of the time? - Do you have measures in place to ensure my data is never accidentally deleted?
Etc. The list could go on and on. If the customer is worried about any of the above (and sadly, most aren't), then she's in luck, because privacy policies and company email addresses are usually a click away on the web. I doubt I know anyone familiar with all the privacy and security processes employed by banks, doctors, financial aid offices, etc. Which is why it's confusing to see so many technically-savvy people up in arms about the name of a jpg file.
This encapsulates exactly why I think your position is naive. You're confusing reality with what-companies-say-to-make-money. It's as if you're completely unaware of the concept of marketing. You seem to be in a position to make purchasing decisions for your company, so let me explain: marketing is a tool used to make money. Again: MARKETING IS A TOOL USED TO MAKE MONEY.
37signals knows that people want to feel like their data is confidential. So they plaster pictures of locks and words like "safe", "secure", "24-hour surveillance", and "biometric locks" on their signup page. This is called marketing. It creates a feeling -- and nothing more -- so that people like you will click "Buy". It's like the airline commercials that depict flights as being comfortable and quiet. It's like oil company commercials that talk about how great it is to be green. It's like McDonald's commercials that show thin and healthy people eating Big Macs. It's smoke and mirrors, and you're falling for it.
The reality is that you have a choice: belong to the 99% who simply want to buy into a "feeling", or belong to the 1% who read the privacy policy and ask questions.
But if you're going to choose to be in the 99%, then do us all a favor and stop complaining about it.
See, we actually sell software as a service. Data security for our clients isn't marketing, it is the absolutely lifeblood of the company (just as it is a critical principal for this industry). 37signals knows that it was a foolish oversight to casually comment on content trawling, which is a good sign. Your ridiculous arguments in their favor do no one any good.
>> See, we actually sell software as a service.
Great, I sell software as a service too. This is an irrelevant fact that doesn't make you or I any more or less correct.
>> Data security for our clients isn't marketing, it is the absolutely lifeblood of the company
"Data security" is a vague term that has as many different definitions as there are people to talk about it. Your mistake is in assuming that your definition (in which seeing a file name in a log is unethical behavior and/or a security breach) is the one and only correct definition. Many many web developers disagree with your definition.
Secondly, security is marketing. You yourself have said, and I quote: "Even if you do casually trawl the data of your users, for the love of all things unholy don't talk about it." So not only do you recognize the importance of data security itself, but you recognize that even the appearance of data security (or lack thereof) can affect a company's bottom-line. From there, it should be easy to understand how companies use the appearance of security as a marketing technique.
>> 37signals knows that it was a foolish oversight to casually comment on content trawling
It seems to me that they've repeatedly defended their decision on both their blog and in this thread, and haven't removed the reference from their post. You're on your own, here.
Hopefully you guys learn from your mistake.