Data Deletion

Export or download content you need, cancel or finish scheduled publishing, revoke API tokens that should stop immediately and confirm which workspace or account is in scope. Deletion cannot be undone from the active application.

Published-post deletion is provider-dependent. KORD can remove a single live post only where the provider adapter supports verified deletion; otherwise use the social platform's controls. KORD does not delete a social account or unrelated media stored by the provider.

Authorized workspace users can delete media. Unused media is removed completely. If media was already used in a post, KORD removes the stored file while preserving the minimum record needed to explain prior publishing history.

A deletion may be blocked while media is required by a scheduled, pending or publishing post. Resolve that workflow first to prevent a failed post.

An owner or admin with the channel-disconnect permission can choose Remove from KORD on a specific connected profile. Removal clears active OAuth credentials, disables the profile, removes it from publishing groups and disables its automatic posting slots.

KORD blocks removal while that profile has a scheduled, pending-approval or publishing post or an active or waiting queue job. The dialog identifies blocking items so they can be cancelled, moved or completed first.

A disabled profile no longer appears as an active destination. Limited profile and publishing history remains so the workspace can understand earlier posts and reconnect the same external profile without creating a duplicate. Removing a profile from KORD does not revoke a shared provider authorization used by another profile or workspace; revoke access at the provider if you want to stop the provider grant itself.

Disconnect the YouTube profile in KORD to clear its active credentials. You can also revoke KORD on the Google Account permissions page. Revocation stops future API access but does not delete videos stored by YouTube.

To request deletion of YouTube Authorized Data held by KORD, email [email protected] from the connected account or workspace-owner email and identify the workspace and channel. After we receive a verified request or detect revocation, KORD deletes the affected YouTube Authorized Data as soon as possible and no later than seven calendar days, except records applicable law independently requires us to retain.

• Google Account permissions - review and revoke KORD access
• Delete content on YouTube - use YouTube controls for videos stored by YouTube

A workspace owner or another authorized role can use Settings → Danger zone → Delete client or brand and type the exact workspace name. The action removes workspace posts, variants, media records, memberships, settings, API tokens and connected profiles from the active database and deletes its stored media objects.

The service keeps a minimal platform audit event that a workspace was deleted, including its former name, identifier, deletion time, actor and reason. This event does not retain the deleted posts or media.

If a storage object cannot be removed immediately because of a transient infrastructure error, it is no longer referenced by the deleted workspace, the failure is recorded for restricted operational cleanup, and the object is not available through the ordinary product workflow.

Email [email protected] from the account email address. Include the account email, affected workspace names and whether you request account deletion, workspace deletion, provider-data deletion or all of them. We may ask for additional verification and confirmation from a workspace owner where other people or client records would be affected.

Removing your personal account does not automatically delete a workspace owned by an organization or content that the organization must retain. We will separate or de-identify your account data where possible and coordinate remaining customer-controlled data with the workspace owner.

We acknowledge verified privacy requests and complete them within the period required by applicable law. Provider-specific deadlines, including the YouTube deadline above, apply where shorter.

Deleted active data may remain in restricted rotating production backups for up to 14 days. Backups are not used for ordinary product access and expire automatically. Any disaster recovery restore remains subject to the same verified deletion duties before restored data can return to ordinary use.

Billing, tax, fraud-prevention, security and narrowly scoped audit records may be retained for a longer statutory or limitation period. We restrict them to the purpose requiring retention and delete or de-identify them when that purpose ends.

Privacy and deletion requests: [email protected]. Product help before deletion: [email protected]. If you believe a request was not handled correctly, reply to the privacy thread with the request reference and the specific unresolved data.