An AI answer may describe a brand as meeting a compliance standard. We wanted to know whether the sources cited in that answer actually support the claim, rather than merely mentioning the brand.
We examined compliance claims in answers to 1,337 relevant prompts on ChatGPT Search and Google AI Mode from May to October 2026. We checked readable cited pages for the brand and standard, then hand-checked a sample for an explicit statement of status. This evaluates source support, not the brand's compliance itself.
ChatGPT Search and Google AI Mode made 3,349 claims that a named brand meets SOC 2, HIPAA, GDPR, ISO 27001, PCI DSS or FedRAMP. Where every cited page could be read, 77.3% of claims cited a page naming the brand and the standard, and a hand check found 53 of 60 such pages state the status. Trust pages lift backing to 90.9%.
About 3 in 4 AI compliance claims cite a page that names the brand and the standard
A compliance claim is an AI answer saying that a named brand holds, meets or is covered by SOC 2, HIPAA, GDPR, ISO 27001, PCI DSS or FedRAMP. Examples are "Shopify is Level 1 PCI DSS compliant" or "Doxy.me offers a BAA". A claim is backed when the same answer cites a page whose text names both the brand and the standard.
We could read every cited page for 705 claims. In those answers, 77.3% of compliance claims were backed. A second check used only the link inside the claim sentence itself. Where that linked page could be read (1,157 claims), it named the brand and the standard 72.8% of the time. The two methods agree within five points: about 3 in 4 claims are backed.
Compliance claims backed by a cited page
- All claims (lower bound)69.2%
- Claim sentence's own link72.8%
- Every cited page readable77.3%
- Brand trust page cited90.9%
- backed, answers where every cited page could be read (705 claims)
- 77.3%
- backed, checking only the link in the claim sentence (1,157 claims)
- 72.8%
- backed, all 3,349 claims, counting unreadable pages as not backed
- 69.2%
Takeaway
53 of 60 backing pages actually state the status AI claimed
A page that names a brand and a standard does not always say the brand meets that standard. We read 60 randomly drawn backed claims next to the cited pages. In 53, the page stated the status: a vendor trust page, a help article on signing a BAA, or a third-party list of HIPAA compliant tools that includes the brand.
In the other 7, the page named both but did not tie them together, or the claim was about a different brand in the same sentence. Applying the 53 in 60 rate to the 77.3% backed share gives an estimate of 68.3%. So roughly 2 in 3 compliance claims are backed by a cited page that states the status.
HIPAA accounted for nearly two thirds of compliance claims
Across 24,029 answers to compliance prompts, the engines made 3,349 compliance claims about 790 brands. HIPAA accounts for 2,129 of them, almost two in three. SOC 2 follows with 671. GDPR claims were rare: 149, even though GDPR is named in 2,336 brand sentences.
Google AI Mode made slightly more claims than ChatGPT Search (1,728 vs 1,621), mostly because it made more HIPAA claims (1,152 vs 977). Claims appeared in 6.0% of answers.
Compliance claims by standard and engine
| HIPAA | 977 | 1,152 | 2,129 |
| SOC 2 | 365 | 306 | 671 |
| PCI DSS | 130 | 59 | 189 |
| GDPR | 51 | 98 | 149 |
| FedRAMP | 61 | 62 | 123 |
| ISO 27001 | 37 | 51 | 88 |
Only 1 in 4 mentions of a standard next to a brand is a compliance claim
Most sentences that name a standard describe what a product does for customers, such as "automates SOC 2 evidence collection". Only 3,349 of 13,882 brand-and-standard mentions (24.1%) were compliance claims.
The gap depends on the standard. HIPAA and FedRAMP mentions are claims about 40% of the time, because buyers ask whether a vendor signs a BAA or holds an authorization. GDPR and ISO 27001 mentions are claims only 6.4% and 5.0% of the time. Those standards mostly appear as the job a compliance tool does.
Share of brand-and-standard mentions that are compliance claims
- HIPAA40.8%
- FedRAMP39.7%
- SOC 221.0%
- PCI DSS17.4%
- GDPR6.4%
- ISO 270015.0%
Fewer than 1 in 10 compliance claims provably have no backing page
We sorted every claim by the best evidence in its answer. 69.2% had a backing page. 316 claims (9.4%) provably had none: in 156 the answer cited nothing, and in 160 every cited page could be read and none named both the brand and the standard. The remaining 21.3% could not be settled, because at least one cited page could not be read.
Google AI Mode claims were backed more often (73.3% vs 64.9%). ChatGPT Search cites more pages that could not be read, so more of its claims fall in the unsettled group. By standard, HIPAA claims were backed most often (74.0%) and FedRAMP claims least often (51.2%).
Best evidence behind each compliance claim
| Not checkable: some cited pages could not be read | 28.0% | 15.1% | 21.3% |
| No cited page names the standard | 0.4% | 1.0% | 0.7% |
| No citations in the answer | 3.6% | 5.7% | 4.7% |
| Cited pages name the standard, not the brand | 3.1% | 4.9% | 4.1% |
| A cited page names the brand and the standard | 64.9% | 73.3% | 69.2% |
The brand's own site backs 61.6% of backed claims
For 1,429 of the 2,318 backed claims, the backing page sits on the brand's own website. The rest rely on third-party pages only, mostly lists of compliant tools.
The engines differ. ChatGPT Search backs 81.4% of its backed claims with the brand's own page. Google AI Mode does so for 45.3% and leans on third-party lists. The pattern was clearest for SOC 2: 89.9% of ChatGPT Search SOC 2 claims cite a page on the brand's own site, against 51.6% for Google AI Mode.
- of backed claims backed by the brand's own page
- 61.6%
- ChatGPT Search
- 81.4%
- Google AI Mode
- 45.3%
When a brand's trust page is cited, 90.9% of its claims are backed
A trust page is a page on the brand's own site whose address points to security, trust, compliance, privacy or legal content, or to a standard such as /hipaa or /soc-2. Engines cited such a page for 26.7% of claims (894).
Those claims were backed 90.9% of the time. Claims that cited another page on the brand's site were backed 73.6% of the time. Claims with no page from the brand's site were backed 53.5% of the time.
Backed share by the brand pages cited
- Brand trust page cited90.9%
- Other brand page cited73.6%
- No brand page cited53.5%
Takeaway
AWS, Google Cloud and Microsoft Azure are called compliant most often
AWS received 148 compliance claims, Google Cloud 110 and Microsoft Azure 70, almost all for HIPAA. Behind them are healthcare and e-signature tools such as Caspio, Docusign, Atlantic.Net, Zoom for Healthcare and Doxy.me.
Backing varies. Sonix had all 27 of its claims backed, and Microsoft Power Apps 30 of 31. Microsoft Azure had 64.3% backed. We merged two index entries each for AWS and Google Cloud.
Brands with the most compliance claims
Claims · Top 10 of 15
- AWS148
- Google Cloud110
- Microsoft Azure70
- Caspio56
- Docusign41
Atlantic.Net41
- Zoom for Healthcare40
- Dialpad39
Doxy.me38
- UpGuard36
Explore the data (15 rows)
| AWS | 148 | HIPAA | 83.1% |
| Google Cloud | 110 | HIPAA | 76.4% |
| Microsoft Azure | 70 | HIPAA | 64.3% |
| Caspio | 56 | HIPAA | 92.9% |
| Docusign | 41 | HIPAA | 80.5% |
| 41 | HIPAA | 85.4% | |
| Zoom for Healthcare | 40 | HIPAA | 77.5% |
| Dialpad | 39 | HIPAA | 74.4% |
| 38 | HIPAA | 76.3% | |
| UpGuard | 36 | SOC 2 | 69.4% |
| PandaDoc | 35 | HIPAA | 71.4% |
| Dropbox Sign | 32 | HIPAA | 87.5% |
| Microsoft Power Apps | 31 | HIPAA | 96.8% |
| RingCentral | 31 | HIPAA | 77.4% |
| Sonix | 27 | HIPAA | 100.0% |
Payment brands get PCI DSS claims with weaker backing
SOC 2 claims go mostly to security-rating vendors: UpGuard (36), SecurityScorecard (26) and BitSight (21). PCI DSS claims go to payment processors, and some are backed less often: 47.6% for Stripe and 20.0% for Square, against 63.2% for Adyen.
FedRAMP claims split sharply. Google Cloud's 12 were 83.3% backed, Microsoft Azure's 8 were 12.5% backed. GDPR and ISO 27001 leaders have fewer than 30 claims each, so treat those rows as examples.
Most-claimed brands per standard
Claims · Top 10 of 12
- SOC 2 · UpGuard36
- SOC 2 · SecurityScorecard26
- SOC 2 · BitSight21
- PCI DSS · Stripe21
- PCI DSS · Adyen19
- PCI DSS · Square15
- FedRAMP · Google Cloud12
- GDPR · Bitwarden10
- FedRAMP · Microsoft Azure8
- GDPR · Jamie8
Explore the data (12 rows)
| SOC 2 | UpGuard | 36 | 69.4% |
| SOC 2 | SecurityScorecard | 26 | 92.3% |
| SOC 2 | BitSight | 21 | 71.4% |
| PCI DSS | Stripe | 21 | 47.6% |
| PCI DSS | Adyen | 19 | 63.2% |
| PCI DSS | Square | 15 | 20.0% |
| ISO 27001 | SecureFrame | 4 | 100.0% |
| GDPR | Bitwarden | 10 | 30.0% |
| GDPR | Jamie | 8 | 75.0% |
| FedRAMP | Google Cloud | 12 | 83.3% |
| FedRAMP | Microsoft Azure | 8 | 12.5% |
| FedRAMP | AWS | 6 | 66.7% |
UpGuard had the most claims without a supporting citation
A claim provably has no backing page when the answer cites nothing, or when every cited page could be read and none names the brand and the standard. UpGuard had 9 such SOC 2 claims. AWS and Google Cloud had 8 each, though both have far more claims overall.
No backing page does not mean the claim is false. We did not test whether any claim is true. It means the answer gave the reader nothing to check. SOC 2 claims are the most likely to provably lack a backing page: 119 of 671 (17.7%), against 144 of 2,129 HIPAA claims (6.8%).
Brands with the most claims lacking a supporting citation
Claims · Top 10 of 11
- AWS148
- Google Cloud110
- Microsoft Azure70
- UpGuard36
- BitSight21
- Quickbase18
- Cloudflare18
- Akamai14
- CrowdStrike12
- Recorded Future10
Explore the data (11 rows)
| UpGuard | SOC 2 | 36 | 11 | 9 |
| AWS | HIPAA | 148 | 25 | 8 |
| Google Cloud | HIPAA | 110 | 26 | 8 |
| Recorded Future | SOC 2 | 10 | 7 | 6 |
| BitSight | SOC 2 | 21 | 6 | 5 |
| FlyPix | SOC 2 | 6 | 6 | 5 |
| Microsoft Azure | HIPAA | 70 | 25 | 4 |
| Quickbase | HIPAA | 18 | 5 | 4 |
| Cloudflare | SOC 2 | 18 | 6 | 4 |
| Akamai | SOC 2 | 14 | 10 | 4 |
| CrowdStrike | SOC 2 | 12 | 7 | 4 |
Google AI Mode states 78.2% of compliance claims flatly
A flat claim states the status with no condition, as in "Shopify is Level 1 PCI DSS compliant". A conditional claim limits it to some plans or setups, as in "signs a BAA on eligible plans". An attributed claim reports it as the vendor's or a source's word, as in "UpGuard states it is SOC 2 Type II".
Google AI Mode stated 78.2% of its claims flatly and attributed only 4.1%. ChatGPT Search stated 55.8% flatly and attributed 22.1%. Hedging does not track sourcing: attributed claims were backed 74.6% of the time, flat claims 69.0%.
How compliance claims are phrased
| Google AI Mode | 78.2% | 17.7% | 4.1% |
| ChatGPT Search | 55.8% | 22.0% | 22.1% |
| Both engines | 67.4% | 19.8% | 12.8% |
The two engines name different compliant brands for the same prompt
For 92 prompts, both engines made at least one compliance claim. The average overlap between the two engines' sets of brands called compliant was 0.186 (Jaccard: shared brands divided by all brands named). Only 21.4% of brand and prompt pairs were called compliant by both engines.
Part of this is ordinary day-to-day change. The same engine, compared between the first and second half of the window, overlapped 0.23 (ChatGPT Search) and 0.20 (Google AI Mode). The cross-engine gap is a little larger than that change.
- brand overlap between engines, same prompt
- 0.186
- of brand and prompt pairs called compliant by both engines
- 21.4%
- same engine, first vs second half of the window
- 0.20 to 0.23
Compliance prompts keep the shortlist length but halve the incumbents' share
We compared compliance prompts with the other prompts in the same market. The shortlist did not shrink: the median answer named 5.33 brands for compliance prompts and 5.39 for the rest. The compliance shortlist was shorter in 80 of 166 market and engine pairs, about half.
Who is on it changes. Incumbents are a market's five most-named brands in other prompts during the first half of the window. In the second half, they took a median 15.8% of brand mentions in compliance answers, against 32.6% in other answers, across 46 market and engine pairs. Compliance answers bring in specialists.
- median brands per answer, compliance vs other prompts
- 5.33 vs 5.39
- median incumbent share of mentions, compliance vs other prompts
- 15.8% vs 32.6%
- market and engine pairs where incumbents lose share
- 33 of 46
What we counted and what we excluded
The sample is every answer from ChatGPT Search and Google AI Mode between May 24 and October 6, 2026 to 1,337 prompts that name SOC 2, HIPAA, GDPR, ISO 27001, PCI DSS, FedRAMP or compliance. Each brand sentence was matched against the six standards. A business associate agreement (BAA) counts as HIPAA. A word-pattern classifier then separated claims about a brand's status from descriptions of what a product does. In a hand check, 89 of 99 flagged sentences were real claims. In a second check, 10 of 60 unflagged sentences were claims we missed, so the claim counts are a lower bound. We set aside 198 negative claims, such as "does not sign a BAA".
Backing was checked against the text of cited pages as crawled by Parse, plus page titles and addresses. We could read 44.0% of the 7,581 distinct cited pages. That is why 21.3% of claims could not be settled, and why the headline uses the answers where every page could be read. Brand names are the public index spelling. Pages from Parse itself were cited for 3.5% of claims and were left in. The figures cover two engines over 19 weeks, so they are a snapshot, not a trend.
- answers
- 24,029
- brand sentences
- 117,941
- compliance claims
- 3,349
- flagged sentences confirmed as claims
- 89 of 99
What this means for your brand
Publish one trust page that names every standard you hold, in plain words, with the scope: which products, which plans, and whether you sign a BAA. When engines cite a brand's trust page, 9 in 10 of its compliance claims are backed.
Put the standard on the pages engines already cite for you, not only on the trust page. Claims backed only by third-party lists depend on those lists staying current. A one-line statement of the standard on your product and help pages gives the engine a page of your own to cite.
Check both engines. They agree on only about one in five brands they call compliant. For buyers, the practical test is whether AI answers HIPAA compliant software claims with a page that says so. Open the cited page before you rely on the claim.
How we measured
We examined compliance claims in 24,029 answers from ChatGPT Search (12,069) and Google AI Mode (11,960) between May 24 and October 6, 2026. The answers respond to 1,337 prompts that name SOC 2, HIPAA, GDPR, ISO 27001, PCI DSS, FedRAMP or compliance, and contain 117,941 brand sentences. We found 3,349 compliance claims about 790 brands and checked each against the text of the pages cited in the same answer.
- compliance claims about 790 brands
- 3,349
- cite a page naming the brand and the standard
- 77.3%
- backing pages that state the status
- 53 of 60
- backed when the brand's trust page is cited
- 90.9%
Get the data
Sources
- Wu et al., Nature Communications: an automated framework for assessing how well LLMs cite relevant medical references (April 2025) · accessed October 6, 2026
- Tow Center for Digital Journalism: AI search has a citation problem (March 2025) · accessed October 6, 2026