From 8c97c4fc7741b6206c213f02885fef09e00e30d4 Mon Sep 17 00:00:00 2001
From: Christopher <131207452+PetrefiedThunder@users.noreply.github.com>
Date: Mon, 26 Oct 2026 21:44:37 -0700
Subject: [PATCH] fix(copy): qualify hashing claim in terms section 7

---
 frontend/src/app/terms/TermsClient.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frontend/src/app/terms/TermsClient.tsx b/frontend/src/app/terms/TermsClient.tsx
index ff5daaff3..a76f3ecbf 100644
--- a/frontend/src/app/terms/TermsClient.tsx
+++ b/frontend/src/app/terms/TermsClient.tsx
@@ -71,7 +71,7 @@ We reserve the right to throttle or suspend API access if usage patterns suggest
     {
         id: 'accuracy-disclaimers',
         title: '7. Accuracy & Disclaimers',
-        content: `We work to keep our regulatory data accurate. Our FTL Coverage Checker covers FDA Food Traceability List categories per 21 CFR 1.1300 with citations to specific CFR sections. Our data is cryptographically hashed and independently verifiable.
+        content: `We work to keep our regulatory data accurate. Our FTL Coverage Checker covers FDA Food Traceability List categories per 21 CFR 1.1300 with citations to specific CFR sections. Where enabled, exports include content hashes you can check with our open verification script. Hashing is a RegEngine feature, not an FDA requirement.
 
 That said: regulations change. We monitor federal sources and update our data, but there may be delays. We strongly recommend verifying critical compliance decisions against official FDA sources (fda.gov, eCFR.gov).