Skip to content

Update compliance copy: Cap is now HIPAA compliant - #2121

Merged
richiemcilroy merged 1 commit into
mainfrom
hipaa-compliance-copy
Aug 13, 2026
Merged

Update compliance copy: Cap is now HIPAA compliant#2121
richiemcilroy merged 1 commit into
mainfrom
hipaa-compliance-copy

Conversation

@richiemcilroy

@richiemcilroy richiemcilroy commented Aug 13, 2026

Copy link
Copy Markdown
Member

Cap is now fully HIPAA compliant. This updates all user-facing compliance copy to match:

  • Footer: HIPAA badge now shows compliant; tagline reads "SOC 2 Type II, ISO 27001 & HIPAA compliant"
  • Homepage: hero announcement pill now announces HIPAA compliance and links to the HIPAA page; security FAQs updated
  • Pricing: page metadata and the plan comparison table include HIPAA
  • Upgrade modal: compliance feature bullet includes HIPAA
  • FAQ page: SOC 2 answer updated and a new "Is Cap HIPAA compliant?" entry added
  • HIPAA SEO page: reframed from "HIPAA workflows via self-hosting" to compliant out of the box with signed BAAs, self-hosting kept as the extra-control option; new comparison table row
  • Self-hosted SEO page: HIPAA FAQ answer now leads with compliance
  • llms-full.txt: security and compliance lines updated
  • SOC 2 blog post: "What is next" section updated to reflect completed HIPAA work
  • New changelog entry announcing HIPAA compliance

Greptile Summary

This PR updates public marketing, pricing, FAQ, SEO, changelog, and machine-readable copy to announce Cap’s HIPAA compliance.

  • Adds HIPAA to footer, homepage, pricing, upgrade, plan-comparison, and FAQ messaging.
  • Reframes the HIPAA landing page around Cap Cloud with signed BAAs while retaining self-hosting as an additional-control option.
  • Updates historical and generated content, including the SOC 2 post, changelog, metadata, and llms-full.txt.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete changed-code defect established.

The changes are limited to public-facing copy and content arrays that existing generic renderers support, and the investigation found no reachable build, runtime, entitlement, or security failure.

Important Files Changed

Filename Overview
apps/web/components/pages/seo/HipaaCompliantScreenRecordingPage.tsx Reframes the HIPAA landing-page content, adds a feature and comparison row, and updates setup and FAQ guidance without violating the generic SEO renderer’s content shape.
apps/web/components/pages/FaqPage.tsx Updates the existing compliance answer and adds a HIPAA-specific FAQ entry with a link to the dedicated landing page.
apps/web/components/UpgradeModal.tsx Adds HIPAA to the existing compliance benefit shown in the Pro upgrade modal; no concrete entitlement defect was established.
apps/web/components/pages/_components/ComparePlans.tsx Adds HIPAA to the Pro compliance comparison row without changing rendering or plan-selection behavior.
apps/web/data/homepage-copy.ts Updates homepage security and regulatory FAQ copy to reflect HIPAA compliance and signed BAA availability.
apps/web/public/llms-full.txt Aligns machine-readable security, compliance, and competitor descriptions with the updated public messaging.
apps/web/content/changelog/web/2026-08-13-hipaa-compliant.mdx Adds a correctly structured changelog entry announcing HIPAA compliance and linking to supporting public pages.

Reviews (1): Last reviewed commit: "Update compliance copy: Cap is now HIPAA..." | Re-trigger Greptile

Footer badge, homepage hero pill and FAQs, pricing metadata and plan
comparison, upgrade modal, FAQ page, HIPAA and self-hosted SEO pages,
llms-full.txt, SOC 2 blog post update, and a new changelog entry.
@cursor

cursor Bot commented Aug 13, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@richiemcilroy
richiemcilroy merged commit bdc3034 into main Aug 13, 2026
21 of 23 checks passed
@richiemcilroy
richiemcilroy deleted the hipaa-compliance-copy branch August 13, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant