Signals privacy policy

Google data accessed and why

With the operator’s authorization, Signals requests https://www.googleapis.com/auth/webmasters.readonly. It checks access to an allowed FixClue Search Console property and reads query and page performance: query text, page URLs, clicks, impressions, click-through rate, average position, and the report’s date and country filters.

These observations help compare existing page coverage with content opportunities and support recommendations to update a page, create a page, or research further. Search Console observations are incomplete and are not global keyword-volume estimates. Signals does not request Gmail, Drive, contacts, or Search Console write access.

Storage and security

OAuth client details, access tokens, and refresh tokens are stored in private local files on the operator’s computer with restricted filesystem permissions. Tokens are used only to authenticate requests to Google. They are not included in model input, public pages, browser responses, or saved research reports.

Retrieved search observations, website snapshots, generated briefs, and verification reports are saved locally. The local dashboard binds to loopback. This public information website receives none of those credentials or research records. Local files and backups still require normal device security; no system can promise absolute security.

Sharing with OpenAI

When the operator starts a research run, selected Search Console observations, relevant website content, source excerpts, and editorial instructions are sent to OpenAI’s API to generate recommendations. Query text and page URLs may be included. Google credentials are never sent to OpenAI.

The app requests that OpenAI response application state is not stored. API inputs and outputs are not used to train OpenAI’s models by default. Abuse-monitoring retention is generally up to 30 days, but may be longer where required by law or reasonably necessary to protect services or others from harm. Approved controls may change retention. OpenAI may process data outside the operator’s country. See OpenAI’s API data controls.

Signals does not sell Google user data, use it for targeted advertising, or use it to train a generalized AI model. Its use of Google API information follows the Google API Services User Data Policy, including the Limited Use requirements.

Retention, deletion, and revocation

Local research runs and their search observations remain until the operator deletes them; there is currently no automatic retention schedule. Disconnecting removes this app’s local OAuth credentials but does not delete existing research runs or copies in backups.

The operator can revoke Signals access in Google Account connections, remove local research data and backups, or ask for help at support@fixclue.com. Revocation prevents future authorized reads; it does not erase previously retrieved data or reverse requests already sent to OpenAI.

This public information website

This site has no Google login, analytics scripts, advertising cookies, forms, or local research database. Its hosting providers may process ordinary request information, such as IP address, browser details, requested URL, and timestamps, to deliver and secure these pages. Hosting is provided through OpenAI Sites and Cloudflare infrastructure, subject to their operational retention controls.

Questions, privacy requests, and reports of unwanted personal information can be sent to support@fixclue.com. Avoid including unnecessary personal information in research sources or support messages. This policy will be updated if Signals’ data practices change.