Privacy, corrections and moderation
This unofficial community directory publishes a limited view of information already made public by the VCF Knight program and public Credly profiles.
Data sources and purpose
We store public names, company, cohort, region, LinkedIn URL and portrait from the public Broadcom Knight roster. When available, we also store the structured country code returned for the matching public LinkedIn profile; cities and free-text locations are neither requested nor retained. Only structured public certifications returned for that LinkedIn URL are inspected for public Credly links. Public Credly profile URLs, credential names, dates and images are used to show specialties and credential history. We do not import source email addresses.
Claimed profiles
LinkedIn OpenID Connect provides a stable account identifier, display name and portrait for a claim request. An administrator reviews every request. Approved Knights may publish a plain-text headline, bio, five topics, three HTTPS links and an optional Spotlight preference. Changes and administrative actions are audited.
Correction, removal and moderation
You may request correction or removal of a directory entry, withdraw a pending claim, or ask for member-written content to be hidden. We may hide content that is misleading, unsafe, promotional or unrelated to the community program. Claims can be revoked when identity or conduct requirements are no longer met.
The correction mailbox is being configured. Until it is published, contact the repository owner through the project’s public issue tracker.
Retention and security
Source data is refreshed periodically; LinkedIn countries are checked every 30 days and the last known country is retained when a later public profile omits it or cannot be collected. Credentials no longer returned by a complete Credly response are removed. LinkedIn scraper responses are reduced in memory and are never persisted. Rejected and withdrawn claim requests and audit events are retained for accountability and abuse prevention. OAuth secrets are never stored in the repository, remote images are mirrored through strict origin and size controls, and profile text is never rendered as HTML.