YouTube Compliance

Hi

This is now urgent for me because YouTube compliance are giving me 3 days to work out a quota here:

https://developers.google.com/youtube/v3/determine_quota_cost

I do not know which options to choose.

All we are displaying is my video channel on my site and the users can choose which video(s) to what.

Which choices to I select on this wizard?

Sorry, but we don’t follow what you’re asking. What does that wizard have to do with YouTube/Compliance? What specifically did YouTube mention to you in that email?

Hello Andrew Truckle,
Thank you for working with us on the YouTube API Services Compliance Review. Your response is appreciated.
In order to proceed further and complete the compliance review, kindly refer the Quota Calculator to calculate how much quota you will need based on your API usage.
Please provide us with this information in the next three (3) business days and feel free to reach out to us if you have any questions.
Regards,
YouTube API Compliance Team

What exactly was the email they sent you in regards to your comment here:

I had an email from YouTube and compliance with their policies and I am having to make changes so that I can continue to host my YouTube Channel on my website using your plugin.

This was the original email:

Hi YouTube Developer,

We’re writing to let you know about upcoming changes to the YouTube API Services that will affect API projects created after July 28, 2020.

All videos uploaded via the videos.insert endpoint from unverified API Projects created after this date will be restricted to private viewing mode. To lift this restriction, each project must undergo an audit to verify compliance with the Terms of Service.

Creators who use an affected project to upload video will receive an email explaining that their video is locked as private, and that they can avoid the restriction by using an official or audited service.

Existing API projects will not be affected by this change, but we strongly recommend that all developers complete a compliance audit for their projects to ensure continued access to the YouTube API Services.

Thanks,
YouTube API Services Team

It is because I had to create the API server project so that your plugin can read and display my channel. This will affect all of us.

Hi

I am now using a different plugin called YouTube Showcase (the free version). I had to manually build the list of videos by providing the video ID values. But at least I no longer required a Google Developer Console project to act as a server bridge.

So I no longer have the compliancy issues. Please be aware that anyone using your plugin (based on the dates I have stated) seems like will have to deal with compliancy issues if they want to use the API services (albeit through your plugin) to display their channel.

Andrew

Thank for your feedback. However, you or anyone that has ever used this plugin never had any of the referenced compliance issues since the plugin doesn’t even use the videos.insert endpoint or even upload video content to YouTube servers for that matter. The YouTube API is only used by the plugin to retrieve content like video titles and thumbnails that to create galleries. The email you’ve shared is something that YouTube is broadly sending API key owners. Please re-read the message specifics and see that it’s not applicable to this plugin.

That may be the case. But what I am telling you is that anyone using your plugin, that has this API project, will get this email. They will need to know how to deal with it. The users could be saved alot of time if you maybe tell Google about your product and what it does. So that in the future any user can just say they user your plugin.

I have explained everything that you had told me and it was not sufficient for them. I had to state that I was using their API in my privacy policy (even to read content). So users might have to do something, I don’t know. But it might be in your interests to contact them and clarify and if needs be write a FAQ.

I also admit what you are saying, and you are most likely right!

Thanks for your input.