PERSONAL CREATOR WORKSPACE
Privacy & your data
Review version · September 16, 2026. These pages describe the current local application. Audit preparation is in progress; this is not a claim of Google approval.
What Operator Grid does
Operator Grid runs on its owner's Windows PC. It uses YouTube API Services to identify the connected channel, research public videos, retrieve public statistics, and upload reviewed videos privately. It is not currently a public multi-user service.
Information processed
The application stores channel identity and statistics, public video metadata, research findings, source notes, tasks, captions, posting information, approval records and local media. Google OAuth tokens and client credentials are encrypted locally using Windows protection. The app does not collect your Google password.
Where information goes
Google receives authorization and API requests. An upload sends the selected video and posting details to YouTube. Research may request public information from YouTube or NASA. Local AI and transcription tools process research and footage on the PC. The dashboard loads Google Fonts, which involves requests to Google. Following external links opens the relevant service under its own policies.
Local storage
The local server uses a session cookie and a temporary OAuth-flow cookie. Saved application records and media remain on the PC. Protect access to your Windows account and backups; encrypted credentials do not mean every media or research file is encrypted.
Disconnecting and deletion
The local Privacy & connections panel includes a YouTube disconnect action. It requests Google revocation and removes the app's saved account tokens and channel identity. If revocation cannot be confirmed, it directs you to Google account permissions. Disconnecting does not delete research findings, drafts, media, or videos already on YouTube.
You can also revoke access through Google account permissions. Revocation alone does not erase local copies. Complete API-data deletion and timed retention controls are still being implemented; no automatic expiry for all stored API data is claimed. Existing post-publication media cleanup is separate and retains metadata.
Contact and third-party policies
Questions: rylanburners@gmail.com.