How gog accesses, uses, stores and shares Google user data.
Last updated: 17 September 2026
gog ("the Application") is a personal, self-hosted command-line client for Google Workspace services. It is operated by a single individual for their own personal use, on their own machine, against their own Google Account.
The Application is not a hosted or multi-tenant service. It has no public sign-up, no user database, and no third-party users. It is a personal-use application with fewer than 100 users — in practice, one. There is no separate data controller distinct from the operator; the operator and the sole user are the same person.
This Privacy Policy explains what Google user data the Application can access, how that data is used and stored, and how you can revoke access at any time.
Access is granted through Google's standard OAuth 2.0 authorization flow. Nothing is accessed unless you explicitly authorize it, and the Application can only reach the Google services covered by the scopes you grant. Depending on which services the operator enables, the Application may access the following categories of data:
| Google service | Data accessible when authorized | Typical operation |
|---|---|---|
| Gmail | Email messages, threads, headers, labels and mailbox settings | Search, read, label, draft, send |
| Google Calendar | Calendars, events, attendees, times and event metadata | List, create, update events |
| Google Drive | Files, folders, file metadata, sharing metadata | Search, list, upload, download |
| Google Docs | Document content and structure | Read, export |
| Google Sheets | Spreadsheet cell values, ranges and sheet metadata | Read, update, append |
| Google Slides | Presentation content and metadata | Read |
| Google Contacts / People | Contacts, contact groups and profile information | List, search |
| Google Tasks | Task lists and task items | List, create, update |
| Google Chat | Spaces, messages and membership metadata | Read, send |
| Google Meet | Meeting spaces and conference records | Read |
| Google Forms / Sites | Form definitions and site metadata | Read |
| Apps Script | Script projects associated with your account | Read, execute |
| Google Analytics | Analytics properties and performance metrics | Read reporting data |
| Search Console | Search performance, queries, impressions, indexed pages | Read reporting data |
| Google Ads | Campaign, ad group, keyword and performance metrics | Read reporting data |
| YouTube | Channel, video and playlist data associated with your account | Read |
| Google Photos | Photos and albums you explicitly select or authorize | Read, upload |
| Google Classroom | Courses, coursework and rosters (education accounts) | Read |
| Account basics | Your email address and basic profile identifier | Identify the authorized account |
Which of the above is actually available depends entirely on the scopes you grant. Any service you have not authorized is inaccessible to the Application.
Google user data is used solely to perform the operations you explicitly request from the command line, on your own account. For example: searching your own mailbox, listing your own calendar events, or reading a spreadsheet you own.
Specifically, we do not:
The Application is designed to be stateless with respect to your Google content:
Your Google user data is not shared with anyone. It is transmitted only between your machine and Google's APIs, over encrypted HTTPS connections.
There are no third parties receiving your Google user data, no sub-processors, and no data resale of any kind. The only circumstance in which data might be disclosed is where required by applicable law or valid legal process — and because no Google content is retained, there is no stored data to disclose.
Because Google content is not persisted, there is no retained Google user data to delete on a schedule. The only retained items are the OAuth credentials described in section 4.
You can delete these at any time:
At any time, and without needing to contact anyone, you can:
gog's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Limitations on use of Google user data are described in section 3 of this policy, and the data handling practices described here are limited to those disclosed above.
The Application is a personal productivity tool operated by a single adult user. It is not directed to, marketed to, or intended for use by children under the age of 16, and it does not knowingly access data belonging to children.
This policy may be updated to reflect changes in the Application or in applicable requirements. The "Last updated" date at the top of this page will be revised accordingly. Because the Application serves only its operator, material changes take effect immediately upon publication.
For any question about this policy or about how your Google user data is handled: