291–300 of 501 posts
https://support.google.com/googleplay/android-developer/answ...
I know a group of devs collaborating on a side project. Same thing happened to them. They created a new developer account for this project, worked together on it, and the app vanished off the store and dev account terminated, along with one of the developer's personal developer account. They assumed, but don't know, it was because the developer who had his personal account suspended as well once worked for a company…
My question, is there some statistical support for this? I scummy company employees tend to trend towards scummy stuff? No doubt lots of false positives, but folks keep on seeing this as a "mistake" google is making, and google may not think this type of associative banning is actually a mistake.
Omelas aside, I think of this every time I read about someone's work or life or memories or whatever just getting zapped by Google, for a reason that is probably contained in a 500kb EULA, but one you will never find. It's free! You can do all of this stuff! It's great! Except for when your stuff gets randomly eaten.
Earlier quoted context omitted.
I had a scare last year where Google supposedly gave me 30 days before they would shut off my Google account of 20yrs. Family photos, youtube videos, 20yrs of email, not to mention the treasure trove of personal documents on GDrive. It took two weeks to duplicate the content and back it up elsewhere. This is a paid tier Google account and I've yet to get an explanation on why this happened. It appears to be because o…
Customer service? For a Google account?
Earlier quoted context omitted.
GDPR Article 22 > The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her. > In the cases referred to in points (a) and (c) of paragraph 2, the data controller shall implement suitable measures to safeguard the data subject’s rights and freedoms and…
GDPR Art. 4: „ personal data’ means any information relating to an identified or identifiable natural person (‘data subject’)“. This is a business, not a natural person.
In the discussion of the last article, there was a discussion about weaponizing "associated accounts" when Google shuts things down. Looks like it's 100% a valid tactic. Looks like you need to make sure your employees all leave on good terms, and stay on good terms in the coming years. Otherwise, you too might find your Google accounts terminated with no recourse.
Earlier quoted context omitted.
I suppose the best practice solution to this is to try to keep company Google Play accounts as "sterile" as possible? Give access to as few employees as possible, and have all access to Google Play go through a designated, trusted release manager or "play account manager"? And don't log in to Google Play from random browsers and IP addresses which could create an association with other Google accounts?
Or just don't link personal and company accounts . Even these issues aside , there are so many reasons to keep them separate and unrelated. That's not unique to Google but goes for GitHub, AWS, and whatever else. Use company e-mail addresses to register for everything. Enforce it for your employees. This is in the interest of both the company and the employee. Yes, the summer intern gets a corp email too, which at mi…
I know a group of devs collaborating on a side project. Same thing happened to them. They created a new developer account for this project, worked together on it, and the app vanished off the store and dev account terminated, along with one of the developer's personal developer account. They assumed, but don't know, it was because the developer who had his personal account suspended as well once worked for a company…
My question, is there some statistical support for this? I scummy company employees tend to trend towards scummy stuff? No doubt lots of false positives, but folks keep on seeing this as a "mistake" google is making, and google may not think this type of associative banning is actually a mistake.
I think the problem is the only solid connection google has are developer accounts / that's the only club they have to swing. So bad actors may jump from account to account and Google's method of whack a mole is to just associate accounts.
Way back in the day I worked on an old forum where we used to try to do that for spammers and such. But we didn't automate it. We just had a checking mechanism that would indicate if some accounts might be from the same person ... maybe.
But beyond anecdotes and the above story I've no idea how widespread this is.