Privacy Policy

Keyword API is an independent Windows desktop application in development for keyword research, Etsy digital product analysis, and SEO research. This public website is informational only and offers no login, Google connection, download, or research service. For privacy inquiries, contact james.ashworth.ashy@gmail.com.

This policy is a draft for developer review, not a confirmation of an implemented application data flow. Before a public application release or OAuth verification submission, the developer must finalize the practices identified below and update this policy accordingly.

The planned Google integration is intended to request your authorization through Google OAuth so that Keyword API can use Google Ads API keyword planning functionality for search-volume research. Google authorization must occur through Google’s own authorization interface; this website does not request your Google password, credentials, or OAuth tokens.

Developer review required: confirm the exact OAuth scopes, Google account identifiers and Google Ads customer or account details accessed, keyword-planning response fields, and whether any profile or email data is requested. Describe the scope of access accurately, including whether the selected scope grants broader capabilities than the application uses. Do not imply that OAuth access or Google approval has been granted.

The planned purpose of Google user data access is to authorize requested keyword research and display Google Ads keyword-planning information, including available search-volume estimates. Google user data is not sold or used for advertising. This restriction applies to the planned integration; the developer must ensure the released implementation follows it. Google user data must not be used for unrelated purposes.

Developer review required: verify and document every actual use of Google user data, including any diagnostics, analytics, support access, or automated processing, before enabling the integration. Confirm compliance with the Google API Services User Data Policy and applicable Limited Use requirements.

The application is intended to run locally on Windows. This alone does not establish where tokens, Google user data, marketplace results, or reports will be stored. Local-only storage, encryption, and automatic expiration have not been confirmed.

Planned Etsy API features include researching public marketplace listings, favorites, reviews, and competition signals. Planned third-party SEO sources may provide backlink, referring-domain, and organic competition data. API results may include seller or other public identifiers.

Developer review required: identify each provider, the precise data and permissions accessed, requests sent, any stored results, provider terms, and retention restrictions. Do not assume public marketplace data is unrestricted or that an API integration is approved.

Research API requests necessarily communicate with the relevant provider. The final policy must identify what search terms, account identifiers, or other information is transmitted and why. This website is hosted on Netlify; hosting may involve processing technical request information such as IP addresses and browser details under the hosting provider’s practices. The site loads typefaces from Google Fonts, which sends font requests and associated technical information, such as your IP address, to Google. These website font requests are separate from the planned Google OAuth integration. No analytics script is installed.

Google user data is not sold or used for advertising. Developer review required: confirm all recipients, service providers, hosting logs, analytics, support tools, and any legal disclosure processes. State explicitly whether Google user data is shared, the specific purposes, and the applicable protections. No claim of zero third-party sharing is made in this draft.

Developer review required: document implemented security measures for tokens and research data, including storage protections, transport encryption, permissions, update mechanisms, logging redaction, and incident handling. Running locally is not itself a security guarantee. No specific storage encryption or other unverified protection is claimed.

No system can guarantee absolute security. Do not send passwords, OAuth tokens, or other credentials in support email.

You can review or revoke a connected application’s Google access through your Google Account connections. Revocation prevents future authorized access but does not necessarily delete previously saved information. For a privacy or deletion inquiry, email james.ashworth.ashy@gmail.com with a description of your request, without including credentials.

Developer review required: specify local data and token removal steps, deletion of server copies and backups if any, request verification, handling timelines, and retention exceptions. Confirm applicable privacy rights and the developer’s legal identity and jurisdiction before publication.

If you choose to email the developer, your email address and the contents of your message are sent through email providers to respond to your inquiry. Do not include sensitive account information. This site contains no application sign-in or submission form.

Developer review required: confirm email provider retention, website logging and any cookie use, the intended age audience, and procedures for any data received from children. The application is not yet released; an implemented children’s-data practice is not asserted.

This draft was prepared on October 26, 2026. It has no application-release effective date. Material changes to the final policy should be reflected on this page with an updated date. Contact: james.ashworth.ashy@gmail.com.

Publication checklist: add the developer or business’s confirmed legal name and any legally required address, finalize all data-handling practices, verify API policy compliance, and remove draft notices only after the text accurately describes the implementation.