Privacy Policy

This policy explains what information Bellsight collects, how it is used, who else processes it, and the choices you have. It covers the Bellsight application at app.bellsight.com, including report, audit and plan pages opened from a share link.

Who we are

Bellsight is operated by Dave Bell, doing business as Bellsight ("Bellsight", "we", "us"). Bellsight is a private tool for search, generative-search and accessibility analysis, provided to clients of our consulting engagements. Accounts are by invitation only; there is no public sign-up.

For any question or request about your information, including a request to see, correct, export or delete it, send it by email to privacy@bellsight.com.

Information we collect

Account information

When we invite you, we create an account with your email address. You can add a display name, a profile picture and a time zone. Profile pictures and workspace logos are stored as public files, so anyone who has a picture's address can view it. Your password is held by our authentication provider, Supabase, and is never stored by Bellsight in readable form. We also record which workspaces you belong to and your role in each: owner, editor or viewer.

Workspace information

For each workspace we store the website it covers and the settings its owner chooses, such as the search terms and AI prompts to track, competitor sites, business listings to check, the workspace name and logo.

Content of the websites we analyse

Bellsight crawls the pages of the website a workspace covers. For each page it keeps the title, description, headings, links, structured data and the visible text of the page, and a new copy each time the page changes, so changes can be compared over time. It does not keep screenshots. Pages are rendered in a remote browser, so accessibility checks see what a visitor sees. Bellsight also reads a small number of pages from competitor sites a workspace tracks, and from sites reviewed in an exploratory audit.

Answers from AI search engines

To measure how a site appears in AI search, Bellsight sends each tracked prompt to ChatGPT (OpenAI), Claude (Anthropic) and Gemini (Google) with web search turned on, and stores the full answer each engine returns, including its citations. Only the text of the tracked prompt is sent to these engines.

Search and performance data

Bellsight checks where a site appears in Google results for tracked search terms through DataForSEO, which receives only the search terms. It measures page speed with Google PageSpeed Insights, which receives only page addresses.

Google user data

If a workspace owner connects Google Search Console or Google Analytics, Bellsight reads data from those accounts. This is described in full in "Google user data" below.

Things you create

Bellsight stores what you and your colleagues create in it: tasks, notes, reports, plans, drafts, and conversations with the built-in assistant.

Email addresses you give us

When an owner shares a report or plan by email, Bellsight stores the recipients' addresses and the message sent, so there is a record of what was shared with whom.

Technical information

Our hosting provider keeps request logs. When a sign-in or password reset fails, we log the email address used, to diagnose the failure. Application errors are reported to Sentry, with its collection of personal details, such as IP addresses, turned off. Bellsight does not store IP addresses in its database. Share links count how many times they have been opened, but record nothing about who opened them.

How we use information

We use the information above to run Bellsight for the workspaces it serves: to crawl and audit sites, measure search and AI-search visibility, find issues and opportunities, write drafts and reports, send the emails you ask us to send, keep your account secure, and fix problems.

We do not sell personal information, we do not use it for advertising, and we do not build profiles of people for any purpose outside the service.

AI processing

Bellsight uses Anthropic's Claude models to analyse workspace data and to write the descriptions of issues and opportunities, drafts, report summaries and assistant answers. To do that, the relevant workspace data is sent to Anthropic with each request. We do not use your data to train AI models.

Google user data

This section describes what Bellsight does with data it receives from Google APIs.

What we request

A workspace owner can connect two Google services. Each connection asks Google for these permissions:

• Google Search Console: your Google account email address, and read-only access to Search Console (https://www.googleapis.com/auth/webmasters.readonly).
• Google Analytics: your Google account email address, and read-only access to Google Analytics (https://www.googleapis.com/auth/analytics.readonly).

Bellsight cannot change anything in your Google accounts.

What we read

• Search Console: the list of sites the account can see, and, for the chosen site, search performance data: clicks, impressions, click-through rate and average position, by date, by page and by search query. Bellsight reads the most recent days once a day, unless the owner turns the daily sync off, and can read up to 16 months of history.
• Google Analytics: the list of accounts and properties the account can see, and, for the chosen property, its name, time zone, currency and creation date. For that property Bellsight reads and stores daily traffic figures: sessions, engaged sessions, active users, new users, page views and key events, by date, by channel, by traffic source and medium, and by landing page (the site's address and the page's path, without any query string). Where the property holds advertising cost imported from linked ad accounts, Bellsight also reads and stores the cost, clicks and impressions by source, medium and campaign name. When the property is chosen, Bellsight reads its history back to the day the property was created and keeps what it has read; an owner can read the newest ten days again with Pull now. When a report is generated, Bellsight also reads traffic reports directly for it: sessions, active users and engagement rate, in total and by date, traffic source, channel, new or returning visitor, and landing page (here the page address including its query string).

How we store it

The access and refresh tokens Google issues are encrypted before they are stored. We keep the email address of the Google account that was connected, so the workspace can see which account it is using. The Search Console and Analytics data we read is stored in our database, in the workspace it was connected to, and in the reports generated from it.

How we use it

We use Google user data only to provide Bellsight's features to the workspace that connected it: performance dashboards, issues and opportunities weighed by real search traffic, and reports. Specifically:

• Members of the workspace see it in the application.
• Search Console figures for each page are sent to Anthropic so the analysis can weigh pages by their real search traffic. Reports, including their Search Console and Analytics sections, can be read by the workspace owner's assistant, which runs on Anthropic's models.
• If a workspace owner connects Bellsight to their own AI assistant through Bellsight's connector, that assistant can read the same reports.
• People who receive a share link from the workspace owner can see the report it points to until the link expires or is revoked.

We do not use Google user data for advertising, we do not sell it, we do not use it to train AI models, and no person reads it except to provide the service to the workspace, for security, or where the law requires it.

Bellsight's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting

A workspace owner can disconnect Google at any time from the Integrations page. Disconnecting deletes the stored tokens and the connected account's email address, which stops Bellsight's access to that Google account. Disconnecting also removes Bellsight's access at Google, unless another Bellsight connection uses the same Google account. You can also remove Bellsight's access from your Google account at myaccount.google.com/permissions.

Data that was already read before you disconnected stays in the workspace, including in reports already generated, until it is deleted at your request (see "How long we keep information").

Who can see your information

• Workspace owners see everything in their workspace, including its Google data, and manage its settings and integrations.
• Editors and viewers see the workspace's analysis, including its search performance data, and the names and email addresses of the other members.
• Recipients of a share link see only the report, audit or plan it points to, while the link is live. The page shows the workspace's name and logo, not the name of the person who shared it.
• Bellsight's operator has access to the workspaces it runs as part of the consulting engagement.

Service providers

Bellsight relies on these providers to run. Each receives only what it needs for its task.

Bellsight also reads public sources to check a business's presence online: Wikipedia and Wikidata, public domain registration records, and the business listing pages a workspace chooses to track.

These providers may process information in the United States and other countries where they operate.

How long we keep information

We keep workspace information, including crawled pages, AI-search answers, Google data and reports, for as long as the workspace is in use, so that changes can be measured over time. Some summaries are replaced as newer ones are calculated. Share links stop working when they expire or are revoked. Error reports and request logs are kept for the periods our providers set.

When you ask us to delete your account, a workspace, or data from a connected Google account, we delete it within 30 days, except where we must keep something to meet a legal obligation.

Security

All traffic to Bellsight is encrypted in transit. Google access tokens are encrypted before they are stored. Each workspace's data is isolated at the database level, so members of one workspace cannot read another's. Keys for Bellsight's connector are stored only as one-way hashes.

Cookies and browser storage

Bellsight uses only the cookies and browser storage it needs to work. It uses no analytics, advertising or tracking cookies.

Opening a share link does not set any cookie.

Your choices and rights

You can change your name, picture, time zone, email address and password in your profile settings. A workspace owner can disconnect Google at any time. To see, correct, export or delete the information we hold about you, email privacy@bellsight.com. We will answer within 30 days.

Children

Bellsight is a professional tool and is not intended for anyone under 16.

Changes to this policy

When we change this policy, we update the date at the top. If a change is material, we ask you to read and accept the new version the next time you use Bellsight.

Contact

Email privacy@bellsight.com with any question about this policy or your information.