Privacy Policy for Prompeteer.ai
The Prompeteer.ai Privacy Policy explains what data the service collects, how it is used and protected, and how to exercise your privacy rights including verified account deletion.
What this document covers
- What information Prompeteer.ai collects, and why.
- How that information is used, stored, and protected.
- When information is shared with processors and sub-processors.
- The privacy rights available to you and how to exercise them.
- How to request account deletion and how that request is verified.
Reading the full privacy policy
The full general Privacy Policy is published by our policy provider. Read it alongside the Google Search Console and Beacon supplement on this page.
Beacon and Google Search Console
Google Search Console and Beacon
This section explains the optional Google Search Console connection in Beacon, a Prompeteer service. It supplements the full Prompeteer Privacy Policy above.
What you authorize and what we collect
When you choose Connect Google, Beacon requests read-only Search Console access (webmasters.readonly). The Google account can be different from your Prompeteer login. Connecting does not give Beacon permission to change your website, submit sitemaps, or manage Search Console users.
Google returns the properties your account can access and your permission level. After you select a property covering your company page, Beacon collects the finalized Web search data Google makes available for that page: dates, search queries, page URLs, country, device, clicks, impressions, click-through rate, and average position. Google may omit private queries or limit the returned rows.
How Beacon uses and protects the data
Beacon uses these observations to show your Google search performance alongside its separate AI visibility measurements. Search Console observations can appear in your reports and exports, including saved or translated reports. People you share those documents with may receive that information.
Connection credentials are encrypted at rest and used by the server to retrieve permitted data from Google. They are not displayed in connection settings. Access to the saved connection and reports is checked against your account and authorized company workspace.
Retention and disconnecting
The connection supports daily background collection until you disconnect or access is revoked. Successful collections prune the current daily search-data table to a rolling 90-day window; a period without a successful collection can delay that cleanup.
Choose Disconnect in your Google Search Console connection settings to remove the active connection credentials and collected search-data rows from Beacon. Beacon also asks Google to revoke the grant. If Google cannot complete revocation, remove Prompeteer from your Google Account connections.
Disconnecting does not remove copies already included in saved reports, translations, or downloaded or shared documents. For deletion of account-linked data, use account deletion in Settings or contact info@prompeteer.com. The full Privacy Policy explains the applicable retention exceptions and privacy rights.
Google user data policy
As stated in our Privacy Policy, our use of Google API information follows the Google API Services User Data Policy, including its Limited Use requirements.
What it applies to
These terms cover the Prompeteer.ai website and every surface the service is reached through: the web application, the public REST API, the Prompeteer MCP server, the browser extension, and the coding-agent integrations documented on the Connect page.
Other policies
Questions
Questions about these policies, or about a privacy or deletion request, can be sent to info@prompeteer.com. Company information is available on About Prompeteer.