Facebook Submit compliance check screencast
General questions and topics about hsnm

Rate this topic
   Post Reply
2 posts   •   Page 1 of 1
kostas2911
Posts: 17
Joined: 29 Mar 2018, 11:31

Facebook Submit compliance check screencast

by kostas2911 » 01 Oct 2021, 09:02

Hello I got a mail from Facebook for Developers asking for a compliance check screencast.

Do you have a guide for how to create it?
Below is the actual email received.

==============================================================================

[Action needed] Submit compliance check screencast


To keep the Facebook platform and community safe, we periodically review apps for compliance. To show how <APP> is using its current permissions, please record a screencast showing how users log into your app and how to use your app to test each of your app’s permissions. Submitting this screencast by <DATE> is required in order to maintain platform access.
This screencast is a compliance review requirement to help us learn about your processes to make sure that you’re safeguarding user data and following our Platform Terms and Developer Policies. If your app is not complying with our Platform Terms and Developer Policies, your app’s API access will be deactivated.
What to include in your screencast
Your app name, app ID and app icon.
Your complete Facebook Login flow (if you’ve implemented Facebook Login, show an app user locating the Facebook Login button).
Your app’s account creation and login flow, if your app users can create accounts and log into your app without using Facebook Login.
For each permission that your app has access to, show an app user accessing data that requires the permission, as well as what your app does with that data.
A Facebook Login flow that shows what happens when an app user denies a permission that your app asks for.
The location of your privacy policy in your app. Click the link to your privacy policy to show your policy’s content.
Content inside your app.
Social plugins, if any, and how they are being used. For example, liking or following Pages, sharing content on Facebook or inviting or tagging friends.
If your app is available on different platforms (Connect, iOS, Android, Canvas...), please make sure to show all of the information above for each of these platforms in the screencast.
Note: if your app does not have a user interface, refer to this example screencast for server-to-server apps.
Technical requirements
Your screencast can be up to 45 minutes long.
Your screencast should be a MOV, MP4, MPG, MKV, AVI or M4V file.
Do not include music or voice-overs. Our reviewers will not listen to audio.
Keep in mind
Before you start a recording, log out of any test accounts.
You do not need to show us your app’s code.
Only include test users and test data. Do not show personal identifiable information (PII).
Record only what we need to see. If your app is not full screen, make it full screen or just record the window itself.
Zoom in. If your screencast has sections where it’s difficult to see what's happening, zoom in to make them easier to see.
Annotate your screencast. Annotations are text and graphic overlays that allow you to provide notes for specific areas in a video. Annotations are a great way to highlight parts of your recording that show your app using a specific permission. Most dedicated screen recording software and video editing software includes tools for adding annotations to your screen recordings.
You will only be able to upload one screencast. Make sure your screencast is complete before you submit it.
For more information on how to record your screencast and what to include in your recording, review our screen recordings guide. If you need further assistance, please reach out to platformcompliance@fb.com.
Please submit your screencast by <DATE>. If you don’t submit a screencast by this date, API access for <APP> will be deactivated.

HSNMSupport
Posts: 1529
Joined: 26 Jul 2016, 09:16

Re: Facebook Submit compliance check screencast

by HSNMSupport » 01 Oct 2021, 09:27

Dear Kostas,
we do receive this periodical Facebook email to let them verify our Login App.
We solve this by sending them an email like this:

Hi Support,
HSNM_URL is an Hotspot service on premises so it cannot work without parameters in the url.
https://HSNM_URL/portal/index.php?GatewayID=14 is the url of our Internal Hotspot.
https://HSNM_URL/ is the backend url to mange the Hotspot service.
http://www.YOUR_SITE.com/ is the corporate site.
We use our facebook app to allow Social login in the hotspot service. You can try it here: https://HSNM_URL/portal/index.php?GatewayID=14 has you already done.
Have a nice day.
YOUR_NAME

After their verification, our App is set as verified and it works with 1 Year limitation, when this process needs to be done again.

Rate this topic

Who is online

Users browsing this forum: No registered users and 5 guests

It is currently 29 Mar 2024, 16:05