Thank you for your patience. The answers you want are in bold. Let me know if you need further clarification.
- Among the items in the checklist that require explanations or documentation, which ones need to be submitted in English? Are there any that can be in Japanese?It was mentioned that the app description must be in English to avoid review comments, but there is no clarification for other items.
You must include a note in bold at the top of your Long Description that the app is only for that region/language. Your Short and Long description information must be in English, or contain an English description directly following any content in the foreign language provided.
- 1-a. Especially, can the Terms of use and Privacy Policy be submitted in Japanese?
If you include the language disclaimer, we can accept resource content (Privacy Policy, Zoom Documentation, and Support Page) in the specified language.
- Can apps of types other than General App also undergo the review process?
Yes, if they were originally created as a legacy app
- 2-a. If a new General App needs to be created, is there a designated transition period from the old app to the new app?
We accept legacy app submissions, but all apps will be asked to convert to General app in the future
- Regarding checklist items 7 and 13, our app does not distribute online and we install it on devices ourselves using adb commands. Do we still need to provide documentation on how to add the app or a landing page?
Landing Page = Yes, the landing page should inform users how to begin the purchase/enablement process, if they need to contact your team to do so, the landing page should specify this.
Documentation Page = Yes, if the user encounters any issues after enablement, this serves as a resource for them. Additionally, users need to be provided instructions on how to deauthorize app access to their Zoom account should they need to
- We plan to set up a development server to comply with checklist item 8. Are there any specific requirements for this?
Deauthorization URL is optional, documentation will be updated to say, âTo do so, apps may provide a secure endpointâ
- Regarding checklist item 8, what should be done upon receiving a notification for authentication revocation?
You should delete the specified userâs Zoom data from your systems in accordance with your Privacy Policy and TOU
https://developers.zoom.us/docs/integrations/end-user-auth/#deauthorization
- Regarding checklist item 9, we have separately created a Webhook in February 2022, and the Meeting SDK app is designed not to directly integrate with the Webhook. In this case, is it necessary to configure Event Subscriptions?
It is only necessary if your Meeting SDK app is long-polling our API or making scheduled GET requests every X minutes. If you are not doing this, web hooks are not required, but recommended
- Regarding checklist items 11 and 12, Do we need to provide OAuth URL settings and flows even if we havenât created an OAuth App?Our app only allows guest participation, and we do not require authentication for joining meeting. While we have implemented JWT generation and usage similar to the link provided, we do not utilize OAuth flows or ZAK tokens.
No you do not, we will update this doc to reflect SDK requirements
- Regarding the UI legal notices requirement for the Meeting SDK app, how should we handle devices without displays?Since the devices do not have displays, users cannot view the UI or access the meeting chat. Therefore, we cannot display various notices to the users and have implemented automatic consent if prompted. For commercial use, we explain the data usage to customers and obtain their consent.
UI legal notices are for other participants who may be joining the meeting from a regular device. If your SDK app is in the call, it needs to notify the other participants via AAN