Dispatch stores the data described in our Privacy Policy. Here is how to have it deleted, depending on who you are.
Use Channels → Disconnect Threads to remove the locally stored access token and authorization details and stop future Dispatch posts to that account. If a post is being published, wait for it to finish and retry. The account identity and publishing history remain in your workspace; use the deletion request process above to remove workspace data.
Local disconnect does not revoke the grant on Meta's side or delete posts already published on Threads. To revoke access separately, remove Dheeraj Social (Dispatch) in Threads settings → Website permissions. Manage existing Threads posts directly on Threads.
Use Channels → Disconnect and revoke Google access for your YouTube channel. Dispatch stops new uploads immediately and requests Google revocation. Google may also remove other Dispatch permissions for that Google account, including Google sign-in consent. An active upload worker may delay cleanup. If revocation cannot be confirmed, encrypted credentials are used only for retries and local provider data is erased within six days of the request, once any active worker has finished. Remove Dispatch through Google account permissions if the app reports revocation remains unconfirmed. You can also email dheeraj.raikwar224@gmail.com to request removal of stored YouTube data; we process those requests as soon as possible and within seven calendar days. The same deadline applies when you ask to delete your entire workspace and to YouTube provider data in older backups; ordinary backup rotation does not extend it. Revoking access is also available in Google's security settings. These actions do not remove videos from YouTube. Delete those directly in YouTube Studio. Your own files and drafts in Dispatch are separate from data received from YouTube.