[AT&T Samsung Galaxy Note I717] Jamesyboy:
In the past, CM has allowed users to opt out of sending their data. It's recently decided to remove the "optout feature" (c'mon, is that really a "feature"), forcing users to eat it.

http://www.androidpolice.com/2013/0...pting-out-of-cm-stats-cyanogen-says-to-chill/

"Cyanogenmod Will No Longer Allow Opting Out of CM Stats-- Cyanogen Says to Chill"

in response, i kindly made this argument:

"A fundamental issue still exists. If the data is collected via a unique identifier, and it has a timestamp, then it isn't as anonymized as people think. Anyone with a basic understanding of data security knows that. I think the uproar has to do with the reputation of the team as the protectors and defenders of our platform...you give us choice. But when we see behavior that doesn't add up, were naturally going to believe you've used that position in the community to do evil. We understand you want the the data.

What doesn't make sense, and the natural road for us all to go down:

1) is this being used to monetize CM?

2) installation data: to include location, language, device, build version, and carrier, are all things that can be identified using a single, static event report. Why should we be comfortable with an always-collecting, transmitting-in-the-background service? What's the use-case for this? You've said yourself that Google Play apps themselves often collect this data..why is that method insufficient for CM? And why should we have to expect the same from you guys as we do from everyone else. Surely there's a way to collect the necessary data you need with a scalpel, negating the need for a device drag-net like this.﻿

In all seriousness, i trust CM to do the right thing...i just can't tell right now if they've done the lazy thing, and created a service which is omnipresent, omnipotent, running in the background and silently spying on me, just so CM can tell which language my device is running, my general location, my build information, etc.

That's fine, it's simple data, and it's fairly straight forward.

The question is, if you needed that data (which CM says it does), then why are you collecting a much, much more complicated data set, and why won't a simple installation report do? Why won't running for a short period of time...say, 5-7 days do?

Why did they take the Carrier IQ route?

Maybe they want it just so they can have it. As Koushik stated on the google plus post (where he does a great job at assuaging some fears, and creating others):

"---Did you know over half of our users are in China? They just passed the US in terms of CM installation base.

Call it ego surfing, but the data is incredibly useful."﻿

So they're collecting all this data, without a need? It's obvious why it's extremely useful to understand, say....which language most of your users use, etc. But you don't need a 24/7 service to find out what language people use your device in.

Anyways, here's the Google + Post:

https://plus.google.com/103583939320326217147/posts/GwnzKJijBKj

Here, he has, however, provided a screenshot of your data in action, assuaging the fears of most (we never truly get to see what our data looks like after its sent through the mizteereeus pipez of the interwebz, magically transformed, and then spit back out to an analyst), and he even tells you a bit about what data it collects. What he doesn't say, is why on earth submitting the data once, after installation, in a single report wont do, or why a build report once a week, or however often, wont do.

That's the end of my tinfoil hat tirade. Like i said, i love CM, i trust them, but i'm disappointed. The reasons i listed above are arguments made to explain why people are raising hell because of this. I don't believe they'll do anything nefarious, and personally, they can ego=surf with my data all they want. It IS pretty cool. Maybe the move was a tad bit short-sighted though, because they may have gotten a bit out of touch with their users, and their users opinion of them-- and that's what my posts were supposed to do...they were supposed to bring the way I (and other's) think about them more in line with reality.

Edit: It's important to note that, as explained to us by CM, CM Statistics calls home upon reboot. Whether it runs all the time, or just for a nanosecond upon reboot, or 24/7 is important as well, but I'm unable to verify any of this, because my github skills are w34ks4uce. If we had a independent dev who could take a look at CM Stats and then explain exactly (key word) what it was collecting, that'd be über helpful....but it wouldn't mean anything in the long run. Because I was viewing the macroscopic effects of the decision. A comprehensive announcement and explanation wold probably have been prescient, because the information contained in the Google+ post is just as key as the announcement itself-- the stigma of collecting data is far to strong to just say one day-- "sneaky, sneaky--no more opting out".