# For Published Zoom Apps -- Privacy Attestations

**URL:** <https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360>\
**Category:** Zoom Apps\
**Created:** [December 15, 2022, 5:47pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360 "2022-12-15T17:47:09Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [December 15, 2022, 5:47pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/1 "2022-12-15T17:47:09Z")

</div>

As part of our continual efforts to protect our users’ privacy, Zoom is requiring all developers to attest to how user data is processed. This information will need to be updated in your app/integration’s technical design document (TDD). It is important that you submit an updated TDD with completed data privacy questions by February 28th, 2023. Failure to complete the updated TDD by this deadline will result in the suspension of your app/integration from the Zoom App Marketplace. You can look at the FAQ here ([https://devsupport.zoom.us/hc/en-us/articles/10809580015757-FAQ-on-Privacy-Embedded-TDD](https://devsupport.zoom.us/hc/en-us/articles/10809580015757-FAQ-on-Privacy-Embedded-TDD)). I will be on next week’s Zoom Apps Developer Office Hours to answer any questions that you all might have.

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [December 15, 2022, 5:47pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/2 "2022-12-15T17:47:54Z")

</div>

Pinned on December 15, 2022, 5:47pm UTC



---

<div class="post-metadata">

**Author:** ![EthanBetafi](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethanbetafi/32/32032_2.png) [@EthanBetafi](https://devforum.zoom.us/u/EthanBetafi)\
**Post date:** [January 25, 2023, 7:39am UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/3 "2023-01-25T07:39:33Z")

</div>

We submitted an update to our app last week with the Privacy Attestation filled out & transitioned to the new more secure verified webhooks setup.

We were surprised to see an estimated 4+ week review backlog estimate. Is the 4+ weeks estimated app review queue timeline accurate for updates to existing marketplace apps? Or just generic boilerplate upper bound estimate mostly targeted at new Zoom Apps?

TBC: Is there a different review queue for small incremental updates for existing approved apps like this focused on security & metadata/attestation improvements? Or for marketing-only updates?

Or should we indeed expect average review times of ~ a month every time we push out a minor update?

Thanks & appreciate the clarification on this,  
Ethan

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [January 25, 2023, 5:14pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/4 "2023-01-25T17:14:21Z")

</div>

Thank you for filling out the attestations. I will check with the QA team and give you a timeframe you can expect an approval.

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [January 25, 2023, 7:35pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/5 "2023-01-25T19:35:41Z")

</div>

Ethan, you are correct that is boilerplate language and represents the upper bound estimate for new Zoom Apps. Although, I’m sorry that I don’t have any estimates on incremental changes that you spoke of in your message.

---

<div class="post-metadata">

**Author:** ![lsubotky](https://avatars.discourse-cdn.com/v4/letter/l/e19b73/32.png) [@lsubotky](https://devforum.zoom.us/u/lsubotky)\
**Post date:** [January 27, 2023, 11:28am UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/6 "2023-01-27T11:28:04Z")

</div>

Hi Shariq. We submitted our app in December and I think the new attestation process may have already been in place at that time. Can you check to see if we’ve completed the requirements or we need to re-submit?

---

<div class="post-metadata">

**Author:** ![richardp](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/richardp/32/33271_2.png) [@richardp](https://devforum.zoom.us/u/richardp)\
**Post date:** [January 27, 2023, 5:13pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/7 "2023-01-27T17:13:52Z")

</div>

Hello, I’m a little confused-- we completed the TDD. Does this mean we now need to re-submit the app, or is simply filling out the TDD all we need to do?

Richard

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 27, 2023, 9:45pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/8 "2023-01-27T21:45:05Z")

</div>

Hi @richardp  
In order for us to have your updated TDD, you will have to submit your app for an update, please.

---

<div class="post-metadata">

**Author:** ![it.stuff](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/it.stuff/32/44994_2.png) [@it.stuff](https://devforum.zoom.us/u/it.stuff)\
**Post date:** [January 28, 2023, 3:23pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/9 "2023-01-28T15:23:10Z")

</div>

Hi Elisa, we resubmitted our App late last year with some updates. Can you check if it has been cleared through this new update resubmission process.  
Thank you!

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [January 31, 2023, 10:50pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/10 "2023-01-31T22:50:40Z")

</div>

The new privacy questions and TDD were released early December. If your update came before that, then you will have to answer those privacy questions.

---

<div class="post-metadata">

**Author:** ![Tatsuro](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Tatsuro](https://devforum.zoom.us/u/Tatsuro)\
**Post date:** [February 21, 2023, 10:07am UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/11 "2023-02-21T10:07:17Z")

</div>

> [@shariq.torres](#):
>
> Failure to complete the updated TDD by this deadline will result in the suspension of your app/integration from the Zoom App Marketplace

Hi. What does ‘suspension’ mean? If the app uses zoom api (e.g. create meeting api) , will the requests of api fail after February 28th ?

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [February 21, 2023, 6:50pm UTC](https://devforum.zoom.us/t/for-published-zoom-apps-privacy-attestations/80360/12 "2023-02-21T18:50:14Z")

</div>

Suspension means that your app will removed from the Marketplace and no new users can add it. The Zoom App will continue to work as normal. This gives you a chance to update your TDD. The final step would be to disable your Zoom App altogether.

[You can read about suspensions and disabling policies here.](https://marketplace.zoom.us/docs/guides/publishing/app-submission/suspend-disable-app/)
