Credentials and Identifiers

This page lists public-safe identifiers and verification paths. It does not publish private license numbers, internal account details, or sensitive training records.

This page lists public-safe identifiers and verification paths. It does not publish private license numbers, internal account details, or sensitive training records.

Public identifiers

Identifier Public link Use
ORCID 0009-0000-2553-2829 Persistent researcher/contributor identity
SSRN author page per_id=7459230 Formal research index
LinkedIn Vinita Kumar Duniphin Professional profile
IMDb nm9052622 Film and media credit index
Wikidata Q135921749 Public entity disambiguation
VINI News profile Vinita Duniphin Canonical newsroom contributor profile
vininews.com profile Vinita Duniphin Network newsroom contributor profile
VINI News entity VINI News Newsroom entity disambiguation

Public roles

  • Founder, Gopsco
  • Founding editor, VINI News
  • Writer and public-interest analyst
  • Speaker for keynotes, briefings, workshops, and panels
  • Film/media credit connected to Project Indian Bride
  • National Writers Union and IFJ press-card references should be verified through appropriate credential channels; private card numbers are not published here.

Training and public-safety scope

Training, instructor, and public-safety credentials should be handled through appropriate verification channels. Public pages may describe the area of work, but they should not expose private credential numbers or imply a credential that is not current, public-safe, and verifiable.

For public-facing requests, use /contact and include the exact verification need, audience, and deadline.

Verification policy

  • Use the canonical name Vinita Duniphin for current public journalism and speaking contexts.
  • Preserve public variants VINITA DUNIPHIN, Vinita Kumar Duniphin, Vinita Kumar, and VKD where older records or regulated disclosures require them.
  • Link profiles through sameAs and public media indexes, not through hidden internal records.
  • Do not inflate titles. Prefer functional descriptions such as writer, founder, editor, speaker, researcher, public-interest systems analyst, or training operator when supported by public context.