Privacy Policy

Effective date: November 9, 2026

This policy describes the public information website and owner-operated Google OAuth deployment automation called Wenona Release Automation. It does not replace the access settings or privacy practices of the separately hosted, private Wenona Cottage Tracker.

Information processed

The informational site has no account registration, forms, advertising, or intentional analytics tracking. It does not itself collect names, payment information, or cottage project records. Like other hosted websites, GitHub Pages may process basic technical access data under GitHub's privacy statement.

When the authorized owner consents through Google OAuth, the automation receives access credentials granting only the Google Apps Script project-management and deployment-management permissions requested on the Google consent screen. Those permissions may allow the automation to read and update Apps Script project source code, versions, and deployments to carry out reviewed releases.

How the authorization is used

Credentials are used by the owner's GitHub Actions release workflow for verification, deployment, and rollback. The workflow is configured to update an existing Google Apps Script application and to require an owner-authorized production run. The public site does not display or use these credentials.

Credential storage and sharing

The OAuth client credentials and refresh token are intended to be stored as encrypted secrets in the owner's private GitHub Actions environment, not in this public website or public repository. Authentication is handled by Google; deployment jobs run on GitHub. We do not sell personal information or share OAuth tokens for advertising.

Retention and revocation

Release configuration and deployment logs may be retained by Google and GitHub in accordance with their respective policies and the owner's account settings. The owner can revoke the Google OAuth grant in Google Account settings and remove the related GitHub environment secrets. Revoking the grant prevents future automated deployments until authorization is restored; it does not by itself delete the separately maintained cottage records.

Contact

For questions about this privacy policy, contact the owner through GitHub. Do not include passwords, access tokens, or private financial information in a public GitHub issue.