Privacy Policy

This policy explains what AI Business Facts collects, why, where it is stored, how long it is kept, and how you get it deleted. Section 3 covers Google user data specifically — the exact permissions we request, field by field, and how to revoke and delete each one.

30 July 2026 — what changed: the 12-month retention on connected-account change records now runs from disconnection or account deletion, whichever comes first, and we say plainly that this record is the one thing that outlives deleting your account. Previously section 3 said write receipts were "deleted with the account", which was wrong. 28 July 2026: we added section 7, which explains the aggregated, de-identified statistics we build and keep, and says plainly that they survive account deletion. We also added a retention row for connected-account change records, which we now keep for 12 months after disconnection for security and dispute resolution. Sections 7 onwards were renumbered; every link still works.

1. Who we are and what this covers

AI Business Facts is a product of Quantumatic LLC ("we," "us," "our"). This policy covers:

• the website aibusinessfacts.com;
• the free AI Visibility Audit tool available on that site without an account;
• the AI Business Facts platform — the paid dashboard for businesses and agencies, including any Google accounts you choose to connect to it; and
• the AI Business Facts Pro WordPress plugin, where it communicates with the platform.

What the product actually does is described on the product overview. Our contractual terms are in the Terms of Service.

Quantumatic LLC is the controller of the personal information described here. Where an agency uses the platform to manage a client business, the agency is the controller of that client's business information and we act as its processor.

2. What we collect, at a glance

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

3. Google user data — what, why, where, how long, and how to delete it

We request three kinds of Google access. Each is optional, each is granted separately, and the product works without any of them.

3.1 Google Sign-In — scopes openid, email

What we request. Your Google account's unique identifier (the OpenID sub claim), your email address, and whether Google has verified that address. We do not request your name, profile photo, contacts, calendar, Drive, Gmail, or any other Google service.

Why. So you can sign in to an existing AI Business Facts account with your Google account instead of a password or emailed magic link, and so a signed-in owner can link a Google account whose address differs from the one they signed up with.

What we do with it. We match the identifier or email to an existing account and issue a session cookie. That is the whole feature. Signing in with Google never creates a subscription, never posts anything to your Google account, and gives us no ongoing access to anything: we request offline access nowhere in this flow, so we never receive or store a refresh token for sign-in. The access token is used once, during the sign-in redirect, and discarded.

What we store. A mapping record in our database (Upstash Redis) of the form google-link:<sub> containing your Google account identifier, the associated email address, the account it points to, and the date it was linked. Your account record additionally stores that identifier and email so the dashboard can display "connected as <your address>".

How long. Until you disconnect, or until your account is deleted — whichever is first.

How to revoke and delete. Sign in, open Account → Google account → Disconnect. This deletes the mapping record and clears the identifier and email from your account record immediately; you can still sign in by email. You can also revoke our access from Google's side at myaccount.google.com/permissions at any time.

3.2 Google Ads data — scope https://www.googleapis.com/auth/adwords (read-only use)

Status. This connector is built but not yet enabled for customers — the OAuth application and Google Ads API access are in review. Until it is enabled, the same report runs from a keyword report you export from Google Ads yourself and upload as a CSV. This section describes exactly what will be requested when you choose to connect an account, so that you can read it before you consent.

What we request. Read access to reporting on the Google Ads account you select. Specifically, we read:

• the customer (account) ID and account name of the Ads account you connect, so we can show you which account is connected;
• for a rolling reporting window (by default the last 30 days), per keyword or search term: the keyword/search-term text, impressions, clicks, cost, conversions, and conversion value;
• the campaign or ad group label those rows belong to, for grouping in the report.

We do not read your billing details, payment methods, account users, audience lists, customer match lists, or any creative assets.

Why we need it. The AI-exposure report tells you which of the search terms you are paying for now return an AI-generated answer above the ads. To do that it needs the terms and their spend, clicks, conversions and conversion value — otherwise it cannot tell you what that exposure is costing. Reading it directly from your account replaces a manual CSV export, and keeps the report current without you re-uploading.

What we never do. The connection is read-only in effect: we never create, edit, pause or remove a campaign, ad group, keyword or ad; we never change budgets or bids; we never upload offline conversions or customer data; and we take no action in your Ads account of any kind. Google's adwords scope is not offered in a read-only variant — the narrowing is enforced by us, and every request our servers make is a read query.

Where it goes. The rows are used to produce your report inside the platform. The keyword text (and only the keyword text — never your spend, conversions, account ID or any identifier) is sent to our search-data provider, DataForSEO, to check whether that query currently returns an AI Overview on Google or Bing. Google Ads data is never sent to OpenAI, Anthropic, Google Gemini, Perplexity or any other model provider, and is never used to train any model.

