Identity verified
What it meansThe identity-verification process was completed.
Where it comes fromKaganCore identity-verification record
What it does not meanExpertise, credentials, professional history, or every claim was independently verified.
Trust Center
Trust should be inspectable, not implied.
KaganCore keeps identity, professional information, source evidence, operational reliability, privacy, publication and payment deliberately separate. Precision is the trust model.
Identity
Who is this person?
Evidence
What supports this record?
Operations
What does the system know from media work?
§ 01The trust ledger
One profile carries several signals without pretending they mean the same thing.
Each row states what the signal confirms, where it comes from, and the claim it deliberately does not make.
SignalWhat it meansWhere it comes fromWhat it does not mean
Professional information
What it meansBiography, expertise, experience, education, publications and media history supplied as professional profile information.
Where it comes fromProfessional record
What it does not meanThe information automatically carries a KaganCore verification claim.
Source evidence recorded
What it meansA source is attached to a specific professional or media record.
Where it comes fromEvidence attached to that specific record
What it does not meanThe entire profile or person has been broadly verified.
Operational reliability
What it meansA separate KaganCore signal derived from governed behavior in media workflows.
Where it comes fromKaganCore operational record
What it does not meanExpertise, fame, popularity, or a benefit that can be purchased.
§ 02Publication & privacy
Public Profile is an explicit subset, not a data-release switch.
A professional can choose an Internet-public profile without making every KaganCore record public. Public disclosure remains owner-selected and server-authoritative.
Eligible public subset
Owner-selected- Professional identity and headline
- Expertise, topics, languages and formats
- Selected professional and media records
- Professional links
Served only while the owner keeps Public Profile on
Never public by default
Withheld- Direct contact methods
- Precise availability and logistics
- Private operational notes and attachments
- Permissioned media-team context
Not released by the publication switch
Being listed inside KaganCore is a separate control from Internet-public publication. Neither implies the other.
Payment neutrality
Money can buy workflow. It cannot buy trust.
The professional profile, its privacy and its publication control are Free Core. Paid features improve workflow, never standing.
What payment reaches
Workflow, analytics and control.
Paid features change how a professional works, never where they stand.
Payment stops here
What payment cannot buy
Publication
Payment cannot make a private profile public.
Featuring
Payment cannot purchase presentation priority that masquerades as trust.
Identity verification
Payment cannot purchase a stronger identity-verification outcome.
Reliability & visibility
Payment cannot buy reliability advantage, preferential placement, or greater public visibility.
Withdrawal & search visibility
Publication and search exposure are separate decisions.
Turning Public Profile off stops KaganCore from serving the personal public profile. What third parties keep in their own caches is not KaganCore's to promise.
One owner decision
Public Profile on.
KaganCore governs this
The direct public link
KaganCore serves the governed public subset at the public address, and stops the moment the owner turns Public Profile off. Private, blocked, not-ready, suspended, deactivated, removal-requested or deleted profiles fail closed instead of disclosing personal profile content.
A separate governed layer
Search indexing
A second, separate release
A profile can be public by direct link without being released for search indexing. Search and index eligibility remain a separate governed layer, and KaganCore may reduce exposure without ever manufacturing publication consent.
Even when indexing is enabled in the future, KaganCore cannot guarantee that a search engine will crawl, rank, refresh or remove a result on a particular schedule. Third-party caches and message previews may lag, so KaganCore does not promise instant third-party removal.
Data & security principles
Authority should live deeper than the interface.
Layer 1
Displays
The interface
A badge, button, realtime signal, email or cached page. Useful, and never the final authority by itself.
Layer 2
Decides
Server authority
Authentication, authorization, validation and publication decisions, owned by the server rather than inferred from what is visible.
Layer 3
Authoritative
Durable truth
The database owns durable state. Everything above it is a view of this record, not a substitute for it.
Authority
Deeper
Platform restrictions may reduce visibility. They must not manufacture owner consent or publish a private professional record.