My team has built an app that uses the Azure Face Detection API to upload a user's selfie and return some basic info. We POST this information to the West Europe server, as described on this page (https://westus.dev.cognitive.microsoft.com/docs/services/563879b61984550e40cbbe8d/operations/563879b61984550f30395236)
I need to understand what happens to the image data in terms of storage, retention, generated metadata, etc. - essentially all info around GDPR requirements. I understand from this page (https://azure.microsoft.com/en-us/blog/microsoft-updates-cognitive-services-terms/) that "Cognitive Services customers own, and can manage and delete their customer data" but I cannot see where I can manage this data in the Azure console. I have also looked in the following places without luck:
https://www.microsoft.com/en-us/licensing/product-licensing/products
https://privacy.microsoft.com/en-gb/privacystatement
Can anyone show me where I can manage this data, or a privacy document outlining default behaviour around privacy please?
Thanks
Ferg
Related
We're looking into integrating with LinkedIn so that we can feed our users with lists of job candidates, and then send our users back to LinkedIn in order to view relevant profiles. I'm not seeing any relevant API docs regarding this. Is this something that is possible to do via your API today or in the near future?
Right now, LinkedIn gives only the scope of r_liteprofile and r_emailaddress to Retrieve authenticated member's name, headline, photo, and member's primary email address.
To get the relevant candidate for the job, you may need to check skills, projects, etc, for that you need the permission of r_fullprofile,
LinkedIn API has restricted such information as per their documentation:
https://learn.microsoft.com/en-us/linkedin/shared/references/v2/profile/full-profile
As per their documentation, to access the information of skills, address, etc, your app needs to request r_fullprofile. But they have closed it now and no alternate is given. The more detail about the current permissions from LinkedIn can be seen here:
https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access
Right now there are currently in development mode. They are working on developing their APIs. What and when they will release such information is not available to document right now.
I want to create a webpage where users can access their education records from LinkedIn (which are then plotted on a timeline).
Using OAuth, I was only able to access my Name and Profile picture. It seems like LinkedIn heavily restricts access, even if users give their explicit consent. I don't see any way to request the scopes needed to request the education section of my profile. A similar experience is also outlined in this medium article:
The frustrations of dealing with the LinkedIn API
Alternatively, people have suggested using Selenium to scrape the public profiles of users. However, LinkedIn has taken up multiple legal fights against scrapers, so obviously they are not ok with it.
Considering that I want to build a service that benefits LinkedIn users and that I only want to access information of users that give their explicit consent to do so, it seems odd to me that this should not be possible on LinkedIn. Is there any way of doing this in 2023? I know similar questions have been asked before, but LinkedIn changed their policy quite a few times as far as I'm aware and previous questions date back many years.
Years ago, someone asked on Stack Overflow if it were possible to retrieve a list of all employees who work at a company. I can do this through the LinkedIn UI, but I cannot seem to find any mechanism for this using the v2 API. The SO response mentions this used to be possible on the v1 API, but you had to request access through LinkedIn's "Vetted API Access Program." Unfortunately, the link on this response is now obsolete and does not send users to any such program.
How could I apply for this program nowadays? This is a specific situation to me and my company, so I would very much like to discuss this with someone at LinkedIn if some form of this Vetted API Access Program still exists. I do not wish to disclose the details of this request to the open internet.
I have confirmed through contacts inside LinkedIn that this API functionality has been removed. No further information has been provided, and LinkedIn tech support refuses to comment any more on this issue. Furthermore, no LinkedIn engineers will comment on this thread here.
This is bizarre since any regular user can do this functionality through the web front-end, but for some reason LinkedIn believes this would be a violation of privacy/security if we could do this programmatically.
Therefore, the only way to obtain this data would be through screen scraping. I wish I had better news, and I wish that LinkedIn would provide some reasoning for their changes, but alas this is where we are.
I just posted a very similar question because I ran into the same problem as you.
The application forms for Linkedin's current partner programs seem to be located here, however I can't tell you which one of those programs comes with the necessary API access rights and I am in general not sure if this API request is still allowed.
Edit: The Linkedin Help page states that applications for partner programs are currently unavailable?
In general, you can get a list of employees of a company if you scrape Linkedin profiles exhaustively, or if you have an exhaustive dataset of Linkedin profiles.
Each Linkedin profile contains a list of experiences that links to the company profile URL.
Thereafter, you will filter the dataset into profiles currently working at X company to get a list of employees currently working in a company. The same technique can also be used to retrieve a list of past employees.
And that is what we did. We scraped all public Linkedin profiles based in the US and made an alternative API known as Proxycurl Employee Listing API to Linkedin API to provide employee listing functionality.
Proxycurl's Employee Listing API will never be as exhaustive as Linkedin's dataset because not all profiles are made public, but most are. But will suffice to meet your needs.
I'm starting with google analitycs.
Before I'll start implementing this into my pages I'm wondering if I'm able to get informations like average time at site, where my user came from, which devices they are using etc.
I would like to get those information from my VueJS front SPA application by async HTTP GET call and display those there. Is it possible?
If yes I would be very thankful if you provide some links to google API where I can find it or some tutorial.
Since Universal GA you can't access users' origin data outside GA in your application. Before that you had all this juicy information inside a cookie, inside __utma, __utmz etc (more info here).
The information you're asking about (time on site, pages visited, etc) can be retrieved from GA afterwards if you make use of the userid feature.
I'm working on the architecture for a project that includes a Android and iOS apps and a web interface with a subset of the mobile apps functionalities. The project is basically a e-commerce solution. In all three interfaces I'm using Google Analytics to track some information. However I'm having an internal discussion about the extent of the information I should send to GA. What should I store in GA and what should I store in my own server?
Let me give you some examples.
Session tracking is clearly something that belong to GA.
ProductDetailViews. Sounds like something that should go into GA, specially considering the enhanced e-commerce module.
Shared item. When a user shares some content over a social network, should I store that information on GA or in my own server? I'm inclined to GA but it becomes more ambiguos.
Do you see my point? Can someone share a general rule or recommendation on what should be saved in GA and what should be saved on the projects own server?
Thanks
For those examples I would generally send all the hits to Google Analytics. Here are a few reasons:
Preventing data silos. You want all of your data in one place and Google provides you with a database reachable via the API where you can keep all your data organised in one place. This is important when you are considering measuring performance, as you want to avoid duplication of conversions or traffic hits
Useage of Google Analytics advanced segments. With all your data in GA, you will be able to create advanced segments for analysis. But the real power is if you are using AdWords or retargeting, as you can send those Advanced Segments to AdWords, and target those users around the web with your custom data
Single point of reference for users All analytics are inaccurate, but you want to make sure they are inaccurate to the same degree. Using GA keeps all your data on the same playing field
Usability and Freedom of information Its easier to serve up your data to users within the GA interface as people are more likely to know how to navigate that than your database. You can also use the GA API to pull out any data you need to push into other visualisation tools.
User session merging With your data and userID tracking in GA, you may be able to track users as they arrive via mobile to desktop and back again, over multiple sessions.
What you need to avoid putting in to Google Analytics is personal info such as names, email address etc. There are against the TOS. But you can capture a unique userID, and match that outside of the tool later.