You can trust DigitalOcean for the same reason you may trust Google, Microsoft, Amazon, Samsung, Intel, IBM, etc. You can evaluate their privacy policy against their history as a company, and mitigate the risk for whatever data you decide to host on their services.

Bugsnag has a well defined API and you can see here both the usage in code and the purpose of the user tracking feature: http://docs.bugsnag.com/platforms/browsers/#identifying-users

If you then click on http://docs.bugsnag.com/api/deploy-tracking/ (in that documentation), you’ll see the releaseStage parameter’s purpose which is simply to track if you’re using the production panel or something else.

bugsnag.com’s API is accessible over HTTPS so your information wouldn’t be seen even if you were using public WiFi.

segment.io is a data analytics API used to track customers. This isn’t uncommon for companies with a very large user base.

customer.io, however, is a messaging API. It uses analytics to perform its tasks, but there’s nothing inherently malicious about it.

At this point it’s not obvious if you bothered to check if anything you brought up was actually untrustworthy. Looking at the domain and deciding if it looks scary seems to be the deciding factor more than actual risk.

I think I should have used the following as my question.

Do you think DigitalOcean sending my logon id to a third party website is considered good business ethics given the logon id is the property of the customer ?

My apologies for that confusion.

Thank you gparent for your clarifications. Believe me, I wasn’t scared of the domain name, or anything it isn’t.