Data doesn't have to be readable. Often, preprocessed datasets are totally incomprehensible for everyone except whoever prepared it. Multiple fields are combined into composites, rescaled, transposed, etc.
You're providing a lot of entropy to a body that has even more sitting around. If anyone could find some part of a dataset that might be sufficient to deanonymize your data Google could.
Not saying you need to be so paranoid, just that non-readability of data might be comparable to obfuscating your javascript to keep people from prying into your code.
At least to a sufficiently knowledgeable corporation.
Comments
Data doesn't have to be readable. Often, preprocessed datasets are totally incomprehensible for everyone except whoever prepared it. Multiple fields are combined into composites, rescaled, transposed, etc.
You're providing a lot of entropy to a body that has even more sitting around. If anyone could find some part of a dataset that might be sufficient to deanonymize your data Google could.
Not saying you need to be so paranoid, just that non-readability of data might be comparable to obfuscating your javascript to keep people from prying into your code.
At least to a sufficiently knowledgeable corporation.
Agreed -- look at their own example data:
wine,5,1,1 no-wine,0,0,10
This data is meaningless to anyone who doesn't know what the columns mean, and you don't have to tell that to Google.
And you can of course replace the labels with any other text you want without affecting the algorithm.