What we store, and where. In our database (Upstash Redis, described in section 13): the connection record (provider, account ID, account name, connection date, last sync date, error state), the OAuth refresh token encrypted at rest, the pulled keyword rows, and the reports and trend history derived from them.

How long. The refresh token is deleted as soon as you disconnect. Pulled rows and derived reports are kept for up to 12 months so trend and drift comparisons work, and are deleted within 30 days of you disconnecting the account or closing your subscription — sooner on request.

Never across customers. Your connected Google Ads data is used to produce your reports. We never use it for another customer, with one exception: it may contribute to the aggregated, de-identified statistics in section 7, and only where at least five separate businesses contribute to the number. Nothing in those statistics identifies you, and none of the Limited Use commitments above are relaxed by this — Google user data is still never used to train models, never sold, and never used for advertising.

How to revoke and delete. In the platform, open the Ads page and choose Disconnect: the refresh token is destroyed immediately and no further data is pulled. To also erase the data already pulled, email support@aibusinessfacts.com and we will delete it within 30 days (see section 10). You can revoke our access independently from myaccount.google.com/permissions, which immediately invalidates the token whether or not you tell us.

3.3 Google Business Profile data — scope https://www.googleapis.com/auth/business.manage

Status. As with Google Ads, this connector is built but not yet enabled for customers pending Google's review. Until then, we read only publicly available listing information through the Google Places API (see section 4), which is not Google user data. This section describes what will be requested when you choose to connect a profile.

What we request. Access to the Business Profile locations you select. We read:

• the location's name, address, phone numbers, website URL, opening hours and special hours;
• its primary and additional categories, attributes and service areas;
• its description and services;
• aggregate review count and average rating, and the profile's verification and publication state.

We do not read the text of individual reviews or reviewer identities, we do not read your messages or message contents, and we do not access Business Profile insights beyond what is needed to show the profile's completeness.

Why we need it. Google Business Profile is one of the sources AI assistants ground local answers in. To tell you why an assistant gives a wrong answer about your hours, we have to compare what the assistant says with what your profile actually says. Reading the profile is what turns "AI got your hours wrong" into "AI got your hours wrong because your profile still shows the holiday hours."

Writing to your profile. The business.manage scope permits writes, and one feature uses it: pushing a corrected fact (for example, updated hours) back to your profile. That write happens only when you approve that specific change in the product. There is no automatic, scheduled or agentic writing, no bulk push, and no change we make on your behalf without an explicit, per-change approval. Every write is recorded with a timestamp, the field changed, the old and new values, and Google's confirmation response, so you have a receipt.

What we store, and where. In our database: the connection record (location ID and name, connection date, last sync date), the OAuth refresh token encrypted at rest, snapshots of the profile fields listed above, comparisons of those fields against AI answers, and the write receipts described above.

How long. The refresh token is deleted as soon as you disconnect. Profile snapshots and comparisons are kept for up to 12 months for trend and drift reporting and are deleted within 30 days of disconnection or subscription closure. Write receipts are kept for 12 months after you disconnect the account or delete your AI Business Facts account, whichever happens first, as proof of what was changed and when — then purged. They are the one category that outlives account deletion, and only for that period; see 9.1.

How to revoke and delete. In the platform, open the client's Profiles page and choose Disconnect — the refresh token is destroyed immediately and no further reads or writes are possible. Email support@aibusinessfacts.com to have the stored profile data erased within 30 days. Access can also be revoked at myaccount.google.com/permissions. Revoking access never alters your profile; anything already published to Google stays published until you change it in Google.

3.4 Summary table

4. Other Google services on this site

These involve Google but do not involve data from your Google account. We list them so the picture is complete.

• Google Places API. We query publicly listed business information — name, address, phone, hours, rating, review count — to build the source of truth an audit scores against. This is public listing data about a business, retrieved with our own API key. It is not tied to your Google account and requires no permission from you.
• Google reCAPTCHA v3. The free audit form is protected by reCAPTCHA, which collects hardware, software and behavioural signals from your device and sends them to Google to distinguish humans from bots. Its use is subject to Google's Privacy Policy and Terms of Service.
• Google Ads conversion tracking (gtag.js). Our marketing pages load Google's global site tag so we can measure which advertising leads to signups. It sets Google advertising cookies on your browser and reports conversion events to our Google Ads account. It runs on the public marketing pages only. You can opt out at adssettings.google.com or by blocking third-party cookies.
• Google Fonts. Our pages load web fonts from fonts.googleapis.com and fonts.gstatic.com. As with any resource loaded from another host, your IP address and browser details are visible to Google in that request.
• Google Gemini API. Audits query Gemini through Google's paid developer API. We send the audit questions and the business's name, location and website — never your Google account data, and never another customer's data.

5. Other information we collect

5.1 The free audit

