1. Scope of this policy
This policy explains how the GWS CLI vpellerindata command-line tool and the OAuth
application used by it handle Google user data. It applies to the OAuth client
created and owned by the publisher named above and used by the gws CLI.
gws is a community open-source command-line tool. It is
not an official Google product and is not affiliated with,
sponsored by, or endorsed by Google. This policy does not cover the upstream
open-source project, which is a separate project and not the publisher of this
OAuth application.
2. Purpose and personal use
The application is intended for personal use by the individual who installs and runs it. Its purpose is to let that person perform Google Workspace operations from their own terminal, such as reading or sending mail, managing Drive files, updating calendar events, and reading or writing Sheets, Docs, and Slides content.
3. What data is accessed, and when
The application accesses Google user data only after you authorize it through Google's OAuth consent screen, and only when you run a command that requires that access. It does not access your data in the background or on its own initiative.
The application is intended to request access only to the following Google Workspace services, using the scope set below. It does not request Google Cloud Platform scopes.
| Service | Intended OAuth scope | Access |
|---|---|---|
| Gmail | https://www.googleapis.com/auth/gmail.modify |
Read and modify email messages and labels, but does not provide Gmail settings access or permanent deletion |
| Drive | https://www.googleapis.com/auth/drive |
Read and manage files as requested |
| Calendar | https://www.googleapis.com/auth/calendar.events |
Read and manage calendar events as requested |
| Sheets | https://www.googleapis.com/auth/spreadsheets |
Read and write spreadsheets as requested |
| Docs | https://www.googleapis.com/auth/documents |
Read and write documents as requested |
| Slides | https://www.googleapis.com/auth/presentations |
Read and write presentations as requested |
| Tasks | https://www.googleapis.com/auth/tasks |
Read and write task lists and tasks as requested |
The scope set above describes the intended access for this application. The exact scopes currently configured for the OAuth client are authoritative in the Google Auth Platform and are checked there before submission. This policy does not claim that any particular scope configuration is currently active, and it does not claim Google approval or verification.
4. How data is used
Google user data accessed through the application is used only to:
- execute the Workspace operation you explicitly request by running a command; and
- show you the result of that operation.
The publisher does not use Google user data for advertising, profiling, resale, model training, or any other onward disclosure.
5. Where data is stored and how it flows
The application runs locally on your own machine. API calls go directly from the local CLI to Google APIs. OAuth tokens stay on your machine, in the CLI's encrypted local credential storage (documented as AES-256-GCM with OS keyring protection). Command outputs are managed by you and remain local.
The publisher's server at gws.vpdata.fr serves only these static
information pages. It does not receive Google Workspace data or OAuth tokens, and
it does not handle OAuth callbacks.
6. This website
These webpages are static. They contain no analytics, no cookies, no tracking pixels, and no forms, and they do not run JavaScript. The hosting and network providers that deliver the pages may process basic technical connection metadata (such as IP address and request information) for delivery and security purposes, under their own policies. This policy does not state a specific retention period for such metadata.
7. Data sharing
Data is sent to Google APIs only to perform the operation you request. The publisher does not sell, rent, or otherwise disclose Google user data to third parties, and does not use it for advertising, profiling, or model training.
8. Google API Services User Data Policy
Use of Google user data obtained through Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. The application's use of Google user data is limited to providing and improving the user-facing features described in this policy.
9. Your choices
- Revoke access: you can remove the application's access at any time from your Google Account security settings (Google Account → Security → Third-party apps with account access).
- Delete local credentials: you can delete the CLI's local credential storage on your machine to remove the stored OAuth tokens.
- Privacy questions or deletion requests: contact vpellerindata@gmail.com.
10. Changes to this policy
This policy may be updated to reflect changes to the application or to applicable requirements. The effective date at the top of this page indicates the current version.
11. Contact
Vincent Pellerin
vpellerindata@gmail.com