1. Disconnect in Studio
Open your client’s Publishing connections and choose Disconnect for the selected platform. If VEXO manages your publishing, ask the workspace account manager or order@vexoent.com to disconnect it. This removes the saved connection credential. Future sends require a new authorized connection. Existing provider posts are not deleted by disconnecting.
2. Revoke provider access
You can remove the provider’s grant directly in Google account connections or Facebook business integrations. Review the provider’s notice: removing an app may affect other connections using the same app grant.
3. Request deletion of retained information
Email order@vexoent.com with the subject “Studio publishing data deletion.” Identify the Studio workspace or business, the platform and the account or channel name, and the information you want removed. Send the request from the authorized account email when possible. Do not include passwords, API secrets, tokens, payment details or identity documents.
VEXO will verify the request and its scope, remove applicable retained platform information and explain any information that must remain for legal, accounting or security requirements. We will confirm completion or explain the remaining steps. Provider posts and videos must also be managed on the provider if you want them removed there. Recovery copies follow their retention rules and are not an active publishing connection.
Private test cleanup
The restricted Vexo Team YouTube test has a separate Disconnect QA channel control. It removes the local channel credential, consent attempts and transfer record. Its generated clip and private YouTube video are test artifacts; disconnecting does not delete the video from YouTube. The Meta QA Disconnect control removes its local account token and pending consent attempts. It retains test receipts and the dedicated developer credential to prevent accidental duplicate sends. Its public test posts must be deleted on Facebook and Instagram. The dedicated QA developer credentials remain in the encrypted vault; contact the Vexo Team or VEXO support for their removal.
