Get help.
Stay in control of your data.

Contact the operator

For product support, bug reports, privacy, correction, revocation or deletion requests, contact the individual operator WANGWEN:

Describe your request, tool version and device type, with the relevant task or channel identifier. We will verify the request scope and identity, asking only for information needed to handle it. There is no public ticketing system or live chat.

What to include

• The time of the issue, command name or steps, whether a real account was involved, and expected versus actual results.
• Redacted status or error codes, limited to the smallest excerpt needed to explain the issue.
• Do not send Google passwords, refresh tokens, client secrets, upload session URLs, stream keys, or full credentials/ or .cws-state/ directories.

Revocation and local deletion steps

1. Stop new local operations first. Verify the dedicated installation and any tasks that still need to continue. Retirement removes local recovery capability; close old-version local worker processes before execution. This does not require stopping or restarting a VPS and does not end an existing remote livestream.
2. Revoke Google access if needed. Open Google connected-app settings, verify the Channel Workflow Studio connection and account, then remove access. While credentials still exist, you may also use grant-revoke-plan / grant-revoke: inspect the impact, confirm, execute and verify the result. Google revocation may affect the same user’s other scopes or related clients in this project; local retirement does not revoke access for you.
3. Choose partial cleanup or full installation retirement. data-delete-plan / data-delete only remove eligible terminal-task data and retain a minimal duplicate-prevention summary. To remove all managed data in this installation, review retire-plan, then confirm retire. It deletes data in .cws-state/ and credentials/ offline, including active or uncertain tasks, account credentials, cache and local encoder SSH keys. Only a constant retirement marker containing no channel, task or hash information, and empty lock files, remain. The installation is then permanently disabled: it cannot be reinitialized or recover or take over old tasks.
4. Check cache retention when continuing to use the tool. data-retention-check inspects all insights-cache partitions offline; cache-expired-purge actually removes cache past its retention period, without separate channel sign-ins or network requests. Cache has a maximum 30-day read-validity period. These commands have no background timer and do not guarantee expiry deletion while the computer is asleep, off or the commands are not run. They do not delete tasks, credentials or external copies.
5. Review retention and record a whole-installation deletion request. The candidate retention-audit reports categories and deadlines read-only; missing or anomalous timestamps require review. Use deletion-request-plan, review the plan, then deletion-request-register to record a request and deletion-request-check to inspect its seven-day deadline. Re-registration does not reset the original deadline. Earlier email or verbal requests require deadline tracking from their actual receipt. This is neither deletion execution nor a background timer; actual erasure still requires separate retirement confirmation as described above.
6. Handle online content and external copies separately. Local retirement does not delete original media outside the managed directories, exported reports, backups, email attachments, online content or Reporting jobs, and does not end remote livestreams. If encoder media was handed off, the receiving-device administrator must separately handle and verify its video, private streaming configuration, manifest and receipt. External temporary files left after abnormal interruptions also require review.
7. Ask for help when needed. Email xiaotao5490@gmail.com with the deletion scope and whether you can still access the device. The operator will distinguish completed, pending and inaccessible parts rather than report local cleanup as deletion of all copies.

New retirement, expired-cache cleanup and invalid-grant blocking have passed offline tests; real-account data has not been cleared. Complete deadline enforcement, external copies and real-account validation remain pending. Do not remove retirement markers, locks or summaries to bypass safeguards or recreate old tasks.

Read local help before acting

The command names above belong to the local Python tool; they are not actions this website can execute. Use the dedicated new installation and its current command help. Verify the project, account, task and state directory before supplying the confirmation returned by a plan. Do not apply these steps to another tool or a copied state directory.

If you can access your Google Account but not the installation, revoke access through Google first to stop future authorized access. This cannot remotely erase files or exports already stored elsewhere. State that limitation in your request.

bash scripts/start.sh grant-revoke-plan --credentials /ABSOLUTE/PATH/spec.json
bash scripts/start.sh grant-revoke --credentials /ABSOLUTE/PATH/spec.json --confirm "PLAN_CONFIRMATION"

bash scripts/start.sh data-delete-plan --kind upload --task-id YOUR_TASK_ID
bash scripts/start.sh data-delete --kind upload --task-id YOUR_TASK_ID --confirm "PLAN_CONFIRMATION"

bash scripts/start.sh data-retention-check
bash scripts/start.sh cache-expired-purge

bash scripts/start.sh retire-plan
bash scripts/start.sh retire --confirm "PLAN_CONFIRMATION"

Common questions

Why do local records remain after revocation?

Revocation changes access permission; it does not automatically erase files on a device. Run the applicable deletion flow separately and check backups, exports and minimal duplicate-prevention summaries.

Why are insights unavailable?

The features have passed offline tests. On November 8, 2026, the first private test video and thumbnail were uploaded and processing completed. A private broadcast and independent stream resource were created and bound: status ready, auto-start and auto-stop disabled, with no streaming started. Seven limited reads succeeded; operations, traffic and estimated-revenue Analytics returned empty rows, not zero values or zero revenue. The real operation recording is complete locally and is being reviewed and edited by the owner; it has not been published. Live streaming and real revocation and retirement validation remain pending. Missing channel authorization, insufficient permissions, pending reports, channel ineligibility or a failed service request can all make data unavailable. Preserve the accurate status instead of treating missing data as zero or interpreting estimated revenue as settlement.

Will an invalid authorization keep retrying?

After an actual OAuth request returns invalid_grant, the tool blocks further use of that grant. This does not prove a deleted channel or establish that access was deliberately revoked. The tool does not automatically reauthorize or repeatedly check in the background. Review the account and authorization issue before deciding what to do next.

Does this website read my account?

No. This site displays static information and workflow illustrations. Account authorization and channel operations happen in the tool you separately install, configure and approve.