Only for the client to have found this very thread. I've deployed 6 systems with extensive Push Bullet notifications, each having to have paid $150 to a 3rd party driver developer who had created a driver to allow the Home system to talk to Push Bullet accounts. That means rolling trucks and 1-2 hours of programming This means I'll need to go with the Push-Over service, pay another $150 for their driver (made by another 3rd party driver developer) and reprogram each existing system. Total: $600 x 6 existing projects + reprogramming of my original template file $300 = $3,900. So, thanks very much Push Bullet for 0 notice and this expense. You have a great service and I wish you guys would reconsider the update to the iOS app, willing to donate. IOS doesn't have the same side-loading functionality as Android does. As Oldenburg notes, this is pretty bizarre offense to be called upon as the app didn't get flagged for these violations in the weeks or months prior.You'd need to jailbreak the device and even then that's just the start down the rabbit hole. This time around, the team was dinged for not providing disclosure about when email addresses are sent to Pushbullet's servers while using a Google account to sign in. The latest notification came about on October 26 (shown below).
The Pushbullet team then submitted the update and that was later approved. To remedy this, the developer decided to write a new policy that combines all disclosures while also mentioning it within the Play Console.
More time passes by until yet another dreaded notification arrived earlier this month claiming the privacy policy disclosure is not mentioned in the Play Console.
At a loss for solutions, the company simply proceeded to increase the text size of the in-app Privacy Policy link and successfully submitted the update. Another notification arrives on May 15, with similar violations as the others, but this time pertaining to SMS Log information.
0 kommentar(er)
