Promptivity GSC Read Only Privacy Notice

Information accessed

The utility requests this Google permission: https://www.googleapis.com/auth/webmasters.readonly

Google's permission can cover Search Console properties available to the connected account. The utility is designed for two designated properties. Its request methods reject search-performance and URL Inspection requests outside those properties before network access; those checks have passed simulated tests, not live account verification. This application restriction does not narrow the underlying Google permission.

Property discovery can return identifiers and permission levels for other properties accessible to the account. Search-performance and URL Inspection requests are directed to the selected property.

Retrieved information can include property identifiers and access levels; daily search-performance figures; and inspected URLs, indexing and coverage information, crawl information, and Google-selected and user-declared canonical URLs.

Purpose and processing

Information is used to prepare the owner's requested search-performance and indexing reports.

The utility sends API requests to Google. Results returned through the owner's assistant workflow are also processed by OpenAI under the applicable account settings and policies. The owner currently allows model improvement, so eligible content may be used to improve OpenAI models. The utility itself has no direct OpenAI API integration; results can leave the desktop through the assistant workflow.

Storage and retention

The implementation is designed to store Google access and refresh credentials in macOS Keychain, separately for the two account configurations. This storage has not yet been tested with live credentials.

The downloaded OAuth client configuration remains in its owner-selected local location. The script does not copy or delete it.

The script prints results and does not itself create report files or application log files. Output can nevertheless be retained in task or conversation history, terminal captures, or files saved through the surrounding workflow. Those copies have separate storage and deletion controls.

The utility currently has no automatic retention period, credential-expiry cleanup, or built-in deletion function.

Removing access and data

The owner can remove the utility's access in Google Account settings. Removing access does not delete reports or other copies already created.

Local credentials, configuration files, saved outputs, and assistant history must be managed separately using the relevant device or service controls. Questions about these records can be sent to [email protected].

Changes

This notice will be updated before introducing materially different data uses.

Contact: [email protected]