Hello there ![]()
We started developing an RTMS App that should allow our customers to import audio of their Zoom Meetings (and Webinars) into our system.
The basic idea is: the customer registers the meeting ID he wants to import with us and installs our Zoom RTMS app; when he starts a meeting, we receive the meeting_started callback and if the meeting id is registered with us, we send a patch request to /v2/live_meetings/#{meeting_id}/rtms_app/status to enable RTMS. I’d then expect to get back an rtms_started event and then can negotiate to get media via the websockets. If we get an rtms_started event for a meeting not registered with us, we explicitely send stop to aforementioned rtms_app/status endpoint.
I’ve got a basic prototype up and running in “Local Test” mode, and it works. However, when adding/installing the app I see a lot of different data categories mentioned under “Types of data »Test App« will access”:
Calendars
Content
Functional
Participant Profile & Contact Information
Product Usage
Profile & Contact Information
Registration Information
Settings
Content
Participants
Registration & Scheduling
Account Information
The app has no surface and only these scopes:
meeting:read:meeting ← get meeting started event if rtms autostart is inactive, required to start rtms manually
meeting:read:meeting_audio ← get meeting audio via rtms
webinar:read:webinar ← same for webinar
webinar:read:audio ← same for webinar
rtms:read:rtms_started ← get rtms events
rtms:read:rtms_stopped
meeting:update:participant_rtms_app_status ← start/stop rtms manually if autostart not enabled
which I believe are required to implement the data/control flow mentioned above – please correct me if I’m wrong.
We don’t do anything with Calendards, Profile, Participant, etc .. and don’t even want to be able to access those as it would make me myself as our customer using the plugin (rightfully?) a little suspicious of how much data our Zoom app wants to access.
So my questions are: why is so much data mentioned that our app can access, can we limit that and how, and is that a problem during review?
Thank you very much!
Best, Chris