• Email address — required to run an audit; used to send you the results and, unless you unsubscribe, occasional marketing about our products.
• Business identifiers — the business name, website URL, or Google Places listing you choose to audit.
• Audit results — the score, grade, per-field comparisons and the answers the AI engines gave.
• Usage data — timestamps, audit type, a random session identifier, and aggregate counters used for rate limiting and abuse prevention.

5.2 Platform accounts

• Identity — name, email address, and either a password (stored only as a salted hash) or a one-time magic-link token. Optional two-factor secrets for administrator accounts.
• Business records — the facts you enter or confirm for each business: hours, phone, address, services, prices, profile URLs, industry.
• Agency records — for agency plans, the client businesses in your workspace, team members you invite, and any white-label branding you upload.
• Audit and report history — every measurement run, its results, and any exported PDF or summary.

5.3 The WordPress plugin

When you pair the AI Business Facts Pro plugin with your account, the plugin and the platform exchange: your site URL, the plugin and site version, the fact payload you have chosen to publish, and counts of AI-crawler requests to the published endpoints. The plugin does not send us your site's content, your WordPress users, your customers' data, or your database.

5.4 Billing

Payments are processed by Stripe. Card numbers are entered on Stripe's systems and never reach ours. We receive and store your subscription status, plan, billing email, and invoice history.

6. How we use information

• To run the service — perform audits, produce reports, publish the facts you approve, and keep your dashboard current.
• To authenticate you — sign-in, sessions, and protecting accounts from takeover.
• To bill you — manage subscriptions, plan limits, renewals and receipts.
• To support you — answer questions and diagnose problems you report.
• To protect the service — rate limiting, bot detection, fraud and abuse prevention, and enforcing spend ceilings on the free tools.
• To improve the product — aggregate usage analysis and error monitoring. We never analyse one business's Google user data to improve the product. It can only ever contribute to the de-identified aggregates described in section 7.
• To market to you — send audit results and, unless you unsubscribe, related product email. Google user data is never used for marketing or advertising.
• To build industry statistics — aggregated, de-identified numbers about how AI assistants answer questions about categories of business. See section 7, which explains what these are and why they outlive your account.

Our legal bases, where the GDPR or UK GDPR applies: performance of a contract (running the service you signed up for), legitimate interests (security, abuse prevention, product improvement, industry research published only in de-identified form, and direct marketing to existing customers), consent (Google account connections, cookies that are not strictly necessary, and marketing where consent is required), and legal obligation (tax and accounting records).

7. Aggregated, de-identified statistics

We create and keep aggregated, de-identified statistics derived from use of the Services — for example, industry-level data about how AI assistants answer questions about categories of businesses. This data does not identify any business. It describes categories, not you: how often AI assistants name any dentist at all when someone asks for a recommendation in a mid-sized city, say, or how often the opening hours they give for a category of business turn out to be wrong.

7.1 How we make sure they identify no one

• Business and account identifiers are removed before a number is calculated. The aggregate never contains your name, your website, your account, or a code that points back to them.
• At least five businesses. We do not calculate, keep or publish an aggregate unless at least five separate businesses contribute to it. A group smaller than five is dropped, not published with a caveat.
• No single-business values. We do not publish a number that describes one business, and we do not publish a breakdown fine enough that one business could be worked out from it.
• One-way. These statistics cannot be reversed to recover the data they were built from.

7.2 They survive account deletion

This is the part worth reading twice. When you delete your account we erase your records on the schedule in section 8 and section 10. Aggregates we already calculated stay. By the time a number exists it no longer contains anything about you, so there is nothing in it to delete — and we cannot subtract one business's contribution from a statistic that has already been published.

If you would rather your business never contributed to these statistics at all, email support@aibusinessfacts.com and we will exclude it from future aggregates. We cannot remove it from ones already calculated, for the reason above.

7.3 What we use them for

• To improve the Services — for example, to see which audit questions produce unstable answers across engines and need rewriting.
• To publish research and industry benchmarks — so a business can compare itself to a category rather than to nothing.

7.4 Connected Google Ads data

We never use one customer's connected Google Ads data for another customer. The single exception is inside the de-identified aggregates described above, and only where at least five businesses contribute to the number.

Everything in section 3 still applies without exception: Google user data is never used to train AI or machine-learning models, is never sold, and is never used for advertising. An aggregate is a count or an average that we calculate and read; it is not training data, and we do not feed it to a model.

8. Who we share information with

These are our subprocessors. We share only what a provider needs to do its job. We do not sell personal information.

We also disclose information where the law requires it, to enforce our Terms, to protect our rights or someone's safety, and to a successor entity in a merger or acquisition — in which case this policy continues to apply until you are notified otherwise.

The business facts you publish through the plugin (hours, phone, address, services and similar) are, by design, made publicly readable on your own website so that search engines and AI crawlers can read them. That publication is the point of the feature, and it is under your control.

