You grant to Microsoft and will secure and maintain all rights in the Data necessary for us to: ... (iv) improve the Service Components and other Microsoft products and services
http://research.microsoft.com/en-us/um/legal/CognitiveServic...
Google Vision API:
5.2 Use of Customer Data. Google will not access or use Customer Data, except as necessary to provide the Services to Customer.
a) You see little chance of remaining relevant in your field without biting the bullet & providing training data as part of the package deal
b) You see "product/service takes off" as a far off dream, with many near-term wins that will make the tradeoff worth it for you. For now. And that has to be good enough.
c) You wonder aloud what kind of data that might be, that could be combined into something else, along with your data. Your best strategy people tell you it's not worth getting bothered over, given the nature of your project. Now is the time to take risks.
> In other words, why would anyone invest in ML as a service with so many potential forces acting against your continued success?
Because those "forces" are wayyyy out there compared to the bigger risk, namely "not having any better ideas"
Nobody said MS has to market this to companies that see MS as a potential competitor.
For the vast amount of companies where ML isn't in any way core, this is great. For example we've got a little internal app that includes a profile picture.
Currently we pre-crop photos before uploading. Obviously not the best solution. Putting together a little javascript thingy to allow the user to crop is somewhere deep in the backlog. Now this exists I'm very tempted to implement a little feature to auto crop around the face on upload. Nothing there to steal, definitely not worth rolling our own ML system to do it but a very nice thing to now be available in our toolkit.
http://docs.opencv.org/2.4/modules/contrib/doc/facerec/tutor...
I saw some demos of M$FT's apis at a recent tech event and it wasn't obvious that the results with their system were significantly better. The biggest hole seemed to be that camera frames were being sent to the cloud, and there were issues with the presenter's quota (forget the exact problem).
But overall, I think the Cognitive Services are a step in the right direction. They generally make sense for businesses who don't have a full-time team of ML/CV experts.
There are serious companies (like Netflix) that put their entire infrastructure on cloud platforms. If the concerns the OP raises are valid, no company for whom ML is a big (read: high usage, high paying) feature is going to rely on these cloud services. And startups that do rely on the cloud services for their MVPs are going to move off as quickly as they can. I can't think of any successful cloud platform for which MVPs and small features are the main customer use case. Heroku comes to mind, but even then there are mid-size companies that do rely mostly on Heroku.
But also - what happens when you wish to expand and grow? My guess is, if this capability was developed in house, you would almost certainly find it easier to not just scale without incurring a "success tax", but most importantly you are now exposed to the deep bowels of the ML process which should certainly give you far greater insight into potential tangentially related services.
An example: you use a natural language processing API and get all the brand mentions in some text the customer has submitted - certainly a useful service for competitive research. As your company scales, now you are more or less beholden to the ML service - if nothing else at least for the consistency of results, which is likely to make you super cautious about rolling your own. But you don't know how the results (brand mentions) were actually inferred. If you were to ask, "Hmm.. what other types of entities can I extract and have it be more useful for our customers? What about only getting brand mentions if it is in the same paragraph as a complaint?" - you might face some options which you might not really like - for one, the way the ML API is structured might actually make this operation expensive (after all, the data is pretty adjacent before being sent to the ML API, but not necessarily so once it is processed). Also, since you never understood how the brand mentions were extracted, it is very likely you are missing out on a ton of insight you could gain by rolling out your own capabilities.
And not to mention: if the ML capability has been outsourced, and if ML is indeed going to drastically impact your industry, then you would certainly not want to be in the position where your competitor can easily disrupt you merely because they spent the time to develop such capabilities in house.
For example, it could just be that ML is not your business. If you're a image hosting platform, you don't necessarily want to build your own NSFW image checker. There's no harm in leveraging something else out there that works great, assuming that you can bankroll it.
Alternatively it can be used as a stop-gap. You're in the middle of implementing your own ML system (or planning to), but you can use a 3rd party to fill the gap until you're ready to go live with your own version.
This is also a great way to test new features and see if users respond to it.
In my opinion it boils down to if either you need to own the model, or guarantee the quality of it, then perhaps you should consider owning it yourself. Otherwise, it's fine to consider using a third party.
Anyway, there are many more obvious use cases. Other apps/games/services that need to detect faces or filter out porn and so on. Imagine a dating site that estimates age and more based on photos, while also filtering out NSFW images.
While I am just treating this as a research project, some of the content is from Youtube, so they are effectively a competitor. Google has been using their speech recognition to help the Youtube search (which has helped me), but they so much data that it's hard for them to solve niche use cases.
I've always wondered if there is anything stopping this data from being used to inform market opportunities for Amazon, Google or Microsoft.
I share your scepticism though.
a) you are providing a lot of training data and instead of being paid for the service, you are actually paying for the privilege?
b) if your product/service takes off, there is a higher chance you will be competing not against similar startups, but rather a feature of the same company to which you just supplied all this training data (after all, you just helped them - in fact you paid them - to identify new markets for their service)
c) and hey, that data can also be combined with other data you do not have access to (in the worst case, it is remaining data which was supplied by your direct competitor and effectively completed the picture for the big company)
In other words, why would anyone invest in ML as a service with so many potential forces acting against your continued success?
To be clear, I don't refer to using the cloud services provided by these companies, which are often a lot more useful, because there are explicit clauses to prevent them from using your data for training(as I understand it).