Skip to content

docs(changelog): state SOC 2 status explicitly, initiated is not certified - #134

Merged
Ben-Home merged 1 commit into
mainfrom
docs/changelog-soc2-status-note
Nov 1, 2026
Merged

Ben-Home merged 1 commit into
mainfrom
docs/changelog-soc2-status-note

Conversation

@Ben-Home

@Ben-Home Ben-Home commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Closes the last open item in #96.

  • docs/changelog.md security section read "SOC 2 Type II compliance program initiated", which can be read as a certification claim. It now states it was a readiness program and that certification is not yet achieved, dated 2026-11-01.

Verified before opening (not taken from the issue text): grep -ri "soc 2 compliant" across docs/ and content/ returns no CorpusIQ self-claim, and the two live pages checked (/ai-for-compliance/, /best-mcp-server-for-business/) serve "SOC 2 aligned" with zero "SOC 2 compliant" occurrences.

No other line in this PR. The 15 other file references in #96 were verified already corrected on main.

…not certification

The security section read 'SOC 2 Type II compliance program initiated', which a
reader can take as a certification claim. The homepage posture is SOC 2 aligned
with no Type II certification claimed, so the history line now says which one it
is and dates the status.
@Ben-Home
Ben-Home merged commit 9eff053 into main Nov 1, 2026
1 check passed
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.

2 participants