Privacy Policy for Prompeteer.ai

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 we hold and where it comes from

When AI answer engines cite an article in their answers to questions a Beacon customer tracks, Beacon reads the public byline on that article. From it we record your name, the site you write for, the link to your public author page if the article gives one, and the article's title, address and publish date. We read only public pages, and our crawler, PrompeteerBeaconBot, follows the site's robots.txt.

We do not collect photos, social media handles or home addresses, and we do not build profiles beyond these professional bylines.

A Beacon customer can also hold a work email address for you, in three ways: from a contact list the customer imports, from a work address you or your site have published, or from Find email, which looks up a work address through Anymail Finder (AMF Internet Services Limited), a contact data service.

How Beacon finds a published address: when a Beacon customer adds you to their outreach list, Beacon looks for a work address you or your site have published: your author page on the site, a personal site that page links to, and the site's contact, press, about and team pages. Our crawler, PrompeteerBeaconBot, follows each site's robots.txt and our opt-out list. We don't guess addresses from your name, we don't test addresses against mail servers, and we don't read social networks. When the address we find is a shared one, such as editor@ or press@, the customer sees that it is a public contact page and not your personal address.

A published address Beacon finds this way may be shown to other Beacon customers who add you to their lists. An address a customer imports, and an address found with Find email, is kept only in that customer's workspace and is never shared with another Beacon customer.

Why we use it, and the lawful basis

Beacon shows a business which writers' articles shape AI answers about its market, so it can contact them about their coverage. Beacon itself never sends email to writers: a customer copies the address or opens it in their own mail app.

Our lawful basis is legitimate interests (Article 6(1)(f) of the GDPR and the UK GDPR): helping businesses understand and respond to the public coverage AI engines rely on, using only professional details you have already published. For addresses a customer imports, the customer decides how they are used and we process them on the customer's behalf.

Who can see it

Your name, site and cited articles are shown to Beacon customers whose tracked questions led AI engines to cite your work. An imported address, or one found with Find email, is visible only to the people in the one workspace that imported it or looked it up. A published address Beacon found on your or your site's public pages can be visible to any customer who adds you to their list. Anymail Finder receives your name and the site's domain when a customer uses Find email.

How long we keep it

If no customer has added you to a list and none of your articles has been cited for 12 months, we delete your record. An address found with Find email, or found on a published page, is shown for 90 days and then cleared. It is looked up again only if the customer asks. An imported address stays on that customer's list until the workspace is deleted or you ask us to remove it.

Your rights and how to be removed

You can ask for access to the information we hold about you, ask us to correct it, object to its use, or ask for its erasure. Write to info@prompeteer.com with your name and the site you write for, or the email address concerned. When we remove you, we delete your record, every customer's list entry, address and notes about you, and the related tasks. We keep only a one-way code of your name and site and of those addresses so that you are not added again.

A site owner can stop our crawler with a robots.txt rule for PrompeteerBeaconBot; the crawler page explains how. You can also complain to your data protection authority.