Game SEO Automation · Policy

Privacy Policy

Effective September 19, 2026

This policy applies to Game SEO Automation, an owner-operated internal game SEO and search-market research tool, and this public information website.

Current data processing

This public website serves static pages without visitor registration, public Google sign-in or an OAuth callback. Separately, the internal application uses an owner-authorized service account to access Google Ads read-only. It reads accessible-account and account metadata to confirm the authorized customer, and requests keyword historical metrics. It does not create campaigns, change budgets or manage account users.

The application source does not include advertising, analytics scripts or tracking cookies. The existing Cloudflare hosting configuration can inject a Cloudflare Web Analytics script into delivered pages; this site sets a Content Security Policy that blocks script execution. Cloudflare still hosts and delivers these pages and may process request information, such as IP address, browser information, requested URL and request time, for delivery, security and operational purposes under its privacy policy. We do not promise that visiting a public website produces no hosting logs.

Google data access and purpose

The service account accesses Google Ads within permissions granted by the account owner. Requested and retained research data includes keyword seeds, targeting settings, historical search estimates, advertiser competition and available bid ranges, with request identifiers and observation times. Account metadata is limited to access verification, account type and currency; retained research reports mask the customer identifier. Google data is used only for internal keyword research, search-demand validation and related SEO research workflows, not unrelated purposes.

We do not sell Google user data. We will not use Google user data for unrelated advertising, customer campaign management or training general-purpose AI models. Access will be limited to the application's stated internal research purpose.

Storage, retention and deletion

The service-account private key is stored on the owner-controlled automation server outside the code repository, research artifacts and routine application backups. The key file is restricted to its operating-system owner (0600) inside a private directory (0700). Access tokens are obtained over HTTPS, held in process memory and are not written to files or the application database. No ordinary-user refresh token is stored. Authorized server administrators can access server data; these controls are not a claim of dedicated encrypted-at-rest storage.

Normalized keyword evidence and request audit records are retained in the internal SQLite database and private research artifacts; selected acceptance results may be retained in the project repository. Routine state backups may contain research records, but not the private key. Research records are retained for ongoing research and audit until the owner deletes or archives them; no fixed automatic expiry or automated deletion service is currently implemented. A cache freshness period is not a retention period. Deletion is handled manually by the operator across live records, retained artifacts, repository copies and relevant backups; revoking access alone does not remove those copies.

You may contact the operator at contact@greedygrowerstools.com with privacy or deletion questions. If you email us, the correspondence is used to respond to your request; do not send passwords or authorization tokens.

Revoke Google access

For any ordinary-user Google authorization, you can revoke access through your Google Account third-party connections settings. Revocation stops future authorized access; it does not by itself delete copies already retained by an application. For the current service-account integration, the account owner can remove that service account from Google Ads Access and security and revoke its key in Google Cloud IAM. The operator can then remove the local credential and retained research records as described above. These account actions are manual, not performed automatically by this website.

Policy updates

We will update this page when actual processing changes. The effective date identifies the version of this policy. Contact the operator using the email above for questions.