Privacy Policy

Effective September 15, 2026

This policy explains how Blue Goose Marketing uses information when its owner connects an account to the private Goose Command Center.

Information Goose accesses

Goose accesses only the Google data covered by the permissions shown during authorization. Gmail permission may include messages, message metadata, drafts, labels, and account identity information. Other Google products are not accessed unless they are separately requested and authorized.

How Google user data is used

Google user data is used only to provide requested assistant functions. These may include reading and summarizing messages, finding information, organizing email, preparing drafts, and sending or modifying email when the account owner requests or approves the action.

Storage and security

Authorization tokens and operational records are stored on a private, access-controlled computer operated by Blue Goose Marketing. Reasonable technical controls are used to limit access. Passwords are not requested through Goose for Google authorization.

Sharing and AI processing

Blue Goose Marketing does not sell Google user data or use it for advertising. Data may be processed by contracted infrastructure or AI service providers only as needed to perform a task requested by the account owner. Google user data is not used by Blue Goose Marketing to train a general-purpose AI model.

Google API Limited Use

Goose's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

Data is kept only as long as reasonably needed to provide the requested function, maintain necessary operational records, and protect the system. The account owner may revoke access at any time through Google Account settings and may request deletion of locally retained Google user data.

Contact

Questions or deletion requests can be sent to collin@bluegoosemarketing.com.

Changes

This policy may be updated when Goose's functionality or data practices change. The effective date above identifies the current version.