fix: scrub PII from README screenshots#10
Merged
Conversation
The previous README screenshots showed a real owner email and fabricated viewer emails at real company domains. Reshot the Routes and Analytics images with a placeholder identity (you@example.com) and @example.com viewers, and removed the unused compose screenshot. No real address or company appears in the assets.
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
1 participant
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.
Pre-launch privacy audit found the README dashboard screenshots showed the owner's real email and fabricated viewer emails at real company domains (a16z/blackrock/sequoia). Reshot Routes + Analytics with placeholder demo data (you@example.com owner, @example.com viewers, neutral titles); removed the unused compose screenshot that carried a 'Confidential' demo card. Image-only change. The code, full git history, and telemetry audited clean separately.