Data deletion
Content Distributor is local-first. The account owner controls the environment where connected-account records, tokens, publishing plans, and media are stored.
Disconnect a platform account
Where your operational installation offers Disconnect, use its account settings and confirm the outcome with the installation operator. Some installations may not offer this control. Disconnecting alone does not erase saved records, media, backups or published posts.
Revoke at the platform
You may also revoke Content Distributor from the security or connected-app settings of Google, Facebook, or Instagram. Revocation prevents future API access even if a local record remains.
Delete local workspace data
Ask the installation operator to remove the relevant posts, media, delivery history, and workspace data. Ask which backups exist and what retention and erasure process applies; this public site does not define a universal retention period.
Completion
Because this public site does not maintain a hosted user database, it cannot delete files from the operator's local environment. Deletion is completed in that environment and, when applicable, in the connected platform's settings.
Revoke YouTube access at Google
You can also remove Content Distributor from Google Account security settings or Google Account connections. This blocks future API access. Disconnecting or revoking does not automatically remove a video already on YouTube or erase saved workspace history; contact that installation's operator to request removal of the account, records, media and backups. Self-service complete account deletion is not enabled in the local installation. The separate Xingyu Studio request form handles its own hosted TikTok data only.
Reddit connection (planned)
Reddit publishing is not yet available. Once enabled, you can disconnect Reddit in the product or revoke Content Distributor in Reddit's authorized apps settings. This stops future access but does not delete posts already on Reddit. To request removal of stored Reddit records, contact huhuwen09@gmail.com.
Limited hosted private-draft workbench — October 8, 2026
A separate workbench is available at app.xingyuzhitong.com for Google identity sign-in, private media and unassigned drafts. Platform connections, scheduling and publishing are available only for the platforms enabled for a given workspace; the section for each platform in the Privacy Policy describes the data involved. Google identity scopes are openid, email and profile; this login is not YouTube channel authorization or public-upload approval.
The workbench uses a dedicated Cloudflare D1 database and private R2 media bucket. It stores the Google account identifier, name, verified email, profile image, session/request information, identity sign-in credential data, uploaded media and prepared draft content. Google and Cloudflare process the information needed for identity, hosting and storage. The workbench does not ask for a Google password and does not sell this data or use it for advertising or model training. The separate platform-connection backend's token-encryption design does not mean every identity or session field uses that application encryption.
The browser uses an HTTP-only session cookie, localStorage for the selected workspace and a versioned draft copy scoped to the user and workspace, and a short-lived sessionStorage context where platform authorization is enabled. Draft copies contain preparation text/settings and selected account identifiers, not OAuth access or refresh tokens; they are not cloud schedules. Use Clear draft or browser site-data controls to remove them. A displayed Google profile image may request Google's image service, which receives normal browser request data.
Deleting an unused private file removes its active object and metadata. Referenced media is protected. This does not remove a platform video or erase database recovery history, replicas or backups, and is not complete account deletion. Contact huhuwen09@gmail.com to request stored account-data removal. A request or active-file deletion receipt is not proof of complete erasure. Other installations and Xingyu Studio retain their separately described operating boundaries.