Privacy Policy

Updated 19 October 2026. This policy covers gws CLI, a private Google authorization project for owner-operated business tools. It is used by owners and staff only, has no public signup, and is not a Google product. Return to the home page.

What we access

Users authorize their own business Google accounts. The venue reply helper connects with exactly gmail.readonly and gmail.compose. It reads incoming Gmail messages and Sent mail. The gmail.compose permission also allows sending at the provider level, but the venue helper code exposes draft creation only and has no send operation. Other owner-approved gws CLI workflows may use different scopes and commands, and the Google consent screen is authoritative.

How we use it

Anthropic processing

Selected email bodies, subjects and header metadata may be passed to Anthropic Claude through the operator subscription for drafting, proofreading and style analysis. Tools are off for these model calls. Anthropic privacy information is available at https://www.anthropic.com/legal/privacy.

Local counted style memory

The helper code does not train any base model. Style learning is kept as counted style rules in local files only.

Storage

Messages remain in Gmail. Message copies, reply comparisons and evidence can be kept on operator-controlled storage in Toronto, and helper state can use the private Hub database. Raw message copies and evidence are kept outside Git and are not published with these pages. Access tokens and refresh grants are stored in protected operator files.

Retention

No automatic deletion timer is implemented, and we state no retention period.

Revoking access and deletion

Revoking Google access does not by itself remove copies that already exist.

Google policy information

See the Google API Services User Data Policy and Google Cloud help for Google's requirements.

Contact

Questions or deletion requests: hello@purrify.ca. See also the Terms of Use.