# Published user-managed General App: deauthorization setup, verification and data deletion

**URL:** <https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816>\
**Category:** API and Webhooks\
**Created:** [November 9, 2026, 1:53pm UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816 "2026-11-09T13:53:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [November 12, 2026, 1:35am UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816/2 "2026-11-12T01:35:34Z")

</div>

For configuration, set the dedicated deauthorization URL under **[Production → App Listing → Links & Support](https://devforum.zoom.us/t/new-build-flow-cannot-find-deauthorization-notification-endpoint-url-field-for-oauth-app/111942/2)**[, at the bottom](https://devforum.zoom.us/t/new-build-flow-cannot-find-deauthorization-notification-endpoint-url-field-for-oauth-app/111942/2). This setting is separate from Event Subscriptions. For a published app, [submit the change through **Send Updates** for review](https://developers.zoom.us/docs/distribute/published-apps/updating/). Saving the field alone does not update the production callback.

You can [request verification](https://developers.zoom.us/docs/api/webhooks/) by computing `v0=` plus the hex HMAC-SHA256 of `v0:{x-zm-request-timestamp}:{raw_body}`, keyed with your app’s webhook Secret Token from **Features → Access**. Compare that with `x-zm-signature`. Use the original request body bytes. `payload.signature` is the uninstall event’s identifier, not the cryptographic signature. I’d use it for deduplication separately from authenticating each delivery.

For data deletion, I’d include saved join URLs in your cleanup inventory alongside tokens and Zoom profile identifiers. For data you need to delete, remove it from your app/database. According to earlier staff guidance, [the Zoom meetings themselves need not be deleted](https://devforum.zoom.us/t/deauthorisation-api/20055/2). That distinction doesn’t establish an exemption allowing join URLs to be retained.

Recall.ai also offers a [Meeting Bot API](https://www.recall.ai/product/meeting-bot-api?utm_source=zoom&utm_medium=forum_answer) for bot-based meeting capture.

---

_[View the full topic](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816)._
