Data practices · updated 3 November 2026
Privacy Policy
This notice describes the currently inspected AUTO SUMO test application and its separately tested recovery candidate. It does not claim that planned safeguards have already been deployed. AUTO SUMO is operated by the owner of Asgq (@Autosumo). Questions, complaints and data requests can be sent to autosumo.media@gmail.com.
YouTube and the data we process
AUTO SUMO uses YouTube API Services to receive public live-chat messages and to manage the owner's broadcasts. YouTube's handling of your activity is described in the Google Privacy Policy and YouTube Terms of Service.
The inspected reader processes message text, message ID, author channel ID, publication timestamp, the live-chat/broadcast identifier and continuation tokens. The application uses these fields to recognize country choices, enforce voting windows and per-viewer rules, reject duplicate deliveries and investigate delivery failures. It does not need viewers' Google passwords or OAuth access. The inspected reader does not select or forward author display names, profile photographs or email addresses to the game; an author channel ID is still a viewer identifier, not anonymous data.
The operator's OAuth credentials are separate. They support reading and authorized management of the owner's YouTube channel, including creating and ending broadcasts and controlled messages in the owner's test chats. Credentials are not published on this site. This notice does not grant any new Google permissions.
Storage and retention: current implementation
| Data | Observed handling |
|---|---|
| Chat payloads in the recovery candidate | Message text, IDs, author ID and timestamp are queued in a private local SQLite database until the game acknowledges delivery. Acknowledgement removes the queued payload. The inspected version does not yet enforce an age limit on unacknowledged payloads. |
| Duplicate protection | The candidate retains message-ID digests and acknowledgement times. A maintenance step during batch staging removes delivered digests older than seven days. This is not an independent scheduled cleanup and does not cover all logs. |
| Game state and backups | The tested game persists viewer-associated country choices and message identifiers in voting/checkpoint structures, as well as championship results and titles. Session snapshots and technical backup packages can retain copies. No uniform automatic age-based deletion covering all these copies has been verified. |
| Technical diagnostics | Connection durations, status, error categories, counters and quota records are retained for troubleshooting. Candidate delivery diagnostics may contain message-ID digests. Public read-only A/B reports contain aggregate measurements, not chat text or viewer identifiers. |
| Video | Broadcast archives are kept by YouTube under YouTube's own controls. No new local video recording or full archive download is used for the current diagnostic work. |
Data requests and OAuth revocation
Email autosumo.media@gmail.com with your YouTube channel URL or ID and the relevant AUTO SUMO broadcast/date to ask about, correct or request deletion of data held by AUTO SUMO. Do not send passwords, access tokens or identity documents. The operator may need proportionate verification of the request. Requests are handled manually; there is no verified self-service deletion button in the current application. Sending a request is not itself proof that every backup has been purged.
If you are the operator who authorized AUTO SUMO, you can revoke Google access at Google account permissions. Revocation stops that authorization; removal of already stored application data is a separate operation. Automatic revocation-to-deletion handling is a release gate, not a capability we claim is complete.
Removing AUTO SUMO data does not delete your messages, account, broadcasts or archives from YouTube. Use YouTube's own controls for data held by YouTube. Deleting a message on YouTube has not been verified to trigger automatic deletion from all historical AUTO SUMO files.
Where data is processed and shared
Chat data is obtained from Google/YouTube and processed by operator-controlled software on the operator's workstation or rented compute used for a specific test. Previous test infrastructure used RunPod and Vast.ai; this notice does not authorize a new deployment. Those hosting environments necessarily process the data used by the software running there. Operational snapshots may be retained on the operator's workstation. Game output presents country-level power and results, rather than intentionally displaying viewer identities.
This informational website is hosted through OpenAI Sites/Cloudflare. Its published source contains no chat payloads, viewer identifiers, OAuth credentials or production connection details. We add no analytics scripts, advertising, forms, embedded players or browser storage to these pages. The hosting platform may process normal network/security request information such as IP address and browser headers. Clicking the YouTube link takes you to YouTube, where Google's own cookies and policies apply.
Changes and contact
Material changes to data practices require updating this notice and the applicable participation/authorization flow before the new use begins. Contact autosumo.media@gmail.com for privacy questions. This notice is a factual disclosure, not a substitute for unfinished retention and deletion controls.