Clarify PostHog key safety - #6918
Merged
Merged
Conversation
Users were avoiding committing the apiKey out of caution, unaware it's a client-side token already exposed in every browser request. Fixes DOC-415 / #609
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This was referenced Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation changes
Closes https://linear.app/mintlify/issue/DOC-415/clarify-posthog-integration-api-key-exposure-and-env-var-handling
For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience
Note
Low Risk
Documentation-only wording change with no runtime, security, or data-handling code impact.
Overview
Adds guidance under the
apiKeyconfiguration option explaining that PostHog project keys starting withphc_are client-side, public tokens (the same value sent from the browser with events) and that committing them in a docs repo is acceptable.This is documentation-only and addresses confusion about treating the key like a secret or relying on env vars for docs configuration.
Reviewed by Cursor Bugbot for commit bcdbaa6. Bugbot is set up for automated code reviews on this repo. Configure here.