Privacy Policy
Last updated: 12 September 2026
This policy covers the Google Cloud project published under sillylogger and the OAuth client it registers (the “Project”). The Project is managed by Tommy Sullivan.
The Project exists so that command-line tools can authenticate and call Google APIs on behalf of the person who authorizes it. Those tools include gws and gog, and this policy applies equally to any other command-line tool that calls Google APIs through the Project’s credentials. The tools are separate programs, run locally by the person using them; what the Project itself does with Google user data is described below.
What is accessed
Google user data is accessed only through Google’s official APIs, and only after you grant access on Google’s OAuth consent screen. What can be reached depends entirely on the scopes you approve at that moment, which may include your Google Drive files, Gmail messages, Google Calendar events, Docs, Sheets, Slides, Tasks, Contacts, and comparable Workspace resources.
The Project requests the narrowest scopes that will do the job you asked for. If a scope is not granted, the corresponding operation fails rather than being worked around.
How it is used
Data is read or written solely to carry out the operation you requested, at the moment you request it. A command that lists your files lists your files. A command that appends a row to a spreadsheet appends that row. There is no background collection, no crawling, and no processing that you did not initiate.
Where the data goes
The tools that authenticate through the Project run locally, on your own machine. There is no sillylogger server, no hosted service, no database, and no operator-side logging: the Project is an OAuth registration, not an intermediary. Google user data moves between Google’s APIs and the machine you are sitting at, and passes through no system operated by sillylogger.
OAuth credentials and refresh tokens are stored on that same local machine, in a per-account configuration directory under your home folder, protected by your operating system’s normal file permissions. API responses are held in memory for the life of a command, and are written to disk only when you explicitly ask for output to be saved to a file.
What is never done with it
- Google user data obtained through the Project is not sold, rented, or traded.
- It is not transferred to advertisers, data brokers, analytics providers, or any other third party.
- It is not used to train, fine-tune, or otherwise improve any machine learning or artificial intelligence model, whether generalized or personalized.
- Nobody other than the person who authorized the Project reads their Google user data through it.
Limited Use
sillylogger’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
The Project retains no copy of your Google user data. Nothing is stored beyond the execution of a command, other than files you explicitly told a tool to write. Those files are yours, on your own disk, and you delete them the way you delete any other file.
You can revoke the Project’s access at any time from your Google Account permissions page. Revoking access immediately invalidates the stored tokens. To remove the credentials themselves, delete the relevant configuration directory on your machine.
Third parties
Access through the Project depends on Google’s own APIs and infrastructure, and your use of them is also governed by Google’s Privacy Policy. No other third-party service receives Google user data through the Project.
Children
The Project is developer tooling and is not directed at children under 13, and no data is knowingly collected from them.
Changes
This policy may be updated as the Project changes. Any revision is published on this page with a new date at the top.
Contact
Questions about this policy go to you@sillylogger.com.