9. How long we keep things

9.1 The audit trail for connected accounts

When we change something in an account you connected, we record what changed, who approved it, and when. This is the receipt described in section 3, and it is the only category here that deliberately outlives the connection.

We keep it for 12 months after you disconnect the account or delete your AI Business Facts account, whichever happens first — then purge it. Deleting your account does not delete this record, and it is the only thing that survives that deletion. It is held under a random identifier with your account id removed from it, so it can no longer be looked up by anything that identifies you. It exists for two purposes and no others: investigating a security incident, and resolving a dispute about whether a change was authorised. We do not use it for analytics, for product improvement, or to build the aggregates in section 7. If you want it deleted sooner, ask us, and we will unless there is an open dispute or investigation it is evidence in — in which case we will tell you that, and what we are keeping.

10. Your rights, and how to delete your data

Wherever you live, you can ask us to: give you a copy of the personal information we hold about you; correct it; delete it; restrict or object to a particular use; or send it to you in a portable format. You can withdraw consent at any time, including consent for any Google connection, without affecting anything done before you withdrew it.

10.1 Do it yourself

• Disconnect a Google account: Account → Google account → Disconnect (sign-in), the Ads page (Google Ads), or the client's Profiles page (Business Profile).
• Revoke from Google: myaccount.google.com/permissions — this works even if you cannot reach our site.
• Stop marketing email: the unsubscribe link in any marketing message.
• Cancel a subscription: from your dashboard, at any time.

10.2 Ask us

Email support@aibusinessfacts.com with the request. We will verify that you control the account or email address involved, and complete access, correction and deletion requests within 30 days. We will tell you if a legal retention obligation (typically billing records) means something has to be kept, and what that is.

A full deletion request removes your account record, business records, audit and report history, connection records and any Google data we hold, from our live systems within 30 days, and from routine backups within 90 days.

Two things do not go, and you should know both before you ask.

• Aggregated, de-identified statistics already calculated (section 7). They identify no one, they cannot be reversed, and one business's contribution cannot be subtracted from them. We will exclude you from future ones if you ask.
• Records of changes we made to a connected account, and their approvals (9.1), for up to 12 months after disconnection — kept only as evidence of who authorised what, in case of a security incident or a dispute. Ask, and we will delete these too unless there is an open dispute or investigation they are evidence in; if so we will say so and tell you what we are keeping.

If you are in the EEA or UK you may complain to your local supervisory authority. Residents of California, Colorado, Connecticut, Virginia and other US states with comprehensive privacy laws have the rights above and will not be discriminated against for exercising them; we do not sell or share personal information as those laws define it.

11. Security

• All traffic to the site and API is encrypted in transit with TLS, with HSTS enforced.
• OAuth refresh tokens are encrypted at rest, and are never exposed to the browser or included in any report or export.
• Passwords are stored only as salted hashes; sign-in sessions are short-lived, server-side and revocable.
• Administrative access is protected by a strong secret plus optional time-based two-factor authentication, with sessions that expire.
• Access to production data is limited to the people who need it to operate the service.
• Endpoints are rate-limited and spend-capped to contain abuse.

No system is perfectly secure. If a breach affects your personal information, we will notify you and any regulator that the law requires, without undue delay.

12. Cookies and local storage

• Strictly necessary: a session cookie once you sign in, and a CSRF state token during a sign-in redirect. The product cannot work without these.
• Preferences: your light/dark theme choice, and your email address during a single free-audit session, both kept in your browser's local or session storage — not sent to us as cookies.
• Analytics: Vercel Web Analytics, which is cookie-less and does not fingerprint visitors.
• Advertising: Google Ads conversion tracking on the public marketing pages only, as described in section 4. This is the one non-essential tracker we use, and blocking it does not affect the product.

13. Where your data is processed

Quantumatic LLC operates from the United States, and our hosting (Vercel) and database (Upstash) providers process data on infrastructure located in the United States. Our email, payment, search-data and AI providers may process data in the United States and other countries where they operate. If you are in the EEA, the UK or Switzerland, transfers of your personal information out of your region rely on the European Commission's Standard Contractual Clauses or another approved transfer mechanism in our contracts with those providers.

14. Children

This is a business tool. It is not directed to anyone under 16, and we do not knowingly collect personal information from children. If you believe a child has given us information, email us and we will delete it.

15. Changes to this policy

We update this policy when what we do changes — including when a Google connection described in section 3 is switched on for customers. The "Last updated" date at the top always reflects the current version. For material changes affecting how we use information you have already given us, we will notify account holders by email before the change takes effect.

15.1 Change log

16. Contact us

Quantumatic LLC
Privacy and data requests: support@aibusinessfacts.com
General enquiries: hello@aibusinessfacts.com
Web: aibusinessfacts.com

We answer privacy requests within 30